Can no longer use remote administration after SP2 Update

[Kevin]

I logged in remotely and remotely performed the upgrade to SP2. After I
rebooted server, the upgrade works fine but I can no longer use remote
desktop connection to connect to my Windows 2003 Server. I cannot even use
remote administration to this server when I'm on another computer on the same
network. Any ideas of what may have caused this problem and a possible fix?

 

[Vera Noest [MVP]]

I don't know what caused the problem, but I'm pretty sure that in the
current situation you will need to reboot the server once more to fix
the problem.
You can do that from the console, or try to reboot the server
remotely with the shutdown command.
Type shutdown /? for options.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 11
jul 2007 in microsoft.public.windows.terminal_services:

> I logged in remotely and remotely performed the upgrade to SP2.
> After I rebooted server, the upgrade works fine but I can no
> longer use remote desktop connection to connect to my Windows
> 2003 Server. I cannot even use remote administration to this
> server when I'm on another computer on the same network. Any
> ideas of what may have caused this problem and a possible fix?

 

[Kevin]

Thank you for your reply. I have rebooted the server several times since and
still don't have any access to it remotely. (of course, I had to reboot
while onsite instead of using the shutdown command since I am unable to
connect to it remotely).

"Vera Noest [MVP]" wrote:

> I don't know what caused the problem, but I'm pretty sure that in the
> current situation you will need to reboot the server once more to fix
> the problem.
> You can do that from the console, or try to reboot the server
> remotely with the shutdown command.
> Type shutdown /? for options.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 11
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > I logged in remotely and remotely performed the upgrade to SP2.
> > After I rebooted server, the upgrade works fine but I can no
> > longer use remote desktop connection to connect to my Windows
> > 2003 Server. I cannot even use remote administration to this
> > server when I'm on another computer on the same network. Any
> > ideas of what may have caused this problem and a possible fix?
>

 

[Soo Kuan Teo [MSFT]]

Can you please check your firewall settings? The "Remote Desktop" firewall
exception should be checked.
Also please confirm remote desktop is enabled.
Thanks
Soo Kuan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Kevin" <Kevin@discussions.microsoft.com> wrote in message
news:FBF5D1FC-C660-4B36-BACD-76B7B98A059B@microsoft.com...
> Thank you for your reply. I have rebooted the server several times since
> and
> still don't have any access to it remotely. (of course, I had to reboot
> while onsite instead of using the shutdown command since I am unable to
> connect to it remotely).
>
> "Vera Noest [MVP]" wrote:
>
>> I don't know what caused the problem, but I'm pretty sure that in the
>> current situation you will need to reboot the server once more to fix
>> the problem.
>> You can do that from the console, or try to reboot the server
>> remotely with the shutdown command.
>> Type shutdown /? for options.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 11
>> jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > I logged in remotely and remotely performed the upgrade to SP2.
>> > After I rebooted server, the upgrade works fine but I can no
>> > longer use remote desktop connection to connect to my Windows
>> > 2003 Server. I cannot even use remote administration to this
>> > server when I'm on another computer on the same network. Any
>> > ideas of what may have caused this problem and a possible fix?
>>

 

[Vera Noest [MVP]]

You can actually use the shutdown command to shutdown a remote
server. The fact that rdp isn't working doesn't automatically mean
that you have lost all remote access to the server.

shutdown -r -m \\<remote_server_name> would probably have done the
trick.

Anyway, since a reboot didn't help, can you check (and this has to
be done at the console) if the server is listening on port 3389?
Type "netstat -an" (without the quotes) at a command prompt.

If it doesn't, check the settings for Remote Desktop for
Administration. Is it still enabled?

If the server is listening on port 3389, try (from the console) to
connect to the server itself (use "localhost" as the servername).

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 11
jul 2007 in microsoft.public.windows.terminal_services:

> Thank you for your reply. I have rebooted the server several
> times since and still don't have any access to it remotely. (of
> course, I had to reboot while onsite instead of using the
> shutdown command since I am unable to connect to it remotely).
>
> "Vera Noest [MVP]" wrote:
>
>> I don't know what caused the problem, but I'm pretty sure that
>> in the current situation you will need to reboot the server
>> once more to fix the problem.
>> You can do that from the console, or try to reboot the server
>> remotely with the shutdown command.
>> Type shutdown /? for options.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on
>> 11 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > I logged in remotely and remotely performed the upgrade to
>> > SP2. After I rebooted server, the upgrade works fine but I
>> > can no longer use remote desktop connection to connect to my
>> > Windows 2003 Server. I cannot even use remote administration
>> > to this server when I'm on another computer on the same
>> > network. Any ideas of what may have caused this problem and
>> > a possible fix?

 

[Kevin]

Thank you for your help. I did run the "netstat -an" command and it appears
that the server is not listening on port 3389. Where do I check to see if
remote desktop administration is enabled? From everything that I can see, it
appears to be. And the check mark is there under "allow users to connect
remotely". The terminal services service is also running. I still use
remote desktop connection to this server, even if I'm on another PC on the
network. Do you have any other ideas? Thank you.

"Vera Noest [MVP]" wrote:

> You can actually use the shutdown command to shutdown a remote
> server. The fact that rdp isn't working doesn't automatically mean
> that you have lost all remote access to the server.
>
> shutdown -r -m \\<remote_server_name> would probably have done the
> trick.
>
> Anyway, since a reboot didn't help, can you check (and this has to
> be done at the console) if the server is listening on port 3389?
> Type "netstat -an" (without the quotes) at a command prompt.
>
> If it doesn't, check the settings for Remote Desktop for
> Administration. Is it still enabled?
>
> If the server is listening on port 3389, try (from the console) to
> connect to the server itself (use "localhost" as the servername).
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 11
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Thank you for your reply. I have rebooted the server several
> > times since and still don't have any access to it remotely. (of
> > course, I had to reboot while onsite instead of using the
> > shutdown command since I am unable to connect to it remotely).
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> I don't know what caused the problem, but I'm pretty sure that
> >> in the current situation you will need to reboot the server
> >> once more to fix the problem.
> >> You can do that from the console, or try to reboot the server
> >> remotely with the shutdown command.
> >> Type shutdown /? for options.
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on
> >> 11 jul 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > I logged in remotely and remotely performed the upgrade to
> >> > SP2. After I rebooted server, the upgrade works fine but I
> >> > can no longer use remote desktop connection to connect to my
> >> > Windows 2003 Server. I cannot even use remote administration
> >> > to this server when I'm on another computer on the same
> >> > network. Any ideas of what may have caused this problem and
> >> > a possible fix?
>

 

[Vera Noest [MVP]]

Remote Desktop for Administration is enabled in Control Panel
System - Remote.

But now you have me completely bewildered by writing:
> I still use
> remote desktop connection to this server, even if I'm on another
> PC on the network.

What's the problem, then?
Note that in your first post you wrote:

> I cannot even use remote
> administration to this server when I'm on another computer
> on the same network.

Can you or can you not connect with an rdp client to this server?

If the server is not listening on port 3389, my guess is that you
can't connect. The only two options that I know of are (in this
order):

1. delete the rdp-tcp connection in Terminal Services
Configuration, create a new rdp-tcp connection, reboot the server

2. if 1. doesn't help: reboot the server, push F8, do a repair of
the OS installation.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 12
jul 2007 in microsoft.public.windows.terminal_services:

> Thank you for your help. I did run the "netstat -an" command
> and it appears that the server is not listening on port 3389.
> Where do I check to see if remote desktop administration is
> enabled? From everything that I can see, it appears to be. And
> the check mark is there under "allow users to connect remotely".
> The terminal services service is also running. I still use
> remote desktop connection to this server, even if I'm on another
> PC on the network. Do you have any other ideas? Thank you.
>
> "Vera Noest [MVP]" wrote:
>
>> You can actually use the shutdown command to shutdown a remote
>> server. The fact that rdp isn't working doesn't automatically
>> mean that you have lost all remote access to the server.
>>
>> shutdown -r -m \\<remote_server_name> would probably have done
>> the trick.
>>
>> Anyway, since a reboot didn't help, can you check (and this has
>> to be done at the console) if the server is listening on port
>> 3389? Type "netstat -an" (without the quotes) at a command
>> prompt.
>>
>> If it doesn't, check the settings for Remote Desktop for
>> Administration. Is it still enabled?
>>
>> If the server is listening on port 3389, try (from the console)
>> to connect to the server itself (use "localhost" as the
>> servername).
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on
>> 11 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Thank you for your reply. I have rebooted the server several
>> > times since and still don't have any access to it remotely.
>> > (of course, I had to reboot while onsite instead of using the
>> > shutdown command since I am unable to connect to it
>> > remotely).
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> I don't know what caused the problem, but I'm pretty sure
>> >> that in the current situation you will need to reboot the
>> >> server once more to fix the problem.
>> >> You can do that from the console, or try to reboot the
>> >> server remotely with the shutdown command.
>> >> Type shutdown /? for options.
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote
>> >> on 11 jul 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > I logged in remotely and remotely performed the upgrade to
>> >> > SP2. After I rebooted server, the upgrade works fine but I
>> >> > can no longer use remote desktop connection to connect to
>> >> > my Windows 2003 Server. I cannot even use remote
>> >> > administration to this server when I'm on another computer
>> >> > on the same network. Any ideas of what may have caused
>> >> > this problem and a possible fix?

 

[Kevin]

Vera,

I'm very sorry about my typo - I meant to put down that I still "cannont"
connect to this server using remote desktop connection. I am on vacation for
a couple of weeks but will try your suggestions when I return. Thank you
very much for your help.

"Vera Noest [MVP]" wrote:

> Remote Desktop for Administration is enabled in Control Panel
> System - Remote.
>
> But now you have me completely bewildered by writing:
> > I still use
> > remote desktop connection to this server, even if I'm on another
> > PC on the network.
>
> What's the problem, then?
> Note that in your first post you wrote:
>
> > I cannot even use remote
> > administration to this server when I'm on another computer
> > on the same network.
>
> Can you or can you not connect with an rdp client to this server?
>
> If the server is not listening on port 3389, my guess is that you
> can't connect. The only two options that I know of are (in this
> order):
>
> 1. delete the rdp-tcp connection in Terminal Services
> Configuration, create a new rdp-tcp connection, reboot the server
>
> 2. if 1. doesn't help: reboot the server, push F8, do a repair of
> the OS installation.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 12
> jul 2007 in microsoft.public.windows.terminal_services:
>
> > Thank you for your help. I did run the "netstat -an" command
> > and it appears that the server is not listening on port 3389.
> > Where do I check to see if remote desktop administration is
> > enabled? From everything that I can see, it appears to be. And
> > the check mark is there under "allow users to connect remotely".
> > The terminal services service is also running. I still use
> > remote desktop connection to this server, even if I'm on another
> > PC on the network. Do you have any other ideas? Thank you.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> You can actually use the shutdown command to shutdown a remote
> >> server. The fact that rdp isn't working doesn't automatically
> >> mean that you have lost all remote access to the server.
> >>
> >> shutdown -r -m \\<remote_server_name> would probably have done
> >> the trick.
> >>
> >> Anyway, since a reboot didn't help, can you check (and this has
> >> to be done at the console) if the server is listening on port
> >> 3389? Type "netstat -an" (without the quotes) at a command
> >> prompt.
> >>
> >> If it doesn't, check the settings for Remote Desktop for
> >> Administration. Is it still enabled?
> >>
> >> If the server is listening on port 3389, try (from the console)
> >> to connect to the server itself (use "localhost" as the
> >> servername).
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on
> >> 11 jul 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > Thank you for your reply. I have rebooted the server several
> >> > times since and still don't have any access to it remotely.
> >> > (of course, I had to reboot while onsite instead of using the
> >> > shutdown command since I am unable to connect to it
> >> > remotely).
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> I don't know what caused the problem, but I'm pretty sure
> >> >> that in the current situation you will need to reboot the
> >> >> server once more to fix the problem.
> >> >> You can do that from the console, or try to reboot the
> >> >> server remotely with the shutdown command.
> >> >> Type shutdown /? for options.
> >> >> _________________________________________________________
> >> >> Vera Noest
> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> >> TS troubleshooting: http://ts.veranoest.net
> >> >> ___ please respond in newsgroup, NOT by private email ___
> >> >>
> >> >> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote
> >> >> on 11 jul 2007 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > I logged in remotely and remotely performed the upgrade to
> >> >> > SP2. After I rebooted server, the upgrade works fine but I
> >> >> > can no longer use remote desktop connection to connect to
> >> >> > my Windows 2003 Server. I cannot even use remote
> >> >> > administration to this server when I'm on another computer
> >> >> > on the same network. Any ideas of what may have caused
> >> >> > this problem and a possible fix?
>

 

[Vera Noest [MVP]]

OK, no problem, I make some embarassing typos myself from time to
time
Have a nice holiday and let us know how things go when you return!

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on 17
jul 2007 in microsoft.public.windows.terminal_services:

> Vera,
>
> I'm very sorry about my typo - I meant to put down that I still
> "cannont" connect to this server using remote desktop
> connection. I am on vacation for a couple of weeks but will try
> your suggestions when I return. Thank you very much for your
> help.
>
> "Vera Noest [MVP]" wrote:
>
>> Remote Desktop for Administration is enabled in Control Panel
>> System - Remote.
>>
>> But now you have me completely bewildered by writing:
>> > I still use
>> > remote desktop connection to this server, even if I'm on
>> > another PC on the network.
>>
>> What's the problem, then?
>> Note that in your first post you wrote:
>>
>> > I cannot even use remote
>> > administration to this server when I'm on another computer
>> > on the same network.
>>
>> Can you or can you not connect with an rdp client to this
>> server?
>>
>> If the server is not listening on port 3389, my guess is that
>> you can't connect. The only two options that I know of are (in
>> this order):
>>
>> 1. delete the rdp-tcp connection in Terminal Services
>> Configuration, create a new rdp-tcp connection, reboot the
>> server
>>
>> 2. if 1. doesn't help: reboot the server, push F8, do a repair
>> of the OS installation.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote on
>> 12 jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Thank you for your help. I did run the "netstat -an" command
>> > and it appears that the server is not listening on port 3389.
>> > Where do I check to see if remote desktop administration is
>> > enabled? From everything that I can see, it appears to be.
>> > And the check mark is there under "allow users to connect
>> > remotely".
>> > The terminal services service is also running. I still use
>> > remote desktop connection to this server, even if I'm on
>> > another PC on the network. Do you have any other ideas?
>> > Thank you.
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> You can actually use the shutdown command to shutdown a
>> >> remote server. The fact that rdp isn't working doesn't
>> >> automatically mean that you have lost all remote access to
>> >> the server.
>> >>
>> >> shutdown -r -m \\<remote_server_name> would probably have
>> >> done the trick.
>> >>
>> >> Anyway, since a reboot didn't help, can you check (and this
>> >> has to be done at the console) if the server is listening on
>> >> port 3389? Type "netstat -an" (without the quotes) at a
>> >> command prompt.
>> >>
>> >> If it doesn't, check the settings for Remote Desktop for
>> >> Administration. Is it still enabled?
>> >>
>> >> If the server is listening on port 3389, try (from the
>> >> console) to connect to the server itself (use "localhost" as
>> >> the servername).
>> >>
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com> wrote
>> >> on 11 jul 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > Thank you for your reply. I have rebooted the server
>> >> > several times since and still don't have any access to it
>> >> > remotely. (of course, I had to reboot while onsite instead
>> >> > of using the shutdown command since I am unable to connect
>> >> > to it remotely).
>> >> >
>> >> > "Vera Noest [MVP]" wrote:
>> >> >
>> >> >> I don't know what caused the problem, but I'm pretty sure
>> >> >> that in the current situation you will need to reboot the
>> >> >> server once more to fix the problem.
>> >> >> You can do that from the console, or try to reboot the
>> >> >> server remotely with the shutdown command.
>> >> >> Type shutdown /? for options.
>> >> >> _________________________________________________________
>> >> >> Vera Noest
>> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> >> TS troubleshooting: http://ts.veranoest.net
>> >> >> ___ please respond in newsgroup, NOT by private email ___
>> >> >>
>> >> >> =?Utf-8?B?S2V2aW4=?= <Kevin@discussions.microsoft.com>
>> >> >> wrote on 11 jul 2007 in
>> >> >> microsoft.public.windows.terminal_services:
>> >> >>
>> >> >> > I logged in remotely and remotely performed the upgrade
>> >> >> > to SP2. After I rebooted server, the upgrade works fine
>> >> >> > but I can no longer use remote desktop connection to
>> >> >> > connect to my Windows 2003 Server. I cannot even use
>> >> >> > remote administration to this server when I'm on
>> >> >> > another computer on the same network. Any ideas of
>> >> >> > what may have caused this problem and a possible fix?

 

[Brad Tiede]

I have the same problem... but let me add a twist. In my frustration I said "FINE" and loaded TightVNC as a work around. The problem is... TightVNC acts the same way. Tries to connect and fails.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com