RPC error on Windows Server 2003 R2 Standard SP2 Terminal Server
Windows Server 2003 R2 Standard SP2 Terminal Server
Logon rejected for DOMAIN\username. Unable to obtain Terminal Server User Configuration. Error: The RPC server is unavailable.
Approximately 2-3 times per week for the past several months my client has had to reboot their primary terminal server due to "RPC Server Unavailable" errors. This happens at any time of the day; usually when there is very little, if any, activity. A reboot is the only thing that clears it up until the issue occurs again a day or three later.
What I've done so far:
- Remove/Readd server to the domain
- Add entry in hosts file for DC
- Verify all DNS-related info is setup properly on server
- Hope, pray, beg for this problem to go away
As I do not work in the same site as the server I have been unable to even attempt to access the console prior to the client rebooting it. Therefore I am not sure if any RPC-related services have stopped and caused the RPC error. However, there is nothing in any of the Event Logs stating anything remotely related to a service being stopped or any other error occurring before the RPC error kicks in.
I've probably read every post on EE that has anything even remotely related to this issue and tried most, if not all, of the suggestions made however none of them have helped me fix the actual root issue.
Logon rejected for DOMAIN\username. Unable to obtain Terminal Server User Configuration. Error: The RPC server is unavailable.
Approximately 2-3 times per week for the past several months my client has had to reboot their primary terminal server due to "RPC Server Unavailable" errors. This happens at any time of the day; usually when there is very little, if any, activity. A reboot is the only thing that clears it up until the issue occurs again a day or three later.
What I've done so far:
- Remove/Readd server to the domain
- Add entry in hosts file for DC
- Verify all DNS-related info is setup properly on server
- Hope, pray, beg for this problem to go away
As I do not work in the same site as the server I have been unable to even attempt to access the console prior to the client rebooting it. Therefore I am not sure if any RPC-related services have stopped and caused the RPC error. However, there is nothing in any of the Event Logs stating anything remotely related to a service being stopped or any other error occurring before the RPC error kicks in.
I've probably read every post on EE that has anything even remotely related to this issue and tried most, if not all, of the suggestions made however none of them have helped me fix the actual root issue.
dmorrisroe
have you done any driver updates? Try uninstalling the NIC then reboot, forcing the NIC to be reinstalled.
check all drivers and Service Packs and make sure you are up to date. Do you have Antivirus on the Server if no just run a quick online scan
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Any driver updates are only those available through Windows Update. I have read that the NIC drivers could be at fault however I have not gone out and looked for updated drivers for them. I just checked the list of updates installed through WU and did not find any NIC drivers listed.
There is AV on the box: Trend Micro's latest version. It is up to date and hasn't reported any issues.
I would rather leave SP2 in place as I have other clients running it on their Terminal Servers without any issues.
The box is a Dell PE1950 with Broadcom BCM5708C NetXtreme II GigE NICs. Only the first NIC is enabled.
There is AV on the box: Trend Micro's latest version. It is up to date and hasn't reported any issues.
I would rather leave SP2 in place as I have other clients running it on their Terminal Servers without any issues.
The box is a Dell PE1950 with Broadcom BCM5708C NetXtreme II GigE NICs. Only the first NIC is enabled.
We have a ticket open with Microsoft as this is indeed an issue introduced with SP2. I would definitely try removing SP2 as a test and if you are not happy, simply add it again.
But I am almost certain you issue will be gone.
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
But I am almost certain you issue will be gone.
Claudio Rodrigues
Microsoft MVP
Windows Server - Terminal Services
ASKER
Per my client, this same issue existed on their former terminal server which was running W2K3 SP1 prior to being completely rebuilt when it was moved to a different role. This morning I updated the NIC driver on the primary TS to the latest version available through Dell so we're back in "wait and see" mode again. If it fails to fix the issue I'll try pulling SP2 out and waiting again.
ASKER
The NIC driver update appears to have kept this issue from happening so frequently however does still occur. SP2 is going to be removed and then we wait again...
ASKER
The removal of SP2 from both terminal servers appears to have truly "fixed" this problem. I'm going to give it another week to make me feel even better about the whole thing. As long as all is still well then this question will be closed and points awarded to tsmvp.
ASKER
This appears to have done the trick although I never claim victory as it just seems to push karma too far... Thank you for your help!
I am having this same problem as well. Do you mind me asking how you uninstalled SP2?
I am having the same issue on a W2k3 Terminal server with only SP1 installed. SP2 has not ever been installed on this box.
Anyone else seeing this as an issue other than SP2?
Anyone else seeing this as an issue other than SP2?
I'm getting the same error on Win2003 server and I don't have SP2 installed. Haven't ever had it installed.
