RDP Issue on Windows Server 2008 R2 Enterpris

Microsoft Windows server 2008 r2 enterpr...
June 3, 2010 at 11:00:54
Specs: Windows Server 2008 R2 Enterprise 64-bit - Server
I am unable to RDP to a couple of my windows 2008 R2 servers. I just get "this computer can not connect" generic error. I have RDP turned on the server, no firewall blocking etc...Google search yields some good info but the attachment referred to in one of the good explanation is not there...which I need to unfortunately...at any rate, if anyone has any direct experience or insight please kindly share....thanks in advance.


See More: RDP Issue on Windows Server 2008 R2 Enterpris

Report •


#1
June 3, 2010 at 15:12:26
Check the EventViewer at the servers for any errors first.
Then open a command prompt and check, whether the servers are listening to port 3389 by using this command:
netstat -anp tcp

Post back the results.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#2
June 3, 2010 at 16:26:46

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1688 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:61625 0.0.0.0:0 LISTENING
TCP 0.0.0.0:61642 0.0.0.0:0 LISTENING
TCP 10.20.4.26:139 0.0.0.0:0 LISTENING
TIME_WAIT

the one server is listening as you can see above but the other one isn't..

I am looking through event viewer errors on this one that is listening, so can I make the other server listen or accept RDP connections through that port?

Thank you so much for responding.


Report •

#3
June 3, 2010 at 16:42:23
If terminal services is installed to the other server, and the needed terminal service licenses are installed too, you can enable RDP.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
June 3, 2010 at 16:49:03
"The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client"

This is one of the errors that sticks out on the one server that is listening to port 3389 but rejects RDP connections...



Report •

#5
June 3, 2010 at 16:58:53
Take a look at this:
http://support.microsoft.com/?scid=...

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#6
June 3, 2010 at 17:27:24
Oh yeah I saw that earlier when I was looking around but it only applies to; Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Web Edition
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server


I have a WinServer 2008 R2. I don't even have any of those sub keys listed in my parameter key.

Unbelievable!!


Report •

#7
June 3, 2010 at 17:55:56
What's about the certificate service?

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#8
June 4, 2010 at 15:11:40
Do you think terminal services role is required on winserver 08R2? I don't have it installed/added on this machine.

Report •

#9
June 4, 2010 at 15:31:33
Oh by the way, certificate is not there either.

Report •

Ask Question