DHCPREQUEST failed

[Theoneandonly]

Hi all,

All clients on some parts of our WAN, dhcp-configured, fail to obtain a lease from the dhcp server at startup.
Inside event viewer, I get the error 1005 or 1003, DHCP failed to obtain a lease for the card with network address XXXXXXXXXX. The following error occurred :
The semaphore timeout period has expired.
I recently moved from hubs to switch on these nets, and red somewhere that swich with spanning three algorithm can loose DHCPrequest packets...as I don't have access to switch, neither with console, nor remotely, can anyone tell me how to increase (reg keys ?) the delay to obtain a lease for a client ?

Thanks for any info

 

[djhawthorn]

You say these clients are on the WAN - I take it they are on a seperate subnet to the one the DHCP server is on?

Is your router configured to forward DHCP requests in this case? MCSE NT4/W2K

 

[Theoneandonly]

It's a small one. The same subnet for the whole WAN, but different domain, each domain with his own DHCP server.
Manual renewal of TCP/IP config works after 30 sec - one minute.

 

[BOKA]

Here is the problem we had.
We have a switched LAN. Switches are Cisco5505. Originally, when just moved into the facility, we were plugging our laptops/desktops directly into switch ports. That did not work well - we could not get an IP right away, but it would work after a few minutes.
To correct the issue, we purchased several layer-2 switches (like Linksys, for example), plugged them between Cisco and PCs and everything has been working great ever since.
Our PCs are WIn9x, NT4, Win2000. Every net card is dual speed. DHCP pool is provided by the router, that is behind the Cisco switch.

Good luck.

 

[BOKA]

Totally forgot - we did try turning on PortFast setting on the switch, but that did NOT help a bit.