IP assignment by DHCP failure

[chris]

One computer running Win XP home will not get an IP
address from the router using DHCP. Instead it changes
during boot up to "Automatic Pritvate" method no matter
how many times I reset to get from DHCP automatically.

Please, before suggesting that I check all the obvious
connections and do all the standard diagnostic tests, I
have run every conceivable diagnostic test, I have
recycled the modem, router etc., I have reset TCP/IP and
I have communicated with Netgear and Comcast technical
help and not been able to figure this out. I know that
the computer in question connects to the router and if I
manually enter a appropriate IP address, DNS etc.
identical the the other computers on the LAN, this
computer will communicate with the other computers on the
LAN but not the internet.

Thanks very much for any help.

Chris

 

[Guest]

Well looks like you are in the same boat as me. I also have been pulling my
hair out.
I also am using a NetGear 614 v2 router. I have tried everything even all
the updates firmware from NetGear. No matter how many times I change my
settings for a 192.168.0.2 windows keeps resetting it back to 169.254.248.88
.. From which point I can not connect to the web. The only thing that seems to
work most of the time is to unplug the router at which time windows says that
the network connection has been lost. Plug the router back in and windows
says a new connection has been detected. Goto the "cmd" command promt in win
xp and type ipconfig . Now you should see the correct information you need
and want. Hello WWW. Let me know if you find a fix. Thanks.

 

[Barbara]

I too have the same exact problem. I had to uninstall SP2.
I wish someone had an answer by now.

 

[Kent W. England [MVP]]

chris wrote the following on 16-Aug-2004 1:14 PM:

One computer running Win XP home will not get an IP
address from the router using DHCP. Instead it changes
during boot up to "Automatic Pritvate" method no matter
how many times I reset to get from DHCP automatically.

Please, before suggesting that I check all the obvious
connections and do all the standard diagnostic tests, I
have run every conceivable diagnostic test, I have
recycled the modem, router etc., I have reset TCP/IP and
I have communicated with Netgear and Comcast technical
help and not been able to figure this out. I know that
the computer in question connects to the router and if I
manually enter a appropriate IP address, DNS etc.
identical the the other computers on the LAN, this
computer will communicate with the other computers on the
LAN but not the internet.

You are the second comcast customer recently to experience DHCP failure
on this group. The other poster is using comcast without a home router,
so the problem is between XP and comcast. Yours is between XP and Netgear.

I wonder if you recently updated to XP SP2? What software did you
recently install or uninstall? Have you recently removed spyware with
Spybot or Ad-aware? Were there any Windows critical updates installed
just before the failure?

At this point, there is no solid clue except that it seems that it is
strictly a DHCP problem, since configuring an appropriate static IP
address confirms that TCP/IP is working and Internet access is OK. I'm
off to google the problem, let me know if any of the above questions
raise a suspect.

 

[Bruce Ramsay]

One computer running Win XP home will not get an IP
address from the router using DHCP. Instead it changes
during boot up to "Automatic Pritvate" method no matter
how many times I reset to get from DHCP automatically.

[...]

Chris,

One thing I've noticed is that sometime in the last 2 or 3 weeks
Comcast has changed the address of their dhcp server in this part of
the net from 12.242.19.34 to 10.155.64.1. Perhaps they've done a
similar thing for you. Since I use the 10.* addresses for my network,
I had firewalled out any incoming 10.* traffic. Tonight I was looking
at a new firewall builder and noticed that the address lease had not
been updated for quite a while. Now I really do need to update my
firewall. One of the symptoms after I actually updated the address
lease was that my routing table was messed up. Perhaps something
similar is happening to you.

Bruce Ramsay

 

[chris]

Hello,

Thanks to everybody who has responded this apparently
insoluble problem.

One of the replies prompted me to check Win XP Hotfixes
that have been loaded on the PC affected.

I found the following on Microsoft's site that pertains
to IP addresses. I do not know what a "loopback" address
range is but this problem looks suspiciously like my
problem. Before I go deleting or fixing with patches can
somebody comment if this looks like it is related to the
problem I originally posted.

Thanks for all the feedback.

Chris

Microsoft Comment:

Programs that connect to IP addresses that are in the
loopback address range may not work as you expect in
Windows XP Service Pack 2
View products that this article applies to.
SYMPTOMS
On a computer that is running Microsoft Windows XP with
Service Pack 2 (SP2), programs that connect to IP
addresses that are in the loopback address range may not
work as you expect. For example, you may receive an error
message that says that you cannot establish a connection.
CAUSE
This problem occurs if the program connects to a loopback
address other than 127.0.0.1. Windows XP Service Pack 2
(SP2) prevents connections to all IP addresses that are
in the loopback address range except for 127.0.0.1.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but
it is only intended to correct the problem that is
described in this article. Only apply it to systems that
are experiencing this specific problem. This hotfix may
receive additional testing. Therefore, if you are not
severely affected by this problem, we recommend that you
wait for the next Windows XP service pack that contains
this hotfix.

 

[Kent W. England [MVP]]

chris wrote on 19-Aug-2004 1:59 PM:

Hello,

Thanks to everybody who has responded this apparently
insoluble problem.

One of the replies prompted me to check Win XP Hotfixes
that have been loaded on the PC affected.

I found the following on Microsoft's site that pertains
to IP addresses. I do not know what a "loopback" address
range is but this problem looks suspiciously like my
problem. Before I go deleting or fixing with patches can
somebody comment if this looks like it is related to the
problem I originally posted.

DHCP doesn't use the loopback address, so I don't think that is your cause.

Check your event log to see if there are any DHCP messages that might
indicate a particular DHCP error. Until this is resolved, configure a
static IP address in the Alternate Configuration tab, so that you can
continue to try DHCP, but can get connectivity while DHCP is failing.

 

[Guest]

Kent,

I have a lot of Windows (SP2) hotfixes loaded and I also
noted that AdAware went haywire before my computer
started refusing to get IP from DHCP.

Is one possible solution to delete the Hotfixes (SP2)?

How does Ad-Aware figure into this (as per your comment
below)?

Thanks much for your help

Chris Maden

 

[Guest]

I have been using Alt Conf tab to assign a static IP
which allows me to communicate with other PC's on LAN but
it will still not connect with the internet.

 

[cctsurf]

I am using WinXP SP2, I streamlined it onto my older cd, and a
experiencing the exact same problem, I am using a Dlink di-524 route
with a Dlink dwl-g514 wireless card.
Before doing a wipe and fresh install of WinXP SP2, I was able to wor
quite quickly with the network, now quite randomly I will not be abl
to receive an address from the dhcp server on the router, or I wil
lose connection whether I'm doing a big download, just some we
surfing, or even with no traffic at all.
Helps would be greatly appreciated!
Thanks,
cctsur


-
cctsur

 

[Guest]

same thing here... DHCP fails, if I give an alternate address in the range
of the router I can see the other PCs on the netwok (as well as accessing the
shared folders) but no access to the Internet. Other thing, I cannot see the
web page of the router... while when I use my Win2000 laptop it all works
fine... I allowed all CIMP in the firewall, tried with the firewall turned
off... nothing

by reading all the threads I am it starts to be come clear that the issues
lies with SP2...

ciao Luca

I have been using Alt Conf tab to assign a static IP
which allows me to communicate with other PC's on LAN but
it will still not connect with the internet.

 

[Kent W. England [MVP]]

I have been using Alt Conf tab to assign a static IP
which allows me to communicate with other PC's on LAN but
it will still not connect with the internet.

When you use the web interface, you must stick with the same user name
or we can't tell who you are. If you are Chris, the original poster,
then this comment makes sense. If you are someone else, this comment
means nothing in Chris' thread.

Chris says that DHCP doesn't work but an alternate static address will
work on his LAN. Assuming that the other PCs are using DHCP and that
Chris static configuration is on the same LAN (reasonable since he can
communicate with local computers), he should be able to connect through
the router. What would stop that?

If you forgot to enter the default gateway IP address or the DNS IP
address(es), that would break your connection. Check those.

Comcast is a cable provider. All cable systems that I know use standard
Ethernet encapsulations with a MTU (max transmission unit) of the
standard default 1500 bytes. Most DSL providers use a PPP encapsulation
with a smaller MTU. If your MTU is too large, your connection usually
doesn't work, except for pings. Can you ping your DNS IP addresses? If
so, there might be an MTU problem, but that is a long shot, since I
assume that comcast is NOT using PPP encapsulation. I think it is likely
that your static config is incomplete, but try pinging the DNS IP
addresses and the default gateway IP address.

 

[smithcferg]

Like you, cctsurf, I have a di-524 with latest firmware upgrade. I hav
tried two different wireless connectors (linksys and smc usb adapters
and a direct connect using a lan. I have at times seen th
169.254.xxx.xxx numbers on all three connections to the router.
Sometimes there is no tcp/ip connection indicated with ipconfig, an
sometimes 0.0.0.0. And then sometimes the dhcp correctly delivers fro
the router, and I connect.

I am using win2000 w/ highest sv pak. And charter cable modem.
cannot explain why 1. The wifi connections fail fairly often (Route
signal is not that bad, and not that far away) 2. When they come back
they often come back with failed DHCP service, resulting in window
assigning the 169.254.xxx.xxx urls. It is often a big struggle to ge
a correct connect with the router, where I will tr
disabling/re-enabling adapter, releasing/renewing with ipconfig
restarting the connections from the wifi utility dialogue boxes
cycling from enabled wep back to disabled and then back to enable
again - until finally something works and I have a connection for
while anyway.

Is static assignment much more reliable than dhcp? And any ideas o
what might be going on here?

Crai


-
smithcfer

 

[cctsurf]

After fighting and fighting my DI-524 router, I found on the interne
that it is a firmware issue with the router. apparently firmware 1.0
worked really well for connection and dhcp, but did not have th
ability to use wpa-psk, or wpa encoding at all, we were limited to ver
crackable wep.
I continue to use 1.05 for the use of psk and have found that if
reboot the router periodically from the web, I do not have the multipl
x weekly lockup problem. Moving my computer so that I have bette
signal strength (turning it sideways from where it was, because it's
desktop and the back (with the antenna) was faced away from the router
I'm hoping and waiting for the next firmware, I think they have gotte
enough feedback on the issue, but I still don't see a firmware updat
since 1.05.
Hope that's helpful.
cctsur


-
cctsur