Douwesiegersma

Thank you. I'll try both suggestions and report back here.. D

IPv6 is not available on win2003 SE. And the error occurs on wireless and wired connections. In the arp-table the IP-address (ending with 3.43) is listed as a static IP-address. Even after I remove it from the reservations in DHCP. The macaddress differs from the macaddress of the workstation the IP-address is given to. I'll go and see if I can find the device with the listed macaddress. To be continued...... D

You are fast guys! There is only one DHCP-server active on the domain. Within DHCP only one scope is active (I de-activated the old one and then deleted it) As for DNS: I recently setup the Reverse DNS entry for the new scope because I discovered a lot (hundreds) of errors (31:DNS update failed) in the DHCP server log. The errors were gone but my the bad IP-addresses were not :-( DNS and DHCP are on the same server. Is that a possible cause of the problem? And how to check for rogue DHCP-servers?

Hello, I'm running a school network and ran out of local IP-addresses. So I created a new DHCP scope 192.168.x.x with 255.255.0.0 as subnetmask. Everything work well except that every now and then an IP-address doesn't work. The workstation gets an IP which seems to be legit (192.168.3.43) but Internet is not working and the server (192.168.100.2) can not be pinged (timed out) Strangely enough other IP-addresses can be pinged (192.168.100.10) The only thing I can do is put the bad IP-address in the reservations with a non existing mac-address forcing the DHCP-server to give the workstation anather IP-address. Any ideas why this happens?? D