RDP issue

Not able to rdp in my lan. It was working yesterday, and now it is not. Pls help.
ibqtiAsked:
Who is Participating?
 
Rob WilliamsCommented:
Have you applied any Windows updates recently? If so some Windows updates require that the server be rebooted twice before Remote desktop is restored. Oddity, but true.

If you have applied SP2 there are several known issues. Have a look at the following:
http://www.lan-2-wan.com/2003-SP2.htm

If still having issues, run through the following check list. I would start with #8:
1-try connecting using the IP of the remote computer not the computer name
2-"allow users to connect remotely to this computer" must be enabled
3-you must be a member of the remote desktop users group of the local machine (administrators are by default)
4-if the workstation is a member of a server 2000/2003 domain you will have one of the 2 following check boxes, depending on the version, on the "Terminal Services Profile" of the users profile in Active Directory. Make sure it is checked appropriately. "Deny the user permission to log on to any terminal server", or "Allow Logon to Terminal Server"
5-if XP SP2 or Server 2003 SP1 the firewall needs to be configured to allow remote connections ( I would disable for now for troubleshooting purposes)
6-makesure any other software firewalls are disabled as well (for test purposes), including Internet security suites. Symantec's sometimes needs to be uninstalled or if using Symantec Antivirus some versions have "Internet Worm Protection" which can block Remote Desktop. Try disabling that as well.
7-Verify the Remote Desktop User group has the rights to log on using Terminal Services.  Go to Control Panel | Administrative tools | Local Security Policy | Local Policies | User Rights Assignments ...make sure Remote Desktop Users is included in "allow logon through Terminal Services"  
8-The terminal Services service must be running
If you have access to the remote machine make sure it is "listening" for your connection. To do so at a command line enter (substitute port # if not using default 3389):
  netstat  -an  |find  "3389"
You should get the following result:
TCP   0.0.0.0:3389    0.0.0.0:0    listening
If not go to Start  | Run | services.msc and see if Terminal Services is started and set to automatic
0
 
northcideCommented:
gonna need more information than "it doesnt work".  be specific
0
 
ibqtiAuthor Commented:
not sure what else to tell you. i checked the windows firewall to make sure that i twas off, i made sure that remote access was still enabled, and i disabled the antivirus as a temporary measure. what else should i check?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
northcideCommented:
are you rdping to a server, desktop?
can you connect to it while attached to the same lan?
what has changed since yesterday?
0
 
ibqtiAuthor Commented:
gotcha! yes to the server.
i'm trying to connect from within the same lan
nothing..that i know of.
0
 
Zenith63Commented:
Did you try restarting the server?
0
 
Rob WilliamsCommented:
Thanks ibqti.
Cheers !
--Rob
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.