class b vs. class a ip addressing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a home network that was working fine. Now, 1 of the computers gets an
ip address in the 169. range instead of 192. How do I correct this?
 
edwgolz said:
I have a home network that was working fine. Now, 1 of the computers gets
an
ip address in the 169. range instead of 192. How do I correct this?

This is an autoconfiguration address assigned automatically by windows
because it was unable to pick up an IP address from the DHCP server ( a
router, or ISC machine usually ). There are many reasons why DHCP might
fail.

Is there anything in the event viewer?

If you manually assign a 192 address, subnet mask, default gateway, and DNS
can you get connectivity?

What has changed since the machine was able to pick up DHCP addresses?

Is the DHCP server still running on the network?
Can other machines pick up addresses?

Verify basic hardware: Link lights on ( router and PC )?
Try a different cable or port on the router.

Is there MAC address filtering on the router and you've changed LAN cards on
the problem machine?

Have you ripped out any spyware lately?
Sometimes this can break the LSP chain, and this can break DHCP.
Google for LSPfix, download and run it.
 
Thanks for the reply Ron. ell suggested I get a new motherboard or re-install
the operating system. 2 of the PC's on the network were getting the 1169.
IP's. I ended up resetting the router and refreshing the DCHP settings on it
and now everyone is in the 192 range. Took 5 hours to figure it out and 45
seconds to fix it. Thanks.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top