General discussion

Locked

Log on problems with Multi-homed Server

By jyimcse ·
NT 4.0 Server with two IP Addresses on one nic. 206.x.y.z is primary and 10.x.y.z is the secondary. No WINS. Clients on the LAN on the 10.x.y.z network are unable to log on to the domain. Error returns no domain controller found or available. I can probably change the order of IP address to resolve, but is there an issue with secondary IP address and netlogon?

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Log on problems with Multi-homed Server

by cdcents In reply to Log on problems with Mult ...

You may have already tried this but it is always good to check if you haven't.
Try to ping/tracert a workstation on the 10.x.y.z network from the multi homed server. By default all traffic would be routed to the 206.x.y.z network since that is theprimary. If you find that the traffic is being routed to the 206.x.y.z network then you may have to add static routes for the other network. syntax would be
ROUTE ADD 10.x.y.0 10.x.y.z
(I am presuming a full Class C subnet hence the 0 in the last octet. Please change as necessary). If this helps and you need more info I will check this posting.
CD

Collapse -

Log on problems with Multi-homed Server

by jyimcse In reply to Log on problems with Mult ...

I am able to ping the server with the secondary, 10.x.y.z, IP. I have implemented LMHOSTS so that I can ping by netbios name. The workstations can see the server, but can't log on.

Collapse -

Log on problems with Multi-homed Server

by cdcents In reply to Log on problems with Mult ...

How about pinging the workstation from the server? Another possibility could be the bindings on the NIC. Check to see if NetBEUI is bound to the 10.x.y.z

Collapse -

Log on problems with Multi-homed Server

by jyimcse In reply to Log on problems with Mult ...

Getting close. NetBeui is bound. But why would it affect netlogon from a workstation using IP only.

Collapse -

Log on problems with Multi-homed Server

by cdcents In reply to Log on problems with Mult ...

I need clarification. What exactly do you mean by "workstation using IP only'. Is NetBEUI not bound on the workstation. If not then binding NetBEUI is probably your solution

Collapse -

Log on problems with Multi-homed Server

by jyimcse In reply to Log on problems with Mult ...

Thanks for your efforts

Collapse -

Log on problems with Multi-homed Server

by shmaltz In reply to Log on problems with Mult ...

please read the following MS KB articles:
Q221210
at
http://support.microsoft.com/support/kb/articles/Q221/2/10.ASP?LN=EN-US&SD=gn&FR=0&qry=multihomed%20PDC&rnk=5&src=DHCS_MSPSS_gn_SRCH&SPR=MSALL
Q181774
at
http://support.microsoft.com/support/kb/articles/Q181/7/74.ASP?LN=EN-US&SD=gn&FR=0&qry=multihomed%20PDC&rnk=9&src=DHCS_MSPSS_gn_SRCH&SPR=MSALL
Hope this helps.

Collapse -

Log on problems with Multi-homed Server

by jyimcse In reply to Log on problems with Mult ...

The articles are interesting. The Servers are not considered multi-homed because there aren't two NIC's. One nic with primary and secondary ip addresses. I guess the only solution is to switch the addresses or get ride of one. Since the lateris the ultimate goal anyway, I will resolve this, but I wanted to know why it wasn't working.

Thanks for you help

Collapse -

Log on problems with Multi-homed Server

by jyimcse In reply to Log on problems with Mult ...

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums