I'm getting a stream of Netbt 4320 errors in the event log of a multihomed Win2k server. They don't appear to be harmful but its preferable to have a clean Eventlog rather than one filled with errors.
Part of the error message states that "Another machine has sent a name release to this machine possibly because a duplicate name has been detected on the TCP network...".
Microsoft in support article Q131740 very helpfully state "Other computers on the network may indicate that the multihomed computer's second card is in conflict with its first. Those computers will then send the name release message." AND THEN WHAT??? HOW DO YOU STOP THIS???
The server is dual homed with nic 1 configured with "Client for MS Networks", "File & Print Sharing..." and IP protocol. It has a static IP address and no default gateway. It doesn't point to any DNS servers (uses Hosts file) and has the setting "Register this connection's addresses in DNS" set (probably incorrectly because its in an NT4 Domain and not Win2k). It doesn't point to any WINS servers but has LMHOSTS enabled and NetBIOS over TCP/IP set.
The second nic only has the IP protocol set with a static IP address on a different subnet to nic 1 AND a default gateway. It doesn't point to any DNS servers (uses Hosts file) and also has the setting "Register this connection's addresses in DNS set" (again probably incorrectly). It doesn't point to any WINS servers but has LMHOSTS enabled (probably incorrectly) and has the setting "Use NetBIOS setting from the DHCP server" (I suspect that this should be 'Disable NetBIOS over TCP/IP' as we don't need NetBIOS on this nic and also don't use a DHCP server).
For subnets available from nic 1 a whole bunch of static routes are set.
DOES ANYONE KNOW OF ANY REGISTRY SETTING OR OTHER CONFIGURATION CHANGE WHICH WOULD ELIMINATE THIS PESKY MESSAGE?
Thanks in advance.
Part of the error message states that "Another machine has sent a name release to this machine possibly because a duplicate name has been detected on the TCP network...".
Microsoft in support article Q131740 very helpfully state "Other computers on the network may indicate that the multihomed computer's second card is in conflict with its first. Those computers will then send the name release message." AND THEN WHAT??? HOW DO YOU STOP THIS???
The server is dual homed with nic 1 configured with "Client for MS Networks", "File & Print Sharing..." and IP protocol. It has a static IP address and no default gateway. It doesn't point to any DNS servers (uses Hosts file) and has the setting "Register this connection's addresses in DNS" set (probably incorrectly because its in an NT4 Domain and not Win2k). It doesn't point to any WINS servers but has LMHOSTS enabled and NetBIOS over TCP/IP set.
The second nic only has the IP protocol set with a static IP address on a different subnet to nic 1 AND a default gateway. It doesn't point to any DNS servers (uses Hosts file) and also has the setting "Register this connection's addresses in DNS set" (again probably incorrectly). It doesn't point to any WINS servers but has LMHOSTS enabled (probably incorrectly) and has the setting "Use NetBIOS setting from the DHCP server" (I suspect that this should be 'Disable NetBIOS over TCP/IP' as we don't need NetBIOS on this nic and also don't use a DHCP server).
For subnets available from nic 1 a whole bunch of static routes are set.
DOES ANYONE KNOW OF ANY REGISTRY SETTING OR OTHER CONFIGURATION CHANGE WHICH WOULD ELIMINATE THIS PESKY MESSAGE?
Thanks in advance.
