Can't Remote Desktop into a machine until I logon locally and then logoff

Windows XP2 to Windows XP2.  If I reboot the target machine, when I try to Remote in I get "The Client Cannot Connect to Remote Computer." But if I walk over to the machine, login, then logout, I can Remote in just fine.

Thats the biggest issue...but I also noticed that if someone is logged into the target machine, and someone else tried to remote the the "Client Cannot Connect..." message comes up again instead of being told someone else is logged and having the option to force them off.

Thanks for any ideas!
synapse88Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
mudassirahmedConnect With a Mentor Commented:
After reboot the target machine,you have to wait for couple of seconds or may be a minute, then do RDP it will work fine (after reboot,don';t do RDP immediately,wait for a minute max)

if user A logged into the machine, and user B tried to login through RDP then it says user A has been logged in to this solution, user B can't force him to logout until the user B has Admininstrator privileages..

Administrator can do the forcefull log off
0
 
Rob WilliamsCommented:
No suggestion on the first item, unless it is due to power management enabled on the network adapter ("allow the computer to turn off this device to save power" -enabled by default)

On the second item, the option to force the user off only exists if the account with you are logging on, is an administrator of they machine. If not they get the message that the machine is in use. Might that be the case?
0
 
mycroftxCommented:
Did you check your Windows Firewall exceptions to make sure Remote Desktop is allowed?  Are you using a different firewall?  If so which and do you have TCP port 3389 unblocked?
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
cbenson7Commented:
Did you try and adding the user to the local users group on the local machine not the domain.  Start them off with administrators rights and if that works add them in the remote users group and remove the admin right and try again.
0
 
synapse88Author Commented:
Ok I have an update on this.

I CAN remote into the machine in question if I wait about 10-15 minutes after a restart.  After letting that time pass, I can remote into it (without having to walk over and login locally).

Any ideas on how to fix it?
0
 
Rob WilliamsCommented:
Try remotely accessing the services management console from a workstation directly after a reboot. If you can access see if all services have started. If not familiar with doing so log on to a workstation as a domain admin, open the local services console, right click on the computer name and choose "connect to another computer".
0
 
synapse88Author Commented:
Thanks for the info
0
All Courses

From novice to tech pro — start learning today.