Discussion Locked

DHCP No Longer Available in Win 98

0 helpful
21 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We've been running DHCP on our network for four years now. All of a sudden I am getting machines that worked fine before that are claim no available DHCP server. What's going on here. At first I thought I had run out of avalailable IP addresses, but my DHCP server claims that only 66% of the addresses are actually being used. Any hints?

21 replies

by stillatit

Here are some suggestions.

1. Start by asking yourself what has changed.

2. Do the stations which cannot find the server consistantly not find it, or do they eventually find it? If it is consistant, try plugging a "good" station into the net port used by a "bad" station, and see what happens when it boots up. If it fails, look at the path to the server.

3. Try replacing the NIC card in one of the "bad" stations and see if the problem goes away. Sometimes a marginal NIC card creates this problem.

4. If you have routers in your LAN, do they support bootp forwarding (and did it get turned off recently)?

5. Use ipconfig /all (NT) or winipcfg (Win9x) to see what, if any, DHCP server the "bad" stations are/were using.

Good luck.

by mphoffar

I see this mostly on laptops, and it usually just comes down to corrupted NIC drivers and just removeing the device and reinstalling it after rebooting takes care of it 99 percent of the time with what I have here

I usually check to ake sure something hasn't changed on the NIC properties before doing that though...like making sure 100 base T wasn't selected (we're running 10 base here)

Good luck to you

Mark

by dash_hadley

This is very interesting because there is also a question in this section about "Lost Gateway." I recently placed my home/office LAN with a Cable ISP and everything was fine for 2.5 months. Then I started getting the DHCP server not available notice and after repeatedly attempting to connect I got the "Lost Gateway" notice. I pulled everything apart and started from scratch. This helped for about two three-hour sessions and eventually I was kicked off. I e-mailed the cable company and toldthem that I was getting this error notice and was unable to log on 24-hours a day. I also felt that it was coming from their end. All the cards were 3-months old; everything else was new and had worked correctly. It took approximately 3 days to get an answer from them. They felt it was the connections and that by turning the systems on and off, it would solve the problems. We always shut down everything at least once in a 72-hour period. Since this incident and my conversations with them, this has not occurred. One terminal boots up with a driver error still, but manages to log onto the system anyway. It is my impression that additional users were placed on the system and they--the Cable ISP--may have in place a re-routing device which placed limits on the users in the area. It may be a problem of allocation of service accessibility.

by Former member

The DHCP Server is running NT 4.0 with SP 6a.

by Former member

My apologies. I failed to mention that newly installed machines are not able to access the DHCP Server. We have installed several new machine many get an IP address and others do not. There doesn't appear to be any appreciable difference in the way the machines are set up and in most cases they are identical. We have experimented with switching NICs, but that doesn't seem to help. The NICs aren't bad. Also, we've had the lines tested and we are getting throughput on the lines.

by tommy.leerschen

Good answers before, How 'bout another thought...Check your NIC cards for connection preferences. Most cards we use have an "Auto" for both speed 10 or 100, and also for half or full duplex. I have found that the autonegotiate settings can fail, andafter "hard" setting the cards, they are able to find the server.

Good Luck

by Former member

The NICs we have are fiber NICs and have already been hard set to 100-FX Full Duplex

by tommy.leerschen

Good answers before, How 'bout another thought...Check your NIC cards for connection preferences. Most cards we use have an "Auto" for both speed 10 or 100, and also for half or full duplex. I have found that the autonegotiate settings can fail, andafter "hard" setting the cards, they are able to find the server.

Good Luck

by Former member

Point value changed by question poster.

by jolly roger

A previous poster said:
5. Use ipconfig /all (NT) or winipcfg (Win9x) to see what, if any, DHCP server the "bad" stations are/were using.

What was the result of performing this action? The more we know the better the chance we can help.

by Former member

The result was the winipcfg crashing because it could't ping any of the servers.

by Former member

Well, first I would like to personally thank everyone for their efforts to help me. It is sincerely appreciated. Rest assured I will return if I have another major crisis.

However, you're not gonna believe what had happened.

Case 1: In one of the offices, the fiber optic cable had been ripped from the wall. The person who did it hid the damage and feigned ignorance.

Solution: We're calling in the cable installation company to do a quick repair job.

Case 2: Apparently there has been an intermittent drop in power at an outlet where one of the fiber switches is located. This results in a loss of handshake between switches even though a handshake between the switch and the clients is visible and active.

Solution: A UPS will be purchased and installed on the switch while the broblem with electrical power is investigated.

Again thank you all for your assistance.

by Former member

This question was closed by the author

This discussion is closed to new replies.