• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2369
  • Last Modified:

Remote desktop connection fails

In our LAN I can't connect to one of the servers through remote desktop. This happens intermittently. When I telnet the server on port 3389, I get a response.
Any ideas why this could be happening.

Also on this server the Logonto on the login screen has been disabled.I have to type domain\username with password to logon. How can I enable the logon button.
0
life_j
Asked:
life_j
3 Solutions
 
ts4673Commented:
If the server is in remote administration mode you only get 2 concurrent connections. If you don't logoff but just simply disconnect it leaves the session open using up one of the 2 and after a certain amount of time passes the connecton is reset which frees it up again. the server will still answer on 3389 even though you can't connect.

The logon to can be set in the rdp client including a password, if that doesn't work it is a group policy setting that you have to change to allow it.
0
 
fm250Commented:
is your server win 2003 or xp?
Were you able to connect before?

here are some things to try:
-make sure the remote desktop is enabled and you have added the user(s).
-the firewall (port 3389) is open, if you have it on the default port.
- there is no other service is using that port.
- you don't  have more than 2 sessions already connected. if you setting is the dafault

Also you can edit all the options that you were asking about from the group policy (run: gpedit.msc) if you don't have DC.
0
 
life_jAuthor Commented:
Thanks guys

Its not the problem with the sessions as I just restarted it and no one would be connected.
How can I check which service is using which port
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
fm250Commented:
netstat
0
 
Rob WilliamsCommented:
>>"How can I check which service is using which port"
See # 7 to verify port 3389 is listening.

Some things to check:
1-"allow users to connect remotely to this computer" must be enabled
2-you must be a member of the remote desktop users group (administrators are by default)
3-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"
4-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)
5-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.
6-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"  
7-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
 
prashsaxCommented:
Have you checked the active connections using Terminal Services Manager.

It will show you which connections are running and for how much time.
0
 
Rob WilliamsCommented:
Thanks life_j,
--Rob
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now