Printable View
I'm trying to fix friend's system: WindowsXP
The problem is that the system never acquires an IP. The icons comes up saying that the "local area" connection is established but status is always "acquiring IP address" The system nevers go any further than that.
1. different Ethernet cards ... nothing
2. different routers ... nothing
3. YES YES... it's set to DHCP
4. tried diferent "connection wizard" setups... nothing
5. it can ping 127.0.0.1
pls help as soon as you can ...
What's ipconfig show?
And if it is set to DHCP, set it to recieve a static IP. Do you have a firewall or anything that could be preventing your computer from making the connection to the router?
Where is it getting its IP from...an ISP??Router?
Can you ping them???
If not check\change the cable...
All sp\updates installed?
MLF
Edit>
Remove tcpip reboot and reinstall...that may help.
Binding to various cards may have mucked things up
Have you just tried setting it statically?Quote:
1. different Ethernet cards ... nothing
2. different routers ... nothing
3. YES YES... it's set to DHCP
4. tried diferent "connection wizard" setups... nothing
5. it can ping 127.0.0.1
Then and at least making sure you still have a connection some way. Does your friend have only that one machine?... Static IPs are pretty manageable as long as you have less than 10 systems or so.
I get a problem like this with wireless a lot... It gets the Mac connection, but the DHCP doesn't configure properly. If this is the case you can at least verify the connection by setting a static IP and going from there.
Open a command prompt window.
Type 'ipconfig' (without the quotes) to view the status of the computer's IP address(es).
If the computer is holding a current IP address, type 'ipconfig /release' to let go of the address.
Type 'ipconfig /renew' to obtain a new IP address (whether or not the computer is holding a current address).
Hope that helps.
Hrm.. well...
Is there a firewall running on this XP box that your friend may have installed, blocking DHCP broadcasts and unaware of the repercussions?
Have you checked the settings on the routers to make sure that the DHCP server is in fact running?
Well there's two more ideas for you anyway...
This happens some times when spyware is removed from a system. You need to re-set tcpip.
You cant remove tcpip from win xp, you can re-set it. Follow the intructions at the link below.
http://support.microsoft.com/default...b;en-us;299357
sorry for late reply...
the static addy did it... WTF
why would this happen???
Is the router set up to give out x amount of DHCP addresses then it stops? Is the router set up to give out any DHCP IP's? You said the computer was set to recieve an by IP by DHCP, maybe the router was never set to give any out?
Looks to me like there's either a firewall on the box stopping the DHCP requests from getting out, or the replies from getting back in, in which case disabling the firewall would reveal thie problem, or that the router is not running a DHCP server.
Windows XP firewall was disabled and there wasn't any other related software installed on the computer. Both, the netgear router and westell DSL modem were set to give DHCP. Do you guys have any other explanation.
The router AND the modem?
Perhaps the two of them are giving out addresses on different subnets. If this is the case, the modem may assign an address of 192.168.1.100, but the router may be operating on an address of 192.168.0.1. The XP host and the router are now on different subnets and cannot communicate with each other. Try turning the DHCP server off on the hardware that the XP host is not connected to so conflicts like this will be avoided. I have encountered this problem before.
In a home LAN setup, only the hardware directly attached to the computer should be set to give out DHCP addresses, in most cases. The only exception would be a switch between the computer and the router.
Check also that the modem is not set tou act as a router as well. If it is capable of DHCP assignment, I am thinking that it can route traffic as well. See if there is some way you can set the modem into a bridge mode so it will not do this. My DSL modem can act as a router as well as modem, so yours might have the same capability.
Either that, or, assuming that the modem is also a router, use the modem only and not the router as well.
But I think your problem lies in the fact that you have two conflicting DHCP servers on your network. Look into that first, and then the other ideas I have suggested.
Striek... and others
I wouldn't come here to ask about a obvious fact as you've just stated. The problem is somewhere else.
Computer was directly connected to the modem which I know is set to give out DHCP. It is the standard that Verizon gives out to in NYC therefore I've worked w/ this modem many times. The router was attached to the system ONLY TO TEST IF THE PROBLEM ISN'T IN THE MODEM. THE DEVICES WERE NEVER CONNECTED AT THE SAME TIME. There's no subnet conflict. The solution was to set the system to static IP.
to work w/
westell modem
IP 192.168.1.50
Mask 255.255.255.0
GWay 192.168.1.1
netgear:
IP 192.168.0.2
Mask 255.255.255.0
GWay 192.168.0.1
So again ... WTF??? Why won't the DHCP work. I did, reset TCP-IP.
I would bet it has to do w/ f***ing WindowsXP
Okay, let's start from the beginning and be very clear on what happens. Disconnect the computer from the modem and throw the router aside. Pop up the network connections screen and set the computer to receive an IP by DHCP (see attached image). Make sure you are doing this to the right ethernet device if you have more than one as I do. Shut down the computer completely now.
Next, shutdown the modem completely. Yes, I mean pull the plug out of the wall. Wait 30 seconds and replug it back in. Now wait until the modem has fully connected and is functional (my modem has lights indicating that it is fully ready; it depends on your modem). Now plug the ethernet cable into the router and computer and start the computer up.
Once started, give the computer a few seconds to obtain an IP. Start a command prompt and type ipconfig /all and copy/paste the results here.
This sounds simple and I'm sure you've done it from the beginning, but I'm curious as what ipconfig will show when the modem is reset.
mira ... the system won't work w/ any type of DHCP
doesn't matter what order you turn things on or off. doesn't matter if you reset modem or router or bring a cisco 2000 series from NSA
it won't WORK w/ dynamic IP
Well then there must be a reason it does not work. Resetting the modem is a good way to start. I realize I forgot to post the image in the other post so here it is. Why not just copy/past the results of an ipconfig /all?
unhappy
Please humour an old fart and test the modem in a different box, and a different modem in that box.............it might be a hardware issue?
Hey, an automobile works fine until it stops?..........and it was working just fine 30 seconds ago............ but that was when he installed SP2?
I think that there might be an SP2 problem here?
:)
The modem and the router are both fine. i've tested them and used them on many machines before and the router is set up right now. i changed different cables and i changed different NIC's.
I'm thinking it is a XP problem ...
So if you connect a different machine right now, it would give it an IP automatically and it would work?
Hi unhappy,
Don't know if these will help or not...maybe they might at least lead you in the right direction...
http://www.practicallynetworked.com/...icbroblems.htm
Windows XP Network Troubleshooting
http://www.microsoft.com/resources/d...f_omn_bgej.asp
Troubleshooting Microsoft Networking
http://support.shaw.ca/troubleshooting/dhcpxp.htm
Troubleshooting - DHCP for Windows XP
http://www.microsoft.com/technet/pro...2cdcdc7ad.mspx
Troubleshooting DHCP clients
sorry...best I can do!
Eg ;)
I don't know if you've tried this...Quote:
to work w/
westell modem
IP 192.168.1.50
Mask 255.255.255.0
GWay 192.168.1.1
netgear:
IP 192.168.0.2
Mask 255.255.255.0
GWay 192.168.0.1
....You've mentioned this is a router, but does it function as a switch as well? (many devices can function in either mode)
If it does I would set all machines to the same range of IP addresses *192.168.0.xxx /24* for example. This may allow the machine to just act as a switch and solve the problem for you...
... If nothing else it's just something else to try... Hope you get it fixed.
Jeez... let's all go running around trying this and that.....
put a sniffer on the box and do an:-
ipconfig /renew....
Then we can see what the heck is going on..... if you don't then you will keep guessing until you or the box dies......