Discussion Locked

DHCP Clients not logging onto domain.

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a growing problem where new 95/98 DHCP clients, when booted, do not prompt for the Network Logon. If I Log off then log back on, or if I use "Release All" then "Refresh All" in WINIPCFG, it works correctly. I have recently created a new PDC running DHCP to resolve this to no avail. PLEASE HELP!

11 replies

by mr_fixit

Also, old clients, when renamed (Network Properties) start having this same issue.

by kza_iran

please send me your complete pic of network properties dialog tabs. do u have "client for microsoft network" as ur "primary network logon"? did u configure logon validation on "client for microsoft network" properties dialog?
sincerly yours,
k.zonouzi ahmad

by mr_fixit

Yes, here is the complete config:
Client for MS Networks, Log onto NT Domain (Specified)
3Com NIC
TCP/IP
File and Print Sharing

Identification: Machine Name specified, Domain Specified, User Name as the description.

Access Controlis set to User Level with the Domain specified.
{{The rating scheme here is limited. Helped or not.}}

by ezmoney

Really need more info on how you are setting the 95/98 machines up. Are you requiring any authenication? If so make sure you have selected logon on to Windows domain and identify the domain in network setting. Then if you are not using group policy you need to change the registry setting. Open pole edit and and set options for local computer under logon. There are more setting you may or may not want. I use this and it works great. If you want more info e-mail me at rodneyw@jep3.state.fl.us

by mr_fixit

Yes, here is the complete config:
Client for MS Networks, Log onto NT Domain (Specified)
3Com NIC
TCP/IP
File and Print Sharing

Identification: Machine Name specified, Domain Specified, User Name as the description.

Access Control is set to User Level with the Domain specified.

{{The rating scheme here is limited. Helped or not.}}

by curious_george

Win9x clients need NetBIOS to identify the domain controllers on a network.

If you are running a WINS server, the DHCP server should have the appropriate records pointing the clients to the WINS server.

If there is no WINS server, all clients should be configured to broadcast mode. On a small network broadcast traffic may be tollerable, at some point it will become excessive and a WINS server should be placed into service.

Win9x clients must be configured for NetBIOS over TCP/IP.

It sounds like you have incorrect NetBIOS information being delivered to the clients, you should review server and client settings in detail, including reviewing any WINS database records that may be present.

by deltree

We had a similiar issue with our roaming laptop users. When they went to a different subnet they did not receive a new IP from DHCP, instead, keeping their old one from a different subnet. Using release all and renew all worked every time but at the annoyance of the end user.
It turned out to be the 'spanning tree' protocol on our Nortel switches. When active, there is an autodiscovery period when new devices attach. The device can send a (DHCP) broadcast through the switch, but the switch will not send any broadcasts back through that port until the autodiscovery phase is complete.
We disabled the protocol on all our switches which fixed the problem.

This discussion is closed to new replies.