DHCP not getting an IP - Help

[Guest]

Archived from groups: microsoft.public.windowsnt.setup (More info?)

I recently added an NT box to my workgroup. I could not get the other
computers to see the NT box, but the other computers could be seen by the NT
box. I realizes that was because NT was not sharing and ended up re-applying
the service pack (6)

Now that is fixed. All computers are seeing each other, but now i cannot
access the internet from the NT box. I did an Ipconfig and no IP address is
shown (0.0.0.0).
and i get the following message at startup:

"the DHCP client obtained an IP address that is already in use on the
network, The local interface will be disabled until the DHCP client can
obtain a valid address"

Can someone help me through this??

--
http://QLiner.com

The goal of the works of a genius' existance lies only in itself.

 

[Guest]

Archived from groups: microsoft.public.windowsnt.setup (More info?)

weird thing you can browse your network in this situation, are you using
another protocol for filesharing (ipx/spx or netbeui)?

Run "ipconfig /all" command on all machines and compare results with your
DHCP server settings (especially IP ranges definition). It is possible you
have one computer set to static IP address withing DHCP dynamic IP range and
that it is just address DHCP server wants to lease to new machine.

Also if you are using APIPA IP range for DHCP dynamic range
(unrecommended!), it is possible there is conflict between DHCP and APIPA
mechanism of dynamic address allocation (computer that cannot contact DHCP
server and has lease time runned out or undefined will use APIPA mechanism
to set IP address and next computer asking DHCP server for new lease can get
the same address). If it is your case, either change DHCP range to any
regular private IP address range (recommended) or turn off using of APIPA on
all computers (it is possible only by tweaking of registry).

If you have not DHCP server and have dynamic allocation set (ie. all your
comps are using APIPA mechanism), check settings of your internet gate, most
of them are able to act as DHCP server and have automatic "user friendly"
setup script that will check your network and setup gate automatically. Note
that if you have 5 or more computers and do not have DHCP server set, do not
use dynamic IP address allocation and set your computers to use static IP
addresses. APIPA mechanism is designed to support small simple networks only
(I saw network with 18 computers using APIPA and all was in order, but i do
not recommend doing this).

You can also set NT computer to use static IP addres from your static IP
address range. (At least DHCP server alone should use static IP address and
also default (internet) gate device should use static address in case
default gateway info is part of DHCP packet).

Note that even if you are using your internet gate device as both DHCP
server and firewall, these two parts are not linked and DHCP server can
allocate client IP address that is not allowed by firewall filters to go
through. So check your firewall filter to see, what addresses are allowed to
access internet from your network.

luck

George

"stewart allen" <inexpensivepcs@comcast.net> pí¹e v diskusním pøíspìvku
news:#Uzka$NVEHA.2972@TK2MSFTNGP12.phx.gbl...
> I recently added an NT box to my workgroup. I could not get the other
> computers to see the NT box, but the other computers could be seen by the
NT
> box. I realizes that was because NT was not sharing and ended up
re-applying
> the service pack (6)
>
> Now that is fixed. All computers are seeing each other, but now i cannot
> access the internet from the NT box. I did an Ipconfig and no IP address
is
> shown (0.0.0.0).
> and i get the following message at startup:
>
> "the DHCP client obtained an IP address that is already in use on the
> network, The local interface will be disabled until the DHCP client can
> obtain a valid address"
>
> Can someone help me through this??
>
> --
> http://QLiner.com
>
> The goal of the works of a genius' existance lies only in itself.
>
>