Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

remote access won't work after reboot

Status
Not open for further replies.

kjohnson530

IS-IT--Management
Mar 26, 2006
28
US
We recently rebooted a server remotely and now we cannot get remote access without first going directly to the system and rebooting it.

Terminal Services manager does not show any session whether active or inactive other than the console.

My guess is that a service failed to start. Can anyone tell me what that service might be.?

 
Assuming it is a service: If you can't reach it via terminal services, the first service I would look at is the terminal services service. If you can't reach it at all, I would check the server service.
 
Terminal services relies on the RPC service and of course Terminal Services itself
I have had this happen with Windows 2003 64-bit. I haven't had the chance to contact MS about it, but in most cases it requires a system reboot via Remote Processor (RILOE or RSA). There is nothing logged in the event log
In certain cases I have even had to resort to disabling the Windows firewall (even though RDP is allowed)because of these issues.
 
Run the Internet Connection Wizard and then restart all of your services in IIS.

This has fixed the problem for me.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top