Re: DHCP Problem causing ip to be 169.X.X.X and not 192.168.X.X

From: Matt DuBois [MSFT] (mdubois_at_online.microsoft.com)
Date: 03/27/04 

Date: Fri, 26 Mar 2004 16:45:37 -0800

So, you have two problems here. I'll split my answer up so you can look at
each seperately.

1) Can't get a DHCP address
        Many routers (I have an older Linksys myself) have an option in
their configuration to limit the number of clients they will serve DHCP to.
If your router was set up by your ISP, they may have set this to just the
number of computers you had (this happened to a friend of mine). If you did
it yourself, you may have set it yourself and forgotten. Either way, its a
good option to check first. Other troubleshooting steps you can take:
        A) Do an "ipconfig /renew" manually at the command prompt. Report
back any error it gives you in a reply to this post.
        B) Disable any firewalls on the computer (temporarily, for testing).
See if you can get an address. If not, statically assign one, and see if
your other computers can ping this one. Report back the results.

2) Can't resolve DNS when IP is statically configured
       Since you can ping to the internet by IP address, that means you just
likely don't have the DNS server configuration right. You can try the stuff
in this section to get you going while you work on sorting out why DHCP
isn't working. Right under where you statically configured the IP address,
you can configure DNS. You have three options here to find the server
address:
        A) Put in the address of the linksys router (may not work)
        B) On a computer that does work, run "ipconfig /all" at the command
prompt, and use what it is using for DNS servers.
        C) In the web administration tool on the linksys router, there will
be a status page that shows you the external IP address and (usually) DNS
servers for your ISP. Copy the DNS server addresses from there and use
them.

As a general reminder, to successfully connect to an internet site, you need
four things to be properly set:
A) IP Address
B) Subnet Mask
C) Default Gateway (should be the internal address of the Linksys router in
your case)
D) Properly configured DNS servers

Reply back to this post with the information requested in the sections above
or reply back saying it is fixed if one of the above suggestions worked for
you. Thanks!

-Matt 

-- 
This posting is provided AS IS with no warranties, and confers no rights.
"Dan Danahy" <anonymous@discussions.microsoft.com> wrote in message
news:D129A5BB-B239-42AA-AB59-59CFA36BC382@microsoft.com...
> I am having a very simular problem. My problem started when I decided that
my onboard Ethernet chip may be having problems with dropouts. I disabled it
in the bios and proceeded to install a Linksys LNE100tx v5.1 nic card. This
system is connected to a Linksys WRT54G. Two other PCs on the LAN are also
connected to the Linksys router.  All are running Win XP Pro.The router is
connected to cable modem. All were working well until I installed the new
nic in one of the PCs. The other two PCs still are working just fine. The PC
with the new NIC card does not get a DHCP download from the router and
instead gets an automatic IP from windows XP with the usual address on the
169.254.0.0 subnet. In that state the PC cannot connect to anything. If I
give it a static address in the 192.168.1.0 subnet (outside of the DHCP
range) then I can see the other two PCs on the net (netbios) but cannot
connect to the internet. I can how ever ping LAN and WAN addresses. It
appears as if windows is not resolving ip addresses. NSLOOKUP cannot find
the DNS servers. I have tried the fix in KB article 817571 with no luck. Oh
and I tried to go back to the onboard Ethernet and it too now has the same
problem. I would be glad to provide more info if needed but any help would
be greatly appreciated.
>
> Thanks,
> Dan

Relevant Pages

  • Re: Setting up client computers after SBS 2003 install
    ... checked into the router if it was a DHCP server, and it was, so I disabled ... server that DHCP was disabled. ... > configuration will certainly assist you. ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP Problem causing ip to be 169.X.X.X and not 192.168.X.X
    ... > their configuration to limit the number of clients they will serve DHCP to. ... My linksys router is set to 50. ... Did that and my virus checker, still no ip address from DHCP on the linksys. ... and use what it is using for DNS servers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Router as an Access Point?
    ... >Is it possible to use a router as an Access Point? ... access point into your 5 IP address connection, ... your ISP's DHCP server is smart enough to know if an IP ... This will get you back to the configuration screens. ...
    (alt.internet.wireless)
  • Re: Ok Im new to SBS - help!
    ... This is one of the documented configurations, and the CEICW wizard "knows" that configuration. ... It also requires configuring the router carefully, ... Doing the usual 2-NIC SBS configuration will definitely be easier for him, because the DHCP server in the ASDL modem/router/etc. ...
    (microsoft.public.windows.server.sbs)
  • Re: Error with XP Pro
    ... >>>school and am trying to set it up on the home network. ... >>>entering the DNS servers that work on the other pc's, ... >> It sounds like whoever setup the router is careful with who uses it. ... >> has a MAC filter for DHCP, and maybe for internet access too. ...
    (microsoft.public.windowsxp.network_web)