Unable to Remote Desktop to Windows 2003 Server

[Guest mtj7009]

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

[Guest Danny Sanders]

Re: Unable to Remote Desktop to Windows 2003 Server

 

Have you tried having the server restarted?

 

 

hth

DDS

 

"mtj7009" <MTJ7009@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

>

[Guest mtj7009]

Re: 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@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

> >

>

>

>

[Guest Danny Sanders]

Re: Unable to Remote Desktop to Windows 2003 Server

 

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@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@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

>> >

>>

>>

>>

[Guest mtj7009]

Re: Unable to Remote Desktop to Windows 2003 Server

 

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@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@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

> >> >

> >>

> >>

> >>

>

>

>

[Guest h.stroph]

Re: Unable to Remote Desktop to Windows 2003 Server

 

In news:83C257DB-996C-4622-BD31-F0D49A38F0E0@microsoft.com,

mtj7009 <MTJ7009@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

[Guest Andrew Morton]

Re: Unable to Remote Desktop to Windows 2003 Server

 

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

[Guest TheSmart_Developer]

Re: Unable to Remote Desktop to Windows 2003 Server

 

On Aug 28, 4:41 pm, "Andrew Morton" <a...@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?

[Guest Morgan che]

Re: Unable to Remote Desktop to Windows 2003 Server

 

 

Hi,

 

I am wirting to see how evertything is going?

 

Have this issue been sovled or you need further assistance? please feel

free to let me know.

Sincerely

Morgan Che

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

=====================================================

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

 

 

--------------------

--->Thread-Topic: Unable to Remote Desktop to Windows 2003 Server

--->thread-index: AckHk4pQuJDTcds+T5WYSSyzFjBtDg==

--->X-WBNR-Posting-Host: 65.55.21.8

--->From: =?Utf-8?B?bXRqNzAwOQ==?= <MTJ7009@newsgroup.nospam>

--->References: <83C257DB-996C-4622-BD31-F0D49A38F0E0@microsoft.com>

<uq86o74BJHA.4340@TK2MSFTNGP02.phx.gbl>

<D7465A7D-87A5-45F5-BF83-B371492C4D55@microsoft.com>

<ua7w2J5BJHA.4728@TK2MSFTNGP04.phx.gbl>

--->Subject: Re: Unable to Remote Desktop to Windows 2003 Server

--->Date: Tue, 26 Aug 2008 08:51:01 -0700

--->Lines: 51

--->Message-ID: <04F6F7D9-B4BB-4439-A5AA-CCBC4F9EBB03@microsoft.com>

--->MIME-Version: 1.0

--->Content-Type: text/plain;

---> charset="Utf-8"

--->Content-Transfer-Encoding: 7bit

--->X-Newsreader: Microsoft CDO for Windows 2000

--->Content-Class: urn:content-classes:message

--->Importance: normal

--->Priority: normal

--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3119

--->Newsgroups: microsoft.public.win2000.general

--->Path: TK2MSFTNGHUB02.phx.gbl

--->Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.win2000.general:13019

--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149

--->X-Tomcat-NG: microsoft.public.win2000.general

--->

--->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@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@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

--->> >> >

--->> >>

--->> >>

--->> >>

--->>

--->>

--->>

--->

[Guest mitchr]

Re: Unable to Remote Desktop to Windows 2003 Server

 

 

Do a remote shutdown "shutdown /r /t 10 /m \\computername" I have seen

this problem after patching here recently. and either I have to reboot

the machine at the console or I have to do the remote shutdown indicated

previously.

 

 

--

mitchr

------------------------------------------------------------------------

mitchr's Profile: http://forums.techarena.in/members/mitchr.htm

View this thread: http://forums.techarena.in/window-2000-help/1027216.htm

 

http://forums.techarena.in