Question Locked

Repeated instances of "RPC Server is unavailable"

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I'm hoping a few of you may be able to shed some light on a persistent problem I am having with my file / terminal server ( Win 2003 SP2 Std.Edition ).

Local logins are permitted but domain logons are not. This server is part of a Samba domain. I've scoured the internet but all the solutions I've found don't seem to fix the problem permanently - merely temporarily.

- RPC service is running
- DNS settings are fine
- NetBios TCP/IP Helper service is running
- Time zone is properly set
- Terminal server license is valid & set for "per user cal"

Restarting the Netlogon service & the NetBios TCP/IP Helper service has worked a few times - allowed a couple of domain users to logon.

I've pulled the server off the domain, removed the machine account from Samba & rejoined the domain. This appeared to work for a few users and then I got the dreaded "RPC Server is unavailable" again.

I'm starting to pull my hair out with this situation. Any suggestions would be most appreciated.

Thanks in advance,
cdntech

5 replies

by peconet tietokoneet

If so have a look at the switch, it just might be the switch that is dropping the links.
Just a thought.

by cdntech

It is connected to a switch & the clients are on a separate trunk of the same vlan...however this appears to have occurred only recently.

Still worth checking out. Thanks for the suggestsion.

by cdntech

Okay I'm not certain what I did but the Terminal server appears to be functional again.

- Rebooting the Netlogon service after removing the server from the domain & rejoining it....this appears to have fixed all the user SIDs within the Remote Desktop Users group. Previously they were a mix of unknown questionable SIDs & a few known domain users. Now they are listed as all valid domain users.

I did notice that part of this appears to be DNS related - although I previously said this was fine. Apparently sometimes the DNSlookup was trying to authenticate against a webserver which has the same name as the domain. I added the domain server to the hosts file however I'm not certain whether this resolved the DNS issues or not.

Perhaps this will assist others a little.

Thanks,
Cdntech.

This discussion is closed to new replies.