Can't Login to W2003 Server - Can't Manage Remotely (RPC Busy)
Hi,
I have a serious problem here.
There are a couple W2003SP1 servers in the network that I can't login to. The symptoms in all of them are the same: It just feezes after entering uname and pw. I know, though, that the server is running its applications since I have client PC that connect to it for a certain application.
And if I try to connect to it remotely (with either name or ip addres) using Computer Manager, I get this message:
Computer \\172.a.b.c can't be managed. The RPC server is too busy to complete this operation.
Nothing that I'm a aware of has changed in these servers. What did change is that a new DC was installed in the network by th IT people replacing the previous one. This annoying behaviour started 2-3 days after that.
H E L P ! ! !
I have a serious problem here.
There are a couple W2003SP1 servers in the network that I can't login to. The symptoms in all of them are the same: It just feezes after entering uname and pw. I know, though, that the server is running its applications since I have client PC that connect to it for a certain application.
And if I try to connect to it remotely (with either name or ip addres) using Computer Manager, I get this message:
Computer \\172.a.b.c can't be managed. The RPC server is too busy to complete this operation.
Nothing that I'm a aware of has changed in these servers. What did change is that a new DC was installed in the network by th IT people replacing the previous one. This annoying behaviour started 2-3 days after that.
H E L P ! ! !
itcoza
The only thing I can think of at this point is to get an application like DameWare to gain access to the services on the servers and then check to see that your RPC services are in fact running. http://www.dameware.com/
ASKER
How, if we can't even get to that server?
Not even \\servername.
Not even \\servername.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you have enabled remote desktop for administration on those servers, you could try to access them that way as well. However, it sounds very likely to me that the RPC service is misbehaving on these servers for some reason, in which case a reboot is the only thing that will fix it.
ASKER
Can't get there any way. Can't reboot because of the production application that is running ok there.
I'm stuck!
I'm stuck!
I forgot to mention (but hypercat did) the RPC service might be failing and the only way to fix it is rebooting.
Reboot on the weekend ;) We're almost there!
I have setup all servers to reboot on Sundays, thus preventing errors through the week.
Reboot on the weekend ;) We're almost there!
I have setup all servers to reboot on Sundays, thus preventing errors through the week.
ASKER
:-)
LOL, I guess we'll receive a response from you on Monday.
Hey, drotkopf, I hope you have a good weekend, and let us know what happened. ;-)
ASKER
Thanks!
ASKER
After rebooting, we applied MS patches, installed AV and found a few things.
I suppose it's working now. Glad to know everything was fixed!
ASKER
Thanks!