Cannot Acquire Network Address

so under "status" when you enable the connection, what does it say? if it says disconnected then its a cable/adapter problem, if it says aquiring for ages then its a ip issue.

It's the latter, but the bizare thing is that every other PC on the network works just fine. The new one is the one that is fracked up. Will it make a difference if I try in on another interrnet connection?

y dont get it
Gimme your ISP name , is it phone line or cable ?
Right ur soons pc concets to router - modem - ISP. So in this case u gotto connect to router which must be configured to alow you to aces internet . So follow istructions how to configure it aswell. Then its the way YOU connect to router - wireles or cable ?
The command lines y gave u previously couldnt fale in settings like these your pc - (router)- modem - isp.(sometimes routers solve all problems with ip aquaering them selves)
So the way y understand it you'r not wireing things up correctly.
Lets make sure that modem is fine with ur pc by instaling it there . If it does work fine the only thing that is left is to configure router to alou you to acess internet .And that may involve mapping ur pc to connect frough modem , but as y sayd router is in between so u need to check settings.

Well I fixed the problem...sort of. Tore the whole beast down, put it all back together re-installed everything and it all worked just fine. I have no idea what caused it this past week, but I am off to deliver the computer in a few hours.

Thanks for all the help

well done
Probably ur registry keys were corupted in some way .

jobeard,

Just want to say thanks. My laptop was unable to get an ip address (intel 10/100 chipset) and was set for autodetect. Unistall, reinstall, updated drivers, You would figure that that would work fine, our network is running at 100 mb and the jack and cable work fine. For some reason I had to force the card to run at 10mbs only then would it acquire an IP address. All other pc's on the network are running at 100mb. To be hobnest I really dont see a noticeable difference in perfomance. Thanks

You're welcome and thanks for the feedback -- this will help someone else greatly

It's mindless that the broadcom (as I last experienced) needs to regress all the way down
to 10mb half-dup, and I think if given enough time, someone could deduce the option that is
causing the 100mb full-dup to fail.

As I don't have the broadcom card myself, I can't experiment further ... sigh.

Jeff

hi peeps...this is the first time that i will be posting a comment here...anyway, regarding your problem, since that you are getting a 0.0.0.0 ip address...most cases would be that the nic is not properly installed or the dhcp client in the computer is not started...you might want to try these troubleshooting steps..

1. disable and then enable the nic in device manager. to do it, go to control panel, click on system, device manager and look for network adapter. click on the plus sign so that you can see the nic that is installed. make sure that there are no marks on it like !, x, ?. if it has a ! or ? on it, try to reinstall it. if it has an x mark on it all you need to do is to right click on the icon and then click on enable.

2. after doing that go to network connections (start, control panel, network and internet, network connections) right click on local area connection and then click on disable and then riight click on it again and then click on enable. check if its already giving you a "connected" status. if its still the same, try to right click on the "local area connection" icon and then go to properties. make sure that the "internet protocol (tcp/ip)" under "this connection uses the ff:". restart the computer as well as the modem to refresh the settings and then try it again.

3. try restarting the dchp client. to do that, click on start, run and then type in "services.msc". look for "DHCP CLIENT" right click on it and then choose "stop", right on it again and then click on "start". after doing that, try to go to command prompt (start, run, type in "cmd", click on okay, type in "ipconfig" in command prompt) to check if you are already getting a valid ip address or a 169.x.x.x ip address

4. if you are already getting a 169.x.x.x ip address, restart your computer and modem (if your modem has a battery pack, take out the battery pack and then unplugged it from the power source. wait for about 10 - 15 seconds, place back the batteries and then plugged back in the modem). disable any security softwares that you have (firewalls, antivirus, anti spywares). and then try to release/renew the ip address ( start, run, type in "cmd" click on okay, type in "ipconfig /release" and then press enter, tyoe in "ipconfig /renew" and then press enter. if you get an errpr message that says "unable to contact DHCP server", call your ISP because there is a problem on their end.


hope these troubleshooting steps would help you.

Fundamental, my dear watson

Not forgetting...

5. try another connector wire....

Did nobody notice? It worked after he disassembled and reconnected......nice checklist skorch

Had the same problem with a lap top and it worked for me.... Thanks