In
bob said:
I have just started getting this message on a stable
network. I can connect from server out but not thru the
server. Have manually started rpcss and this has not
helped.
With the limited info supplied, and assuming you have AD, the major cause of
this, and usually, this is a sign of using your ISP's DNS servers in your IP
properties. You'll need to remove them if this is the case. Adjust your
clients also. They all need to point to your internal server only.
AD requires DNS, specifically it;s own. All service location info is stored
in DNS. When any service or app requires to connect to a domain resource, it
queries DNS, and the appropriate info is returned. If an outside DNS is
listed in properties, they won't have the answer. Results from this can be
numerous, one of which is RPC server unavailable.
More info on AD and it's DNS requirements:
http://support.microsoft.com/?id=291382
Another cause is going thru a NAT device, if one machine is on a public IP
and trying to communicate internally to a private IP or vice versa, since
NAT cannot support Kerberos, LDAP or RPC.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
