Return to index
MS specifically recommends against using a multihomed machine as a PDC or any potential Master Browser (e.g. BDC), because of the browsing problems this causes. Your best bet is to rearrange your network so that your PDC is single homed and whatever machine you use as a router cannot act as a Master Browser.
If you can't do that, the following example should work. It describes a 2 segment LAN, using multihomed PDC as a router, WINS server, and DHCP server. I haven't tested it, but there is now a KB article (it wasn't there when I wrote this) that describes the same setup.
segment1 --- NT router --- segment2
<all masks are 255.255.255.0, unless noted>
NIC1: 192.168.100.1 (segment1)
NIC2: 192.168.200.1 (segment2)
Both default gateways blank.
WINS: 192.168.100.1, 192.168.100.1
IP forwarding enabled.
NetBIOS bind to NIC2 is disabled. <----- IMPORTANT!!
WINS Server implemented
Router (03): 192.168.100.1
Router (03): 192.168.200.1
WINS (44): 192.168.100.1, 192.168.100.1
Node type (46): h-node (08)
All other machines on both subnets are configured as DHCP clients.
1) If you have any devices that require static IPs, either exclude these IPs from the DHCP scope or create a reservation for them.
2) Notice each segment appears on a different IP subnet and that the clients on each subnet have their Default Gateway set the IP of the NT router's NIC on that subnet.
3) Disabling the NetBIOS bind to all but one interface on the PDC makes the machine single-homed, as far as NetBIOS is concerned. This allows you to avoid the problems associated with multihomed PDCs. However, it also means that all NetBIOS connections must be made to the one 'enabled' interface. You will need to make sure that all machines needing to make NetBIOS connections to the PDC resolve the name (PDC or domain) to the NetBIOS enabled IP. With WINS, this will be automatic. If you use any static tables (e.g. lmhosts), you must manually control this.