Discussion Locked

98SE client ask for DHCP twice

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Anybody ever experienced this:

In a 1500+ PC workstations site equiped with NT4 servers and Win98SE clients, some will not show the Domain Logon at startup.

It appears that the WS is asking to renew the IP address at startup, gets acceptance from one of two DHCP servers, and cary on with domain logon. This is normal.

On the troubled workstations for some reason, after the initial IP renewal, the workstation apparently discard the IP adress and does a complete IP discovery/negotiation sequence, with discover/ offer/request/accept. Some time it will get a new IP adress some times it will get the same as was first renewed, depending of the accepted offer from the DHCP server.

It looks like for some reason the IP stack is reset. This is asyncronous to the Windows startup, so at the time of logon, there is no IP stack, causing Windows to display only the Windows logon, and not the Domain Logon.

No need to say, the initial IP renewal is completely valid (I compared this with an analyzer).

What will make the IP stack reset, during startup?.

The workstations are newer Compaq models with i8xx chipset and onboard Intel NIC.

We tried forcing LAN speed/duplex, using 10 MB hubs instead of switches etc. to no avail.

Any sugestions

5 replies

by giacomo

You should definetly contact Compaq in regards to this problem. They've helped me out before with Nic issues. Perhaps you should get online and find the most recent driver for your Nic and test it. Sometimes the solution is as easy as that. If you're unlucky at least you've made compaq aware of the problem.

Giacomo

by ivan

Oh, and I forgot to mention:

The problem comes and go; Some times you will strike 3 in a row, some times it takes 10 retries to get the error.

We have tried the originaly Compaq supplied NIC drivers, the Compaq updated drivers, and the newest Intel supplied ones (thanks Giacomo). Same problem.

We tried disabling interrupt steering (I'm an old timer, from the days when an interrupt was an interrupt). You figured it; same problem.

Dr. Bob, both your links where dead links (first one blank, second no such page). Have they possibly been truncated in the answer?
Are they dealing with shared interrupts?

I am very interested as I do suspect hardware being the course, though it appears on different models.

by wlbowers

Have you tried a different port on the switch or hub this unit is in.

I had this kind of problem and It wound up being a intermittant port.

good Luck Lee

by ivan

Note that this happend to several Workstations (hundreds), and that, as originally stated, we tried hubs instead of switches etc.

Thanks for your answer annyway.

We eventually solved the problem by installing one Win2K server for DHCP serving.Haven't seen the problem since.

This discussion is closed to new replies.