hany1234
asked on
Cannot RDP into Windows 2003 R2 Std x64
Hi There,
I recently had a HP DL380 G7 rebuilt with Windows 2003 STD R2 because it had issues that were pointing to a corrupt registery. So a new install should not have any problems, right?
With the fresh new install, we are unable to RDP into it after we installed all the MS updates that were available. The new server is not a member of any domain.
This is not a firewall setting, as we have tried both firewall ON with Exceptions for RDP and Firewall completely OFF.
The server seems to send a RESET to any PC attempting to connect. This was observed via Wireshark. What is weird is that a RST and ACK flags are both set in the reply to any PC connection attempt. I am no expert in Wireshark but this doesn't look right.
Trying to telnet to the server on port 3389 causes the telnet window to close straight away.
What bugs me is that this was working before the Microsoft updates! I even installed the updates over an RDP session, and none of the settings was changed. We installed available MS Updates except one which failed, but succeeded after a restart. After that one was installed, RDP stopped behaving.
If I change the Client's settings to "Warn me" under server authentication, the client comes back with "The Identity of the remote computer cannot be verified. Do you want to connect anyway?" However, even accepting this still doesn't allow the connections.
VNC has no issues.
We have been staring at this issue for hours but can't find any resolution.
Any help would be appreciated.
Regards,
Hany
I recently had a HP DL380 G7 rebuilt with Windows 2003 STD R2 because it had issues that were pointing to a corrupt registery. So a new install should not have any problems, right?
With the fresh new install, we are unable to RDP into it after we installed all the MS updates that were available. The new server is not a member of any domain.
This is not a firewall setting, as we have tried both firewall ON with Exceptions for RDP and Firewall completely OFF.
The server seems to send a RESET to any PC attempting to connect. This was observed via Wireshark. What is weird is that a RST and ACK flags are both set in the reply to any PC connection attempt. I am no expert in Wireshark but this doesn't look right.
Trying to telnet to the server on port 3389 causes the telnet window to close straight away.
What bugs me is that this was working before the Microsoft updates! I even installed the updates over an RDP session, and none of the settings was changed. We installed available MS Updates except one which failed, but succeeded after a restart. After that one was installed, RDP stopped behaving.
If I change the Client's settings to "Warn me" under server authentication, the client comes back with "The Identity of the remote computer cannot be verified. Do you want to connect anyway?" However, even accepting this still doesn't allow the connections.
VNC has no issues.
We have been staring at this issue for hours but can't find any resolution.
Any help would be appreciated.
Regards,
Hany
Is port 3389 listening? From a command prompt on the server do:
netstat -an | find "3389"
My successful results are:
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
netstat -an | find "3389"
My successful results are:
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
Also: Open Terminal Services Manager. On the left pane, expand "This Computer" so it shows your terminal server. Click the + to expand everything. Does it show "RDP-tcp (listener)" ?
Can you right click and reset it?
Are you able to RDP to yourself from the server. Log on to the console of the server then RDP to "localhost" so you RDP to yourself.
Can you right click and reset it?
Are you able to RDP to yourself from the server. Log on to the console of the server then RDP to "localhost" so you RDP to yourself.
ASKER
Hi ZabagaR :)
Thanks for your reply.
I get the ssame result of:
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
Termina Services Manager Shows RDP-tcp (listener) and I was able to reset it as you suggested.
Attempting to RDP to the localhost gives me the same result. It immidiately fails and goes back to the Connection window which asks for the username and the password.
What else can I check??
Regards,
Hany
Thanks for your reply.
I get the ssame result of:
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
Termina Services Manager Shows RDP-tcp (listener) and I was able to reset it as you suggested.
Attempting to RDP to the localhost gives me the same result. It immidiately fails and goes back to the Connection window which asks for the username and the password.
What else can I check??
Regards,
Hany
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you make sure there is no antivirus blocking (as "theruck" suggested).
Can you try resetting the tcp stack?
http://www.mydigitallife.info/reinstall-and-reset-tcpip-internet-protocol-in-windows-vista-2003-and-xp/
Can you try resetting the tcp stack?
http://www.mydigitallife.info/reinstall-and-reset-tcpip-internet-protocol-in-windows-vista-2003-and-xp/
Wow, that's a weird one. Good to keep in mind for the future. Glad you got it.
ASKER
It was fixed.
try to remove terminal server windows component perhaps and then add it after a reboot.
uninstall antivirus.i had such issues randomly with kaspersky