Re: DHCP Problem causing ip to be 169.X.X.X and not 192.168.X.X
From: Dan Danahy (anonymous_at_discussions.microsoft.com)
Date: 03/27/04
- Next message: Steve Winograd [MVP]: "Re: Creating a network?"
- Previous message: Patrick aka-WhØs ÑéXt{¿}: "Info. on making a web page"
- In reply to: Matt DuBois [MSFT]: "Re: DHCP Problem causing ip to be 169.X.X.X and not 192.168.X.X"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 27 Mar 2004 13:31:08 -0800
Matt,
Thank you for the quick reply. I think I have tried all of your suggestions. I'll go through them one by one.
> 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.
My linksys router is set to 50. I have three PCs on the net.
>A) Do an "ipconfig /renew" manually at the command prompt. Report
> back any error it gives you in a reply to this post.
I did that and the error was something like "trying to do an operation on something that is not a socket" That is when I went through the winsock delete and reinstall.
> B) Disable any firewalls on the computer (temporarily, for testing).
> See if you can get an address.
Did that and my virus checker, still no ip address from DHCP on the linksys.
>If not, statically assign one, and see if your other computers can ping this one. Report back >the results.
I tried that too. Also when I have a static address in, I can see the other PCs shared folders etc on the LAN (netbios).
>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)
Tried that, didn't work
> B) On a computer that does work, run "ipconfig /all" at the command
> prompt, and use what it is using for DNS servers.
Looked at those. They are the ones the ISP puts out.
> 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.
Tried them, still didn't work
>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
I think I have done all of those. Still didn't work.
So after agonizing over this over night, I decided to do a repair (upgrade to WinXP) that didn't go well either. After the second reboot the screen goes black and everything freezes.
After spending 5 hrs on the phone with Microsoft, they gave up and referred the call to research. But not before rendering my machine un-bootable. It used to be able to go back to the old system but not now. They say they will call within 48 working hrs to try to fix the problem. I am on the verge of doing a complete fresh install. I really hate to do that (all those app re-installs). I do have work to do with this PC so I may be forced into the full install. But, thanks for your thoughful answer to my first two problems.
Cheers,
Dan
----- Matt DuBois [MSFT] wrote: -----
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 justAs 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
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
- Next message: Steve Winograd [MVP]: "Re: Creating a network?"
- Previous message: Patrick aka-WhØs ÑéXt{¿}: "Info. on making a web page"
- In reply to: Matt DuBois [MSFT]: "Re: DHCP Problem causing ip to be 169.X.X.X and not 192.168.X.X"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
