Multi homed DC

After some network changes, we had to add a second network adapter to
of our domain controllers, for PLC communication. To start with the
added adapter had tcp/ip enabled, but it was disabled because only
another protocol(DLC) was needed for communication with the PLC. This
worked fine for about a few hours.

The domain consist of a PDC(sdr100a) and a BDC(sdr100b) our problem
now is that when we try to map a network drive using NetBios names
from another domain or domain controller, this error occurres:

C:\>net use v: \\sdr100a\c$
System error 121 has occurred.
The semaphore timeout period has expired.
C:\>

After trying to make things better again we are back to only one
network adapter witch is okay for the moment. But the problem
persists. I think the problem is has something to do with the master
browser of the domain. because I can map the drives just fine if I use
DNS names or just IP addresses.
Does anyone have any idea to what is wrong or can point me in the
right direction.

Debug information:

This commands is run from another domain controller.
C:\>browstat status apsdr100
Status for domain apsdr100 on transport \Device
\NetBT_Tcpip_{B9269649-1E75-4B8C-
912D-53FE061D3EA9}
Browsing is active on domain.
Master browser name is: SDR100A
Could not connect to registry, error = 53 Unable to determine
build of br
owser master: 53
Unable to determine server information for browser master: 121
1 backup servers retrieved from master SDR100A
\\SDR100A
Unable to retrieve server list from SDR100A: 121
C:\>

This is the output from the PDC of the domain Apsdr100.
C:\>browstat.exe dumpnet
List of transports currently bound to the browser
1 \Device\NetBT_Tcpip_{B9269649-1E75-4B8C-912D-53FE061D3EA9}
C:\>
.

Relevant Pages

  • RE: Master Browser Problems
    ... Computers can have problems with master browsers etc. ... VPN to a member server but am still getting the same problem ... > Xsol-gold is Domain Controller. ... > Xsol-Exchange will elect itself as a master browser as I would expect ...
    (microsoft.public.windows.server.networking)
  • Unshared deleted printers still appear
    ... We have a Windows Server 2003 Domain Controller that is also the master ... browser. ... The problem is when adding a printer using the add printer wizard ...
    (microsoft.public.windows.server.general)
  • Re: Event id 8032 and dmz
    ... workgroup there shouldn't be any need to reach the domain controller ... and the establishment of who is the Master Browser should take place ... capabilities on these servers as they are probably accessed by the SQL ... "The browser service has failed to retrieve the backup list too many times ...
    (microsoft.public.windows.server.networking)
  • Re: "broken"/missing ACLs?
    ... explains many of the settings that can cause a problem. ... >the domain controller consistently. ... >for the network adapter, bad CAT5 cable, or even a problem with the switch ... >> icon and the ACL name itself is a long string of alphanums. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Server 2008 with Hyper-V - domain controller - Firewall GUIs show firewall ON, but n
    ... This physical computer has only one network adapter and there are virtual machines that communicate with each other, other LAN attached computers and the Internet, so yes, there is a virtual network linked to the NIC. ... I wouldn't recomend using the Hyper-V parent partition as a Domain Controller either. ...
    (microsoft.public.windows.server.networking)
Loading