Urgent .. I think I messed up!

[bradcom]

Hi there ... I am administering a Windows2000 server remotely (remote connection/terminal services) and due to the RPC w32.Blaster.Worm, I installed the Windows 2000 Security Patch: Buffer Overrun In RPC Interface Could Allow Code Execution (file Windows2000-KB823980-x86-ENU.exe).
After rebooting the machine, I can no longer get into the server to administer it. It seems to be up and running, because it's an email server and my email works. Could it have disabled terminal services? Is there anything I can do? Please help.

 

[Stiddy]

form the command line can you:

remote \\servername

this should put you at the command line of the server in question.

From there you can run the command:
net start

To get a list of all running services and make sure terminal services is running.

 

[dellboy]

sorry to barge in but I just tried

remote \\servername

on a W2k box and nothing happens, all I got was an error stating can not find the command.

Tried it as it seems like a really useful tool, what am I doing wrong. I am on the domain and clicked start, run (typed) remote \\servername

I'm interested

Cheers

 

[wbg34]

Go to start --> run --> cmd and hit enter.
Then type remote \\servername.

 

[dholbrook]

Your post is not clear as to being able to access remotely or not being able to log on locally. Which is it? Is it your terminal services that stopped? If so, check on the services on that system to see if the terminservices service has been turned off, and try turning it back on. The SP may have disabled the service. (You have a different problem if you can not log on locally to the server, but the services can also be checked remotely.)

Since you are administering, I assume you have admin access. Can you create a share to the C$ share on the remote server?

I have been reading a few posts with people having RPC related problems after adding SP4 for WIn 2000. You might want to check TechNet at Microsoft.

 

[bradcom]

Thank you very much for the replies, as I'm in a huge bind here. Unfortunately I'm getting the same thing as dellboy. From the command prompt I type ...
remote \\servername (where severname is my server).

I then get this error message ...
'remote' is not recognized as an internal or external command, operable program or batch file.
I'm running windows XP.

 

[bradcom]

Sorry if I was unclear ... I cannot logon remotely, and I do not have access to the server locally. We host our server in Texas, and I'm in Ontario, Canada.
I usually logon using the Start->Programs->Accessories->Communications->Remote Desktop Connection. When I try that now, I get ...
The client could not establish a connection to the remote computer.

The most likely causes for this error are:
1)Remote connections might not be enabled at the remote computer.
2)The maximum number of connections was exceeded at the remote computer.
3)A network error occured while establishing the connection.

 

[Stiddy]

I think that you have to run remote.exe from W2k pro not from a server......

 

[bradcom]

Stiddy ... I'm on XP pro here at work. Our Server is Win2000 Server. If XP pro doesn't have the remote.exe file that your talking about, do you know of any other options?

 

[Stiddy]

DO you have the W2k resource kit? If so it has a command line remote utilty in it? I will show you hao to install it if you have it. Hopefully XP has remote.exe.

 

[bradcom]

Unfortunately I don't think XP has the remote.exe, but the problem is now solved! Thank you guys for helping me out.
I wish I could say "I solved the problem", but all I did was a hard boot.

From my location I can reboot the computer remotely, but that didn't work, so I asked the company that hosts my server to do a power reboot, and voila, everything works now.

Thanks again.

 

[dholbrook]

If the hard boot solved the problem, I would suspect the terminal services did not start the first time (maybe hung for some reason) as sometimes happens with warm boots. Since you can now get back in, I would still go look at all the services to be sure all those required (automatic)have now started, as the problem may still be there in something eles.

HTH

David

 

[MSEDDE]

Some of the command line problems might be from not putting a space where needed or using the wrong slash. I also found that sometimes when the \\servername doesn't work, you can use the IP address and it does.

ME

 

[chriseubank]

RPC services get toasted..

I'm afraid you'll have to reboot

Damn viruses!

Good luck!