I've run into this problem a few times and I want to finally figure out
what's happening.

When I set up a class C in DHCP console, I end up with the first address
listed (if manual) being not completely brought down to the XPPro
workstation. Currently, I've set up a new class to designate staff-only
machines for filtering purposes. But when I put in the first active address
(10.1.222.2), that machine only partially and only sporadically gets it's
IP.

Usually on an ipconfig /renew, the machine will get the ip and the mask, but
not the gateway. When I try to ping -t the server that is in the same class
B (10.1.2,2), I get a consistent 3 successes 1 failure (consistent over
100's of successive pings). As I understand it, with the mask at
255.255.0.0, the lack of a default gateway should not apply to pinging a
server on the same Class B.

Once since I created the address, the machine got everything. Usually it
gets "Can't contact DHCP server", sometimes it gets everything but the
gateway, but still won't communicate IP to connect the client.

I have confirmed the settings in DHCP server through another address
(10.1.222.3) which works perfectly.

I believe I have seen this before on the win9x workstation but with nothing
coming through at all.

Any ideas or remedies for this?

--
Chris Denby
-------------
IT Coordinator
Rainy River District School Board
Fort Frances, Ontario
Canada






--
Chris Denby
-------------
IT Coordinator
Rainy River District School Board
Fort Frances, Ontario
Canada