DHCP Problems?? 2

[wolf2x]

We had a problem with getting a workstation to join the domain AND to use dhcp. If I tried to tell it to use dhcp, it would give us the error that no domain controller could be found.

I did try to release/renew the ip address but that did not help. IPCONFIG/ALL just returned an ip address of 0.0.0.0. I reapplied the latest service pack but still nothing....

It did join the domain AFTER I assigned a static IP. But, of course I dont want my workstations to have static ip's.

Does anybody know why this problem is happening?

Thanks in advance,

Abel

 

[kjonnnnn]

Using DCHP, did you give it a gateway address and WINS addresses. Even if DHCP is giving those out, sometimes they dont "catch"

 

[wolf2x]

On the dhcp server, we do have the gateway address assigned.

For wins, I have the workstation to 'enable dns for windows resolution'.

BTW, we are running NT 4.0 workstation and server.

 

[hsablan]

I have run into this problem before. What I did to get back on is to change from a domain type network to a workgroup. I then changed it back again. Make sure you create a new account when you change back the type of network to domain. Hope this works for you.

 

[mbhandari]

Hi,
Are you ding the same across the wan or lan?
If you are not getting a DHCP IP address It is clearly DHCP problem.
Try stopping the DHCP and starting again.
It may possible your PC not sending the DHCP request.
Try packet sniffing to check the DHCP req-responce.
Until unless you don't get IP your WS not going to join Domain( of-course it may if you have some other protocol)
-bhandari

 

[dxd]

Yes...focus on DHCP not domain login as bhandari indicates. The first troubleshooting step you did by using a static IP confirmed that the protocols and OS are working properly.

Next we must determine why is this PC not getting dynamic IP. Have you checked the event log on the Workstation?
What NIC is in the box, try a another. I am not sure if any error would be displayed, but duplicate MAC address' on the same network could prevent dynamic IP assignment.

I have also seen timing issues with auto settings on both the NIC and switch. Try setting the appropriate settings on the NIC. For instance, set the speed, duplex, and media type to the values supported by the switch it is connected to. Doug
dxd_2000@yahoo.com

 

[wybnormal]

Make sure you are not crossing IP subnet boundries. DHCP is broadcast based and will not be routed between subnets unless the router has been configured to pass the broadcast packets. The fact a static worked says the links are fine. Something is preventing ports 67 and 68 from getting here and there.

Mike S

 

[wolf2x]

The workstation is on the same subnet as the DHCP server.

I had tried a different nic card. I tried a 3com 905b and a 3com 905c. Same result. The errors that show up within event viewer are the ones dealing with not being able to get a lease from dhcp server.

Now, both cards came out of workstations that had one time or another been on the network. If it is a duplicate MAC address problem, wouldnt I get the error...something about 'duplicate names'? Instead of that error, I just get 'no domain controller could be found.'

 

[dlnalaeh]

You could try turning DHCP logging on (SP4 & higher on the DHCP server) under DHCP Manager, Server Properties, General Tab. It writes a log on DHCP attempts and whether they were a RENEW, Assign, or NAK. It keeps a weeks work on the server. I also set conflict attempts to 1 so that a machine who happens to have the IP address DHCP is trying to give at the moment for whatever reason doesn't prevent DHCP from giving the requesting machine a different one. It pings the one it wants to give, if it gets an answer it flags that IP as a conflict and assigns a new one to the requestor. Otherwise the machine wouldn't get one.

Set it to DHCP and reboot before trying to join the domain, make sure it is getting an IP before you try to join the domain. It should get an IP regardless of the domain membership.

 

[wolf2x]

Okay...with your guys help, I got it to work the right way. I deleted the computer account out of Server Manager. Then, I moved the workstation to workgroup and at the same time told it to use dhcp. Rebooted. Sure enough, it was able to lease an ip. Moved it back into the domain, creating the computer account....no problem.

Thanks again, I appreciate everyone's help.