Mixed DHCP & Fixed IP's on Same Network

I'm having a problem with one of the PC's on my home network that is not
getting the right IP address from my router using DHCP. I'm using 10.1.1.x
and this PC is set to auto config IP address and it's pulling something
starting with 169.x.x.x. I can get this PC to work, if I manually assign an
IP in the 10.1.1.x range. The other three computers on my network are
resolving the correct IP using DHCP.

Is there any problem with keeping this problem PC with a fixed IP while the
others are set to auto config via DHCP? I'm using a linksys router and
Linksys USB clients. This problem just started happening in the last week or
so. All computers are on Win-XP.

In article <xZidnTawjuVVwDGiU-(E-Mail Removed)>, Wil <(E-Mail Removed)> wrote:
> it's pulling something starting with 169.x.x.x.

That's the address Windows machines pick when they can't get an address via
DHCP. I think 169.254.0.0/16 belongs to some military organization. If so,
that's a bad choice for MS to have made. People with guns have ways of
making their displeasure known.

> Is there any problem with keeping this problem PC with a fixed IP while the
> others are set to auto config via DHCP?

No, I do that with my laptop sometimes, and some of the machines around here
have static addresses while the others use DHCP.

> This problem just started happening in the last week or so.

Maybe set the addess to static (pick an address, any address), then set it
back? Also, check the logs for anything having to do with DHCP.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
LEO: Now is not a good time to photocopy your butt and staple
it to your boss' face, oh no. Eat a bucket of banana pudding
and wash it down with a gallon of strawberry Quik. -- Weird Al

"Hactar" <(E-Mail Removed)> schreef in bericht
news:bohtc0$c9h$(E-Mail Removed)...

>
> Maybe set the addess to static (pick an address, any address), then set it
> back? Also, check the logs for anything having to do with DHCP.
>

Looks to me that his NIC (network card) has stopped functioning. Could also
be the connection from his NIC to a router switch or whatever he uses.

Wil try this: assign a IP like 10.0.0.1 to the problem PC. Assign 10.0.0.2
to another PC in the network (both subnestmasks should be 255.255.255.0).
Try to see if you can ping both ways..... If no, replace the cable. No
succes? Replace the NIC.


Regards,


Marcel

--
Posted by news://news.nb.nu

"Marcel Joustra" <(E-Mail Removed)> wrote in
message news:3face4cd$(E-Mail Removed)...
>
> "Hactar" <(E-Mail Removed)> schreef in bericht
> news:bohtc0$c9h$(E-Mail Removed)...
>
> >
> > Maybe set the addess to static (pick an address, any address), then set
it
> > back? Also, check the logs for anything having to do with DHCP.
> >
>
> Looks to me that his NIC (network card) has stopped functioning. Could
also
> be the connection from his NIC to a router switch or whatever he uses.
>
> Wil try this: assign a IP like 10.0.0.1 to the problem PC. Assign 10.0.0.2
> to another PC in the network (both subnestmasks should be 255.255.255.0).
> Try to see if you can ping both ways..... If no, replace the cable. No
> succes? Replace the NIC.

Marcel, I should have said I'm using wireless on three of the PC's on my
network. The problem PC is wireless also. I have one additional PC that is
connected via cable and DHCP is working with this PC. I can ping any PC on
the network using 10.1.1.x and subnet mask as 255.255.255.0. However, I am
manually assigning the IP address to the problem PC.

I'm also using MAC address filtering and I have maximum number of DHCP
clients as four. If there is no harm in keeping my problem PC with DHCP
turned off, then I'm going to leave it that way and let the others one find
an IP automatically. Thanks for the suggestions.

>
>
> Regards,
>
>
> Marcel
>
> --
> Posted by news://news.nb.nu

"Hactar" <(E-Mail Removed)> wrote in message
news:bohtc0$c9h$(E-Mail Removed)...
> In article <xZidnTawjuVVwDGiU-(E-Mail Removed)>, Wil <(E-Mail Removed)>
wrote:
> > it's pulling something starting with 169.x.x.x.
>
> That's the address Windows machines pick when they can't get an address
via
> DHCP. I think 169.254.0.0/16 belongs to some military organization. If
so,
> that's a bad choice for MS to have made. People with guns have ways of
> making their displeasure known.
>
> > Is there any problem with keeping this problem PC with a fixed IP while
the
> > others are set to auto config via DHCP?
>
> No, I do that with my laptop sometimes, and some of the machines around
here
> have static addresses while the others use DHCP.
>
> > This problem just started happening in the last week or so.
>
> Maybe set the addess to static (pick an address, any address), then set it
> back? Also, check the logs for anything having to do with DHCP.
>
<snip signature>

Thanks for the suggestions. I'll give it a try today.