Netlogon Broadcast over IP Subnets (87130)
The information in this article applies to:
- Microsoft LAN Manager 2.1
This article was previously published under Q87130 SYMPTOMS
A router does not pass a netlogon broadcast from a client on one subnet
to a server on another separate subnet separated by the router.
Netlogon requests are not seen by servers even though you can ping the
server's IP address from the client workstation.
Transport protocol: TCP/IP
Network topology: A subnetworked TCP/IP network in which the servers
and the clients are separated by a router and are
not bridged.
CAUSE
The primary domain controller is not on the same IP subnet as the clients
requesting netlogon.
RESOLUTION
Do one of the following:
- Move the primary domain controller (PDC) into the same IP subnet
as the clients requesting the netlogon by performing these steps:
- Change the IP address of the PDC so that it is on the same
subnet. Refer to page 270 in "Internetworking with TCP/IP
Volume I" for a description of subnetting.
- Physically move the PDC to the same segment as that of the clients
requesting the netlogon.
-or-
- Do the following:
- Put a backup domain controller on the client's IP subnet
requesting the netlogon.
- Connect it through a dedicated link to the primary domain
controller in that domain.
- Use NetBEUI as the protocol on the dedicated link.
-or-
- Bridge the client's IP subnet and the server's IP subnet. This
allows all broadcasts on the IP subnet to be passed to the other
subnets. This method is not recommended.
Notes: Microsoft did not ship a TCP/IP transport stack with LAN Manager
version 2.0. Some customer sites might use a different TCP/IP transport
stack (for example, stacks from Wollogong or Hewlett-Packard). If these
transport stacks are not NDIS compliant, they will not work; if they are
NDIS compliant, they are not guaranteed to work.
| Modification Type: | Major | Last Reviewed: | 9/30/2003 |
|---|
| Keywords: | KB87130 |
|---|
|