Admin password change, no DHCP available

[mojo31]

We just changed our admin password. We have users who have been out for weeks come back and not be able to log on to the network. They dont get an IP address. Also users from another trusted domain cant log on for the same reason. Any idea why?

 

[ricpinto]

Check your network connectivity. At least the workstation can get an ip address when you logon locally.

 

[mojo31]

Network is fine, or we'd have problems all over the shop, and we've determined that if you set the machine in question with a static IP addy it connects fine.

 

[OverDrive]

Look at your Eventvwr and check out your DHCP settings...

Since your static works fine, and the other users have been gone for a while... this is the first thing I would check...

gluck!
Chance~

 

[GlenJohnson]

Have you tried ipconfig /release - renew? Do the problem machies get any ip's, even incorrect ones?

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

TTinChicago

http://www.johnsoncomputers.us

 

[mojo31]

it seems like machines that had leases b4 the change was made were fine, but trying to introduce something new to the network wont pick an IP up. Tried ipconfig /release, /renew but it comes back with "Cant find DHCP server"
we are getting NACK's in the logs, for machines from other networks logging on to our which you would expect.

 

[OverDrive]

Stop and Start the DHCP service...

That would be your first step... I would even possibly bumb the server if you can?

Gluck!
Chance~

 

[GlenJohnson]

Try adding a hosts file to the problem machines just to test it. Can you ping the server?

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

TTinChicago

http://www.johnsoncomputers.us

 

[GlenJohnson]

What happens if you change the password back?

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

TTinChicago

http://www.johnsoncomputers.us

 

[mojo31]

Maybe the password change was a red herring....
We have a range with 1024 (1023 useable)addresses, with some exclusions, we have 760 odd adreses available. It seems that it dishes out one address, and then it wont dish another out. As soon as we release it from one machine, do a ipconfig /renew on another the new machine picks it up, we also have DhcpServer error 1009. We have plenty of addresses left (32% in use), so its not that. Giving any machine a static address works fine too Is it possible that the DHCP server has become coorupt? There are also JET info messages 8, 16 and 69. Anyone have any info in regards to this.

 

[GlenJohnson]

"1009 DHCP Error The DHCP service encountered the following error while cleaning \r\nup the pending client records: %n%1\r\n" What happens when you do a cold boot of a problem client?

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

TTinChicago

http://www.johnsoncomputers.us

 

[mojo31]

done that, still doesn't pick up an address.

 

[GlenJohnson]

It seems that it dishes out one address, and then it wont dish another out. As soon as we release it from one machine, do a ipconfig /renew on another the new machine picks it up

Does it keep giving out the same ip address?

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

TTinChicago

http://www.johnsoncomputers.us

 

[mojo31]

No, different addreses are being dished out, but then no more after it. Then you release it. and another machine will pick it up, we did this in situ in the office.Those that have leases at the moment appear ok. The only thing that has changed is that the domain Admin password was changed about week and half ago. The first instance we had was a user who had been on 3 weeks leave and came back, couldnt get on the network-no IP address. In the end I had to delete the WINS entries (which were tombstoned) delete the computer account from the domain, rename the pc, and then it rejoined the domain with an IP, no problem.