Cannot RDP to server after upgrade
I recently upgraded from Windows Server 2000 to Windows Server 2003 SP2. Everything works fine except I can longer use Remote Desktop to login remotely. I was able to prior to the upgrade.
1. Firewall on the server is disabled.
2. The Allow users to connect remotely to your computer check box is checked.
3. Proper users have been added to the Remote Desktop Users group.
4. The Terminal Services licensing is set to Remote Desktop for Administration.
5. The IP and name work fine and are pingable.
6. I can telnet to the name or ip 3389 from another machine.
7. I have rebooted numerous times from the Console.
I don't know what else to do. It is set up the same as all the other servers, and worked fine pre-upgrade.
1. Firewall on the server is disabled.
2. The Allow users to connect remotely to your computer check box is checked.
3. Proper users have been added to the Remote Desktop Users group.
4. The Terminal Services licensing is set to Remote Desktop for Administration.
5. The IP and name work fine and are pingable.
6. I can telnet to the name or ip 3389 from another machine.
7. I have rebooted numerous times from the Console.
I don't know what else to do. It is set up the same as all the other servers, and worked fine pre-upgrade.
DrDave242
What specific error do you get when to try to RDP to the server?
ASKER
This computer can't connect to the remote computer.
Try connection again. If the problem continues, contact the owner of the remote computer or your network administrator.
Try connection again. If the problem continues, contact the owner of the remote computer or your network administrator.
Are you able to RDP from the server to itself using its IP address?
ASKER
No, I can't. On the box itself it says it times out.
Open Terminal Services Configuration on the server and select Connections in the left pane. There should be a listener in the right pane named RDP-Tcp. Right-click it and select Properties. Under the Network Adapter tab, make sure an adapter is selected, or it's set to "All network adapters configured with this protocol."
ASKER
It's set to all, as are all the other servers. I did try to set it to the actual adapter, and that made no difference. In fact, if I remember right, it just reset to all when I restarted.
On that same tab, is "Maximum connections" set to 2?
ASKER
Yes.
try using this tool seems to be very good at fixing RDP connections called intelliAdmin Network Administrator 3.0 Free edition http://www.intelliadmin.com This tool has a remote desktop enabler along with several other usefull tools, check it out I think you will be surprised at how well it works. You can run this tool remotely against any machine on the network but there are some licensing restrictions.
You mentioned that you're able to telnet to port 3389 on that server, so something's listening on that port. Run "netstat -abn |more" on the server and hit the space bar until you see the entry for TCP port 3389. Its status should be listed as "LISTENING," and it should have the TermService service listed under it. (See the attachment, although the PID number - 1904 in mine - will likely be different.) Does it look correct?
netstat.jpg
netstat.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.