General discussion

Locked

DHCP not always giving out IP addresses

By clugovsky ·
OK, here's one that's been bugging me to no end. Most of the PC's running their DHCP clients are working great (all Win98 or Win98SE). They boot up first thing in the morning and get their dynamic IP address assigned to them and, of course, are able to login to the domain. There are a few however, that simply won't. The login screen comes up but the message "No domain server found, etc.." When I cancel through it and run WINIPCFG (or IPCONFIG) to check the ip address, it's completely wrong(My scope is 209.x however it shows 169.x which would explain why it can't find the PDC or BDCs). Now if I hit the Renew button, it finds the address first try and I can "logoff" and then login correctly.

Any takers?

System descriptions:
Workstations: Win98 or Win98SE w/ TCP/IP, Client for MSnets, DHCP Dynamic, WINS obtained from DHCP.
Servers: PDC running WinNT4 SP6a, BDCs running WINNT4 SP6a, Win2K DHCP Server, Win2K WINS Server, Win2K WEB Server, WinNT4 SP6a Exchange Server

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

DHCP not always giving out IP addresses

by clugovsky In reply to DHCP not always giving ou ...

Btw, this issue only happens to a few of the workstations (3-5 desktops out of 200 desktops)

Further, I am running a WAN (have BDC's and a DHCP on the other side as well with a 192.x scope)

Collapse -

DHCP not always giving out IP addresses

by hstahl In reply to DHCP not always giving ou ...

Is it always the same 3-5 desktops? Do these 3-5 desktops (if they are the same ones) share the same network hub or switch?

It seems like there are a lot of places the problem could be... just listing off what I'm thinking right now:

- Somebody is running a program that has a DHCP server in it and that's what's giving out your bunk addresses (although I think 169.X is the panic address of Win9X). I think this is pretty unlikely, but you never know.

- What happens if you don't startup these mis-behaving workstations until 20-30 minutes after all the others? I'm wondering if your DHCP server is just getting hammered right around 9:00am (or start of the day) and is taking too long to get back to these ones so the clients time out. It could also be your network is overworked right about then -- bunch of collisions, retransmits, etc. This is probably more likely than an overworked DHCP server (since DHCP isn't too taxing).

- Try one of the misbehaving desktops at a different physical location. I wonder if you've got some bad wires in your runs. Also try with just a different patch cable at the same location.

- If none of the above work try using a Network Sniffer to watch traffic on the same area as those workstations. See if you ever see their request for an address and if you do, see if your server responds. If you are on a switched network you'll need to be in the same segement as those computers. Easist way would be to throw a hub on one and plug in your laptop to that and watch the traffic you see when you start one of the workstations.

-Heath

Collapse -

DHCP not always giving out IP addresses

by clugovsky In reply to DHCP not always giving ou ...

Verified there are no other DHCP servers around other than the Win2K running locally (this location) and the other one running across the WAN.

As far as overworked, the server is a standalone DHCP that only takes care of dynamic assignments, nothing else.

Have tried to augment the 3-5 workstations login time by up to an hour with no different in the result.

To your first question, though, those 3-5 workstations have the same problem for about 3 months and then for some reason, the problems move on to a different 3-5 workstations. (i.e. Accountant #1 had the problem, but after 3 months he's fine, but Operations Manager #2 now has the problem)

Collapse -

DHCP not always giving out IP addresses

by turambar386 In reply to DHCP not always giving ou ...

Howdy. What's happening here is that for *some* reason, these Win98 machines are timing out while looking for a DHCP server. When this happens, they resort to their idiotic APIPA (Automatic Private IP Addressing) feature which assigns them a 169.x.x.x IP address.

Apparently, there is a known problem with some versions of Win98 having a very short time-out period looking for a DHCP server.
Check Microsoft technet article Q194790 for instructions on getting a patch.

Otherwise, you can disable APIPA by editing the registry. You can do so by adding the "IPAutoconfigurationEnabled" DWORD registry entry with a value of 0x0 to the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP

I don't know if disabling APIPA will get the machine to wait longer for a DHCP server, but at least it won't go giving itself a random IP address.

Hope that helps.

Collapse -

DHCP not always giving out IP addresses

by clugovsky In reply to DHCP not always giving ou ...

Poster rated this answer

Collapse -

DHCP not always giving out IP addresses

by clugovsky In reply to DHCP not always giving ou ...

This question was closed by the author

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums