Cannot connect via RDP after reboot...

Jono

Jono

Jono

Man of Honour
Joined
18 Oct 2002
Posts
13,262
Location
Northallerton/Harrogate
Hi,

I'm having problems with one of the PCs I'm currently working with.
I didn't install windows on it or set it up in any way whatsoever, and on similar PCs in the past (set up by the same sort of people at the company for which I work) I've never had this problem.

The problem is:
After rebooting it, I cannot log in via remote desktop to the PC, until logging into the PC locally.

Has anyone experienced such a problem before and/or have a fix for it.

The PC is running Windows XP Pro, RDP is being done on a local network (192.168.0.X), the account used to log in via RDP is Administrator, and as I said, this is the only such PC (although the hardware may be slightly different/updated this time, the base configuration is as far as I know (could be wrong) identical to previous machines.)
I had a search on the net and one suggestion was changing Terminal Services service to start automatically - it was set to manual initially, but changing to auto hasn't made a difference.

During normal operation this PC will not have a keyboard/mouse/monitor connected to it, and will be controlled via RDP. It will not often need to be rebooted, but that's always a possibility.
It's vital that enabling connection via RDP immediately after reboot is configured somehow, and fast.

Thanks in advance for any info/advice/suggestions.
 
It may have been part of a domain. I/we can take it off that if necessary?. The other such PCs we have are part of the domain - this one has been moved now onto a customer site and isn't directly connected to their network - the others were.

However, it's just part of a LAN right now, only accessed by a computer on that local network. Or should be.

All / both options are checked on the remote tab afaik - will check in the morning to be sure.
 
I'd be checking a few things.

Can you ping the machine before it's logged in?

Is rdp connecting then failing authentication?

Is windows firewall turned on?

Have any specific permissions been set up to allow access in the remote tab?

Is it a static or DHCP IP address? (could another pc have the same IP?)

Are you trying to rdp via an IP or the comp name? (possibly a DNS issue)


Also if it's not going to have a KB, Mouse and Monitor attached you'll probably need to change some settings in the bios to allow it to boot.
 
Andy100 said:
I'd be checking a few things.

Can you ping the machine before it's logged in?
Yes

Is rdp connecting then failing authentication?
No - it's just saying it can't connect to it.

Is windows firewall turned on?
Not entirely sure, don't think so.

Have any specific permissions been set up to allow access in the remote tab?
Not sure will check - what should I be looking for?

Is it a static or DHCP IP address? (could another pc have the same IP?)
Static.

Are you trying to rdp via an IP or the comp name? (possibly a DNS issue)
Nope, IP address

Also if it's not going to have a KB, Mouse and Monitor attached you'll probably need to change some settings in the bios to allow it to boot.
It can boot fine without it :)
Click to expand...


Everything is fine if/once I go and log into it locally. Seems like something needed for RDCing to it is starting when the user logs in, but not with windows. And I've no idea what it could be.
 
I guess it could be worth to see if the RDC services are turned on and running on the PC your trying to connect to. Though all the services run at startup before a user log's on don't they (not totally sure on that bit) so if thats right and they are turned off, they shouldn't suddenly turn on and run if someone logs on?
 
I had a really strange (but sort of similar issue) before. If i left my PC on overnight, when i came back i could not log on locally (no login box). If i RDPed to it then the screen locked box would come up and i could log on as normal. Fixed it by resetting the local security policy and it's been fine ever since.
 
possible cause..

has a wireless card that doesn't setup the ip until it gets into windows

it's probably not wireless, but worth mentioning
 
You must log in or register to reply here.
Back
Top Bottom