DHCP Server will not issue IPs on initial introduction to domain.

[soonerkid]

When I attempt to introduce a new workstation to the domain, DHCP will not initialize with the workstation in question. I must place the machine onto the domain with a static IP and reboot. I then can switch to DHCP, reboot once more, and all is well.

This really is no big deal until I try to introduce a jetdirect external print server that has no initial user interface. It relies on DHCP on first call ...then you can Telnet and assign statics or whatever you like.

I know the two problems are linked ...I am just not sure where the problem lies. Suggestions will be greatly appreciated. Thanks.

 

[F1lby]

Sorry, please explain a little more.
Is the DHCP server offering IP addresses to other machines OK?
WHat sort of client is it that CANT get an IP address from the DHCP server?

 

[soonerkid]

F1lby,

Thanks for the response! The clients are all NT 4.0 Workstations. SP6 installed all the way around.

DHCP will not give a lease to ANY new workstation when first brought onto the domain. A static IP must be assigned the first time it is introduced. If a static IP is used, the server will recognize it and welcome it to the domain.

After the workstation is initially introduced, I can switch from static IP to DHCP and it will function normally from that point on. Leases will expire and renew as assigned.

I need to get DHCP to throw that initial IP when workstations or JetDirect Print Servers are introduced. The print servers are external HP 500X and they seem to rely on DHCP to start speaking to the network.

Hope this clarifies.
Thanks.

 

[F1lby]

OK, joining a domain is a red herring..... Domain security has nothing to do with DHCP leases. Don't forget that domain security CANT work until the client has a valid IP address. All normal networking requires a proper IP address.

ANY client can get a lease from a DHCP server (for instance Windows, Linux, Jet Direct, Mac, Beos, etc etc). Then, once an IP address has been assigned, the client can start to do other networking jobs such as authentication, etc.

How do you know the client does not get a lease?

Ok, so get an NT workstation client, configure it to pull an address from a DHCP server and start it up. Go to command prompt and do IPCONFIG /ALL and what do you get? What are the values that have been given?