RPC Server Unavailable

  • Thread starter Thread starter CB
  • Start date Start date
C

CB

I am having a problem with one computer on my network that
has 2 NIC's. One NIC is connected to my Domain
via DHCP while the other is connected to a local LAN
running some equipment on a private IP range 172.16.x.x

I keep getting an error in the Event log

Event ID: 5719 Source: NETLOGON

No Windows NT or Windows 2000 Domain Controller is
available for domain SUMTER. The following error occurred:
The RPC server is unavailable.

Any Ideas on how to resolve this problem?

I have updated Drivers on Both NIC's
Replaced Network Cable
Windows 2000 SP3
Virus Scan has been kept updated via ePO
 
Make sure that the DNS entires on both NICs only point at the WIndows 2000 DNS server hosting the AD domain. If you point at
any other DNS servers that are unaware of the AD domain DNS zone, you will get this error. If removing these other DNS entries
causes name resolution problems for the secondary network, use a hosts file or create a secondary zone on your Windows
2000 DNS server for the zones that contain the resources you need access to.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Why is that computer also connecting to a local LAN? Is that at the same
time? Check the bindingorder and make sure that the 'domainnic' is on top.

Marina
 
I will check the binding order.

The LAN is used to communicate to a 'line' that operates
various machines robot/PLC/Printer.

I need the other NIC to get the batch jobs from our WAN.
 
I will try that. The LAN is on an entire different Subnet.

LAN = 172.x.x.x and is not part of any AD domain
While the WAN NIC is on 10.x.x.x and is part of an AD
domain.

-----Original Message-----
Make sure that the DNS entires on both NICs only point at
Click to expand...
the WIndows 2000 DNS server hosting the AD domain. If you
point at
any other DNS servers that are unaware of the AD domain
Click to expand...
DNS zone, you will get this error. If removing these
other DNS entries
causes name resolution problems for the secondary
Click to expand...
network, use a hosts file or create a secondary zone on
your Windows
2000 DNS server for the zones that contain the resources you need access to.

Thank you,
Mike Johnston
Microsoft Network Support
Click to expand...
confers no rights. Use of included script samples are
subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread from
 
Back
Top