DHCP event ID 1003 2

[McDeanski]

We have a multihomed W2K server wich is connected to our LAN and the second NIC is connected to xDSL (BabyXL in the Netherlands). We get an active lease of 4 hours and after 2 hours our server wants his lease reactivated, but this doesn't work. We get from the 2 hour sign in the event viewer Event ID 1003 (windows was not able to renew its address from the DHCP server; the semaphore timout period has expired) ending after 4 hours in a Event ID 1000 (lost its address) IPCONFIG /renew does'n't work, only disabling and enabling the NIC and everything works fine for 4 hours. Can somebody help with this??

 

[Lightspeed1]

McDeanski -
Is there a specific reason you are obtaining an IP via DHCP on your server? As a general rule, servers should be statically assigned IP. What Model and brand of NIC are you using? What is dishing out DHCP to the server? Are you trying to obtain a lease over a WAN connection? Try setting the lease renew period to the 8 hour mark, which I believe is the default. Personally, I would go with a static IP config on the server. It's one thing to have a client machine lose it's address, but if your server does, the whole network is effected.
Regards,
Lightspeed1

 

[GlenJohnson]

Static IP by all means. Also, check and see if the nic is sending out bad packets. To much network traffic can cause all kinds of problems. Did a quick search on google, and found this.

Source DHCP
Type Warning
Description Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 00B0D0A5D62E. The following error occured:
The semaphore timeout period has expired. Your computer will continue to try and obtain an address on its own from the network address {DHCP} server.
Comments Adrian Grigorof: If the DHCP server works properly then this generally means a network or connectivity problem. Try to isolate the physical equipment that connects the wokstation in question to the DHCP server.
Contributors Jesse Pelayo
Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"Don't take a fence down until you know why it was put up".
Robert Frost (1874 - 1963); U.S. poet.

 

[McDeanski]

Sorry for the confusion but our server (W2K SP2a) has a second NIC (3C905C-TX) and thisone is connected to our ISP. We get from them a lease of 4 hours and there is where the problems starts, not on my local LAN where I use static ip of course. We use the xDSL-line for our Internet and Mail connection.

Thanks for your reply.

 

[johnpsmith]

i had this same problem on a server acting as a client to a dhcp server. no network problems occurred if the ip was static-so it can`t be a network problem and also /renew worked as did disable/enable. all this was with a multi-homed client. i searched google frantically coming up with nothing important
However with a multi-homed computer there is apparently importance to the physical order of the NIC cards:ie slot location. the private lan card is obviously the static ip. you must ensure that that card is also in the lower slot location and the automatic ip is requested from the card next in slot order.
apparently on start-up windows can`t cope with automatic ip from the first physical slot-it apparently marks it as "problematical" because on startup it needs an ip to start network connections and only then will it turn to searching for a dhcp
so i switched around ip definitions making the first physical slot NIC the static ip
and thank g-d error id 1003 for dhcp has not occurred since
in addition in the tcp/ip core networking guide p.279-280 you will find how to use the IgnoreBroadcastingFlag.
this may help if you NIC card cannot accept unicast broadcasting.
i didn`t need to use it but you may find it helpful