can't connect via RDP

Sie

SWM wrote:

I have had a few servers do this as well, RPC server is unavailable. aarggh

Does anyone knows how to overcome it with out a server restart.

Another great way to reboot a remote server with out the shutdown command (i have had servers that dont respond to it) is via ADUC, right mouse click on server name, manage, action, properties, advanced, settings, shutdown, select "restart" and "if hung".

Goodluck

I havent tried rebooting them that way, must give it a go.

Unfortuantly i think binarysoul said this was a workgroup PC?.....

snadam

Sie wrote:

RPC Service can do this from time to time, appears to 'hang' when in a started status unfortunatly what I usually do is reboot the system.

If you can schedule tasks on the server just schedule a shutdown -r -f. However you may need to specify the Reason codes.

Note: shutdown /r /m \\ComputerName/t 60 /d p:0:0 to initiate a remote planned restart. Other (Planned)

just about to suggest that. Sounds like some service/s are hung when you bounced it.

also, you can also adjust the /t switch to initiate how long the timer is (default is 30 seconds, you can set it to 1 so you dont have to wait) However, it might be best to leave it be.

binarysoul

This is becoming a classical problem!

I was able to start RPC (it was stopped).

Now the silly server won't respond to shutdown command to restart itself. I tried task scheduler and PSshutdown from internalsystem, no go. psshutdown tells me server will reboot after 20 second, but server is still up.

Goldmember

Did you ever check if there were RDP sesssions being used on the server with

qwinsta /server:servername



Your probably past that now since you rebooted the server and it hung.

Sie

binarysoul wrote:

This is becoming a classical problem!

I was able to start RPC (it was stopped).

Now the silly server won't respond to shutdown command to restart itself. I tried task scheduler and PSshutdown from internalsystem, no go. psshutdown tells me server will reboot after 20 second, but server is still up.

How about the remote shutdown command? Does this do the same??

Silly question but since you restarted RPC have you tested Remote Desktop again?

Attempt shutdown -i for a GUI

mgeorge

cisco_trooper wrote:

Get physical access to the device and insure the remote desktop service is running.

Physical access is not required to check to see if this service is running.

Use your standard management MMC and connect to the remote machine.
Right click "My Computer" then click manage
Then right click "Computer Management (Local)" and click "Connect to another computer..."
you can browse for the computer, use the DNS name or the IP address

Scroll down the list and check for "Terminal Services" and see if its started.
Keep in mind that Terminal Services are dependant on the RPC servce.
Use remote event log viewer to check and see if any service failed during startup.

You can use start and stop services remotely using NETSVC.EXE provided on the resource kit.
http://www.cramsession.com/articles/files/stoppingstarting-services-182004-1605.asp

Hope this helps

blargoe

It sounds like it hung up while shutting down and left some required services either down or trying to shut down. Unfortunately, the server probably needs to be buttoned

Did you try
shutdown -r -f -m \\machinename -t 0

This command will shutdown a remote machine, -f forces all applications to end, -t 0 means now. If this doesn't work, you probably have to button it.

Sie

Can we ask why you cannot physically access the server or have someone do it for you??

binarysoul

mgeorge27 wrote:

cisco_trooper wrote:

Get physical access to the device and insure the remote desktop service is running.

Physical access is not required to check to see if this service is running.

Use your standard management MMC and connect to the remote machine.
Right click "My Computer" then click manage
Then right click "Computer Management (Local)" and click "Connect to another computer..."
you can browse for the computer, use the DNS name or the IP address

Scroll down the list and check for "Terminal Services" and see if its started.
Keep in mind that Terminal Services are dependant on the RPC servce.
Use remote event log viewer to check and see if any service failed during startup.

You can use start and stop services remotely using NETSVC.EXE provided on the resource kit.
http://www.cramsession.com/articles/files/stoppingstarting-services-182004-1605.asp

Hope this helps

Thanks! this was helpful. Thanks for everyone's suggestion.

I've narrowed the problem to error, "Win32: RPC Server unavailable". When I remotely accessed MMC on the server and right clicked on "Computer Management" I got the above message saying RPC unavailable.

Under services, RPC is "Started" and there is no option to stop or restart it. I suspect the server is hang when trying to reboot. I don't think the server actually rebooted. Is there any remote utility I can checkc server uptime? I know on local machine, we can use systeminfo.exe.

I will keep you folks posted. Unfortunatly, due to some beuracratic processes, physical access is a month-long process

sprkymrk

Within your local System Info, you can go to VIEW>Remote Computer.

However, if the RPC server is unavailable it probably won't work.

blargoe

OK then, it's hung. You will have to get physical access or find someone else that can do it for you.

binarysoul

sprkymrk wrote:

Within your local System Info, you can go to VIEW>Remote Computer.

However, if the RPC server is unavailable it probably won't work.

You're right. It didn't work. It told me network path not found and/or Windows Management Instrumentation isn't installed on target server.

undomiel

RPC problems usually result in a reboot, but are not always fixed by it. I haven't had to deal with it on a server yet but in XP I've run across it many times. Sometimes it is just a clock that has gone out of sync (sometimes by 99 years) and other times it has been a corrupt WMI repository. Which is sometimes fixed by re-registering the components and other times I've had to resort to a repair install.

binarysoul

undomiel wrote:

Sometimes it is just a clock that has gone out of sync (sometimes by 99 years)

Now that mention this, I remember seeing in event logs saying date had changed by 29 days. Unfortunately, I didn't get a chance to check date/time.

The server is now pingable, but is no longer showing under Workgroup with other servers that are part of the Workgroup

Tyrant1919

Reinstall OS. :^)