Unable to Remote Desktop to Windows 2003 Server

We have restarted the server multiple times. Nothing in the event logs either.

"Danny Sanders" wrote:

> Have you tried having the server restarted?
>
>
> hth
> DDS
>
> "mtj7009" <MTJ7009.DeleteThis@newsgroup.nospam> wrote in message
> news:83C257DB-996C-4622-BD31-F0D49A38F0E0@microsoft.com...
> > All of a sudden, we are unable to RDP to a Windows 2003 Server. It could
> > possible be a windows update that caused the issue but not sure which one.
> > I
> > have run Wireshark to make sure that tcp port 3389 traffic is hitting the
> > server and it is. On the client it says unable to connect to RDP.
> > Short of rebuilding the server are there any options or troubleshooting
> > steps i should take?
> > Windows Server 2003 SP2.
> > Firewall is off completely.
> > Thanks
> >
>
>
>

What OS are you using to connect with? Anything in that event log? Can you
connect using client running another OS?

You can also search the MS Knowledge base for "RDP".

hth
DDS


"mtj7009" <MTJ7009 RemoveThis @newsgroup.nospam> wrote in message
news:D7465A7D-87A5-45F5-BF83-B371492C4D55@microsoft.com...
> We have restarted the server multiple times. Nothing in the event logs
> either.
>
> "Danny Sanders" wrote:
>
>> Have you tried having the server restarted?
>>
>>
>> hth
>> DDS
>>
>> "mtj7009" <MTJ7009 RemoveThis @newsgroup.nospam> wrote in message
>> news:83C257DB-996C-4622-BD31-F0D49A38F0E0@microsoft.com...
>> > All of a sudden, we are unable to RDP to a Windows 2003 Server. It
>> > could
>> > possible be a windows update that caused the issue but not sure which
>> > one.
>> > I
>> > have run Wireshark to make sure that tcp port 3389 traffic is hitting
>> > the
>> > server and it is. On the client it says unable to connect to RDP.
>> > Short of rebuilding the server are there any options or troubleshooting
>> > steps i should take?
>> > Windows Server 2003 SP2.
>> > Firewall is off completely.
>> > Thanks
>> >
>>
>>
>>

We have tried using vista, xp, another windows 2003 server to see if any of
them would connect. None of which has been able to connect.
We have gone some searches on the web for any help, none of which helped us,
hence we are here.

"Danny Sanders" wrote:

> What OS are you using to connect with? Anything in that event log? Can you
> connect using client running another OS?
>
> You can also search the MS Knowledge base for "RDP".
>
> hth
> DDS
>
>
> "mtj7009" <MTJ7009.RemoveThis@newsgroup.nospam> wrote in message
> news:D7465A7D-87A5-45F5-BF83-B371492C4D55@microsoft.com...
> > We have restarted the server multiple times. Nothing in the event logs
> > either.
> >
> > "Danny Sanders" wrote:
> >
> >> Have you tried having the server restarted?
> >>
> >>
> >> hth
> >> DDS
> >>
> >> "mtj7009" <MTJ7009.RemoveThis@newsgroup.nospam> wrote in message
> >> news:83C257DB-996C-4622-BD31-F0D49A38F0E0@microsoft.com...
> >> > All of a sudden, we are unable to RDP to a Windows 2003 Server. It
> >> > could
> >> > possible be a windows update that caused the issue but not sure which
> >> > one.
> >> > I
> >> > have run Wireshark to make sure that tcp port 3389 traffic is hitting
> >> > the
> >> > server and it is. On the client it says unable to connect to RDP.
> >> > Short of rebuilding the server are there any options or troubleshooting
> >> > steps i should take?
> >> > Windows Server 2003 SP2.
> >> > Firewall is off completely.
> >> > Thanks
> >> >
> >>
> >>
> >>
>
>
>

In news:83C257DB-996C-4622-BD31-F0D49A38F0E0@microsoft.com,
mtj7009 <MTJ7009.DeleteThis@newsgroup.nospam> typed:

> All of a sudden, we are unable to RDP to a Windows 2003 Server. It
> could possible be a windows update that caused the issue but not sure
> which one. I have run Wireshark to make sure that tcp port 3389
> traffic is hitting the server and it is.

You are running wireshark on the 2003 server, yes? That will tell you that
the tcp packets are arriving on the interface you selected destined for port
3389 and their content, nothing more.

> On the client it says unable to connect to RDP.

This indicates that RDP is either not running on the server, not listening
on tcp port 3389, not configured to accept connections from the client, or
that a firewall is blocking. You state that firewall is disabled, so that
narrows it to 3 potential causes.

> Short of rebuilding the server are there any options or
> troubleshooting steps i should take?

If it's listening on port 3389 then you know that it's just not allowing
access to that client. If it's listening on a different port then you know
that piece of information as well. I use the following free application to
get familiar with my machine:


D:\ > fport /p
FPort v2.0 - TCP/IP Process to Port Mapper
Copyright 2000 by Foundstone, Inc.
http://www.foundstone.com

Pid Process Port Proto Path
428 svchost -> 135 TCP C:\WINNT\system32\svchost.exe
8 System -> 139 TCP
8 System -> 445 TCP
588 MSTask -> 1025 TCP C:\WINNT\system32\MSTask.exe
8 System -> 1027 TCP
624 svchost -> 3002 TCP C:\WINNT\System32\svchost.exe
624 svchost -> 3003 TCP C:\WINNT\System32\svchost.exe
624 svchost -> 3004 TCP C:\WINNT\System32\svchost.exe
14004 putty -> 3227 TCP D:\security\putty.exe
7044 MailWasher -> 3535 TCP
D:\security\MailWasher\MailWasher\MailWasher.exe
14848 firefox -> 3646 TCP D:\Mozilla\Firefox 3.0\firefox.exe
14848 firefox -> 3647 TCP D:\Mozilla\Firefox 3.0\firefox.exe
14848 firefox -> 3648 TCP D:\Mozilla\Firefox 3.0\firefox.exe
14848 firefox -> 3649 TCP D:\Mozilla\Firefox 3.0\firefox.exe
10764 putty -> 3705 TCP D:\security\putty.exe
13672 ePrompter -> 4494 TCP D:\ePrompter\ePrompter.exe
8312 terminal -> 4571 TCP
D:\trading_stuff\forex\interbank_fx\4.0\terminal.exe
1408 jusched -> 4754 TCP C:\Program
Files\Java\jre1.6.0_07\bin\jusched.exe
1408 jusched -> 4755 TCP C:\Program
Files\Java\jre1.6.0_07\bin\jusched.exe
1008 WinVNC -> 5900 TCP
D:\security\VNC\tight_VNC\TightVNC\WinVNC.exe
1432 Proxomitron -> 8080 TCP D:\security\proxomitron\Proxomitron.exe
624 svchost -> 53 UDP C:\WINNT\System32\svchost.exe
8 System -> 137 UDP
8 System -> 138 UDP
8 System -> 445 UDP
264 lsass -> 500 UDP C:\WINNT\system32\lsass.exe
624 svchost -> 520 UDP C:\WINNT\System32\svchost.exe
624 svchost -> 3001 UDP C:\WINNT\System32\svchost.exe
496 blackd -> 3738 UDP C:\Program
Files\ISS\BlackICE\blackd.exe
264 lsass -> 4500 UDP C:\WINNT\system32\lsass.exe

mtj7009 wrote:
> All of a sudden, we are unable to RDP to a Windows 2003 Server. It
> could possible be a windows update that caused the issue but not sure
> which one. I have run Wireshark to make sure that tcp port 3389
> traffic is hitting the server and it is. On the client it says
> unable to connect to RDP.
> Short of rebuilding the server are there any options or
> troubleshooting steps i should take?
> Windows Server 2003 SP2.

Maybe it's been left with two sessions logged in. Can you connect if you use
the /console command line switch?

http://blogs.technet.com/mhass/archive/2005/11/03/413605.aspx

Although if it's been restarted I don't know why those sessions would still
exist.

Andrew

On Aug 28, 4:41 pm, "Andrew Morton" <a....DeleteThis@in-press.co.uk.invalid>
wrote:
> mtj7009 wrote:
> > All of a sudden, we are unable to RDP to a Windows 2003 Server.  It
> > could possible be a windows update that caused the issue but not sure
> > which one.  I have run Wireshark to make sure that tcp port 3389
> > traffic is hitting the server and it is.  On the client it says
> > unable to connect to RDP.
> > Short of rebuilding the server are there any options or
> > troubleshooting steps i should take?
> > Windows Server 2003 SP2.
>
> Maybe it's been left with two sessions logged in. Can you connect if you use
> the /console command line switch?
>
> http://blogs.technet.com/mhass/archive/2005/11/03/413605.aspx
>
> Although if it's been restarted I don't know why those sessions would still
> exist.
>
> Andrew

Have you tried telneting to port 3389?