RPC server unavailable or domain not found
Hi All,
I have 2 pairs of virtual servers on vmware esx. One pair is a sbs2008 with a server 2003 terminal server, the other pair is sbs2011 also with a server 2003 terminal server.
The 2 pairs of virtual servers have nothing to do with eachother, and they are on different networks.
The last couple of weeks I sometimes get an error on the terminal server stating "the RPC server is unavailable" when trying to log on. Sometimes i also get the error "the specified domain either does not exist or could not be contacted".
Any help is welcome.
Regards
I have 2 pairs of virtual servers on vmware esx. One pair is a sbs2008 with a server 2003 terminal server, the other pair is sbs2011 also with a server 2003 terminal server.
The 2 pairs of virtual servers have nothing to do with eachother, and they are on different networks.
The last couple of weeks I sometimes get an error on the terminal server stating "the RPC server is unavailable" when trying to log on. Sometimes i also get the error "the specified domain either does not exist or could not be contacted".
Any help is welcome.
Regards
netballi
Try restarting the Site Server Content Deployment (CRS) service.
ASKER
When it happens again I will try that.
Another symptom when this happens is that I can reach the terminal server from the dc, but cant reach the dc from the terminal server.
Regards
Another symptom when this happens is that I can reach the terminal server from the dc, but cant reach the dc from the terminal server.
Regards
ASKER
It occurs again. I want to try what you said, but there is no Site Server Content Deployment (CRS) service.
ASKER
Can anyone help?
I also get errors from a monitoring tool (on the domain controller) like this one: Connection could not be established (Port Error 135: RPC Server not accessible
It's not happening always. Maybe twice per day now. Most of the time there are no problems.
Thanks for your help.
Regards.
I also get errors from a monitoring tool (on the domain controller) like this one: Connection could not be established (Port Error 135: RPC Server not accessible
It's not happening always. Maybe twice per day now. Most of the time there are no problems.
Thanks for your help.
Regards.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No I dont. Is that necessary?
It's recommend, depending upon usage, memory can become fragmented, memory leaks in applications etc
ASKER
Ok, I will try that for a couple of days. I'll schedule a reboot every night.
You should look at the event log for error related to this issue.
Maybe the problem could be at the sbs server, have you tried to restart the active directory service
sc stop ntds
and then
sc start ntds
and try again the connection from terminal server.
Maybe the problem could be at the sbs server, have you tried to restart the active directory service
sc stop ntds
and then
sc start ntds
and try again the connection from terminal server.
ASKER
Hancocka, I'v scheduled a restart for the last 3 days, but the problem persists. But I have to admit that it occurs less often.
Serchlop, I cant see any events in the eventlog of the sbs server when th problem occurs.
Serchlop, I cant see any events in the eventlog of the sbs server when th problem occurs.
ASKER
Hi All,
I see one thing that maybe contributing to this problem.
These are Vmware virtual machines. And I see that the CPU Ready percentage is higher than on other VMs. In some cases it goes up to 40 %!
Can this be the cause?
Regards,
I see one thing that maybe contributing to this problem.
These are Vmware virtual machines. And I see that the CPU Ready percentage is higher than on other VMs. In some cases it goes up to 40 %!
Can this be the cause?
Regards,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
CPU ready times were too high on this vm's. That was causing this.