Networking Issues - Router & DHCP

[CKTurbo128]

Hi. I currently have a problem on my home network, which consists of four computers (two desktops, two laptops), all running Windows XP (three running Home Edition, one running Professional). I am using a Linksys EtherFast Cable/DSL Router (BEFSR41) to network all the computers and share internet access through my cable modem. Everything seem to work fine, except one of the desktop computers on the network is not working right with the network now. Before, this computer's network card listed that it's address type was assigned by DHCP (from the router) and the IP address looked fine - it was 192.168.1.101. However, now the address type no longer states that it is assigned by DHCP - it says "Automatic Private Address" and the IP address is listed as 169.254.126.244. <---[NOTE: That's not the IP address my ISP has given me; it's some kind of weird IP address that XP made up apparently.]

I've run the Network Connection Wizard several times, but the IP address would stay the same, with the stupid 169.254.***.*** crap address. I can no longer access the Internet with this computer, and even typing in "192.168.1.1" in the browser doesn't work - can't access the router's settings from this computer as if it weren't on the network at all. I've checked all network cable connections - all seem to be good and the lights on the router show the normal "green-yellow-orange" lights. All the other computers on the network work fine and their IP addresses are listed as assigned by the DHCP.

Strangely, this computer can still access other computer's files and the other computers can still send print jobs to this computer (the main printer is connected to this computer). I've tried looking through XP's help center and have found no solutions. Can anyone help me solve this problem?

- CKTurbo128

[engjohn]

I do not know your setup, but this should work.
Right click on my network places select properties.
Right click on Local area Connection and select properties.

double click on internet protocol(tcp/ip)
set it up to use a static IP
IP address should be 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1

dns use the ones supplied by your provider (ISP)
if not use these 207.178.128.20 and 207.178.128.21 untill your find yours.

You should work fine then...

[CKTurbo128]

Hmm, it's really strange. I set up the IP address, subnet mask, gateway and DNS numbers (from ISP) manually, but I still can't access the Internet. It's really strange (and annoying) - all the other computers are assigned IPs by the router's DHCP except this one... and it shares/prints network files fine (the network games don't work though on this one :( ) Any more ideas? Maybe the NIC card is bad? :confused:

- CKTurbo128

EDIT: One thing that I notice under the "Details" button under "Status" of the network connection on the other computers that work fine is that they have three extra labels: DHCP Server, Lease Obtained, and Lease Expires - while on the problem computer, it doesn't list them at all - if that helps. :eh?:

[engjohn]

click start, run
type cmd in the run box and press enter.
once the "dos" window is open type ipconfig /all and tell me what is
outputs... everything...

[CKTurbo128]

I've attached a .zip file containing the snapshot of my desktop on the problem computer that shows the ipconfig information - I couldn't get the picture down to 300 x 300 size restriction because at that size, the picture is too distorted to see the necessary information, so I had to put the picture in a zip file.

- CKTurbo128

[CKTurbo128]

Sorry for double posting, but I wanted to attach another snapshot of the ipconfig information from a computer whose Internet does work. I had to zip it again because of the 300x300 pixel limit.

I already see some differences between the problem computer and the working computers in the ipconfig information: in the problem computer, the node type is "unknown," while on the working computers, the node type is listed as "hybrid." Also, there is a connection-specific DNS listed for the working computers, while the problem computer doesn't have any. It also looks like DHCP is disabled on the problem computer as well. Thanks for helping me out on this.

- CKTurbo128

[Lusankya]

reinstall the network components.. you gotta trash your TCP/IP stack and make the system build a new one.

[CKTurbo128]

How do you get rid of the network components and reinstall it? Sorry, I'm new to networking. :(

- CKTurbo128

[Lusankya]

Hmm go to

start button/settings/network settings

open you local area connection properties and remove the tcp/ip stack. reboot then reinstall it. Will ditch the old copy and use a fresh stack

[CKTurbo128]

Strange, the uninstall button is grayed out for the Internet Protocal (TCP/IP) - is there any other way to uninstall it? (Note - I'm using Windows XP: Home Edition)

- CKTurbo128

[Lusankya]

you will have to remove the whole client then

remove client for microsoft networks
reboot
reinstall

*make note of exactly whats in there first and what the little symbol that goes with them is*

[CKTurbo128]

Hmm, I uninstalled the Client for Microsoft Networks and reinstalled it, but that same IP address (169.254.126.244) is still there. :mad: I tried to also type in "ipconfig /renew" under command prompt and it gives me this error : "An error occurred while renewing interface Local Area Connection : An operation was attempted on something that is not a socket." I am just about ready to go buy a new NIC - maybe the NIC is defective or something. I don't know, I still suspect that XP is the culprit and not the NIC, since it is supplying that weird IP address (169.254.126.244) and says that it's an "Automatic Private Address" instead of "Assigned By DHCP." Is it hopeless? :(

- CKTurbo128

[AMD'er]

tell you what to try here....1st right click on my computer, hardware and go to the nic card....or go to add or remove hardware... Remove the nic... powerdown and take the nic card out complete...true this might be takeing it to the extreme but just do it any way....Pop it back and and let XP reconginize it. then try the same steps as applying the static IP.

[Lusankya]

swap the nic's of the 2 machiens and see if they work that way

or at the very least.. swap them long enough to determine if it is the nic or the machine

[foxforcefive]

The 169.254.x.x address is one that is assigned when the NIC cannot get an address via DHCP.

I would do what AMD'er said to do before buying a new NIC.

My .02.

BL

[Kinerry]

all I can say is winxp is gay when it comes to network setting it likes to do everything itself to mess you up

[sa8nt]

"An error occurred while renewing interface Local Area Connection"


Not too familiar with XP Home but have you tried to use a generic "Administrator" username and password?

On w2k I've seen that error and was able to get in using my generic log in. For the Domain name I used the Computers name and not the network.

Once I was in and had Admin rights I was able to modify my network settings as described by others.

Again, this was for w2k pro not XP Home....so I don't know if this helps at all....

[frodoski]

Let us first go back to basics...

Have you considered the cable? A simple thing which can be overlooked. Is the cable properly inserted in the NIC as well as the switch/router?

Next...Open a command prompt type: ping 127.0.0.1. If all ping time out with no response you have a problem with TCP/IP. Note: the 127.0.0.1 is a local loopback address which can be used for testing the TCP/IP stack for proper operation.

Next...the 169.255.XXX.XXX address is applied only if a DHCP server (your switch/router) cannot be reached or if there are not enough addresses available in the DHCP address pool. Check the settings in your switch/router for the size of the address pool, it may be that the initial settings were set to a very low number of addresses. Increase the address range of the DHCP address pool.

Sometimes the 169.255.XXX.XXX address requires a re-boot to acquire a new DHCP address, ipconfig /release and ipconfig /renew doesn't quite fill the bill.

Try the reboot, then run from the command prompt ipconfig with no switches. I should look something like this:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.X
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.XXX

If not I would suggest getting a new cable.
Don't always jump at the hardware to correct a problem...think...it...through in a methodical way. Sarting with the basics. Some of which are listed above.

[CKTurbo128]

Hmm, I tried using another cable, but the same IP address was still present (although 127.0.0.1 pings fine in Command Prompt). The Linksys router that I use seems to be fine too (it's set to 50 users). However, I kind of fixed the problem (somewhat). I decided to take a chance on System Restore and see if it works. I used System Restore to restore my computer back to a point when I knew my Internet connection is working and it worked. Everything seems normal, with my primary Local Area Connection reporting "Assigned By DCHP" and 192.168.1.101 as its IP address. There is still a problem though; whenever I make any network changes, even if its a minor change, the Internet connection ceases to function and my Local Area Connection reports "Automatic Private Address" with that bad IP address, 169.***.***.***. :mad:

So now, I have to use System Restore whenever this computer stops getting assigned IP addresses by DCHP. It happens, but at least Internet access works now :rolleyes:. Besides that, another big problem has been formed: I can no longer play LAN games on this computer! Either this computer can't see the network games and other computers or it crashes the game entirely, with Windows XP complaining about a "Net_sendpacket" error (Half-Life/Counterstrike) when trying to connect to a network game :( . Doesn't this sound really odd? I'm perplexed. :eh?: I wonder if I can ever get this computer's network settings to normal without annoying issues... Thanks again to everyone who helped me out on this problem.

- CKTurbo128

BTW, the only thing that worked throughout the entire problem is the file/printer sharing and it still works. :)

[frodoski]

***Moan**Rubs forehead**massages temples as splitting headache begins***more moaning***

Hmmm....If I had to do a system retore just to get back to a point where I am able to reconnect to the network, I would be thinking seriously about reloading the OS **heavy sigh**. If you can save your data (i.e.: documents etc.) to another drive or partition on the system, and you have all of the software distributions for the applications you have loaded, flatten the system partition and reload the OS. It sounds as though there is something within the OS that is broken. I've been running XP Pro for about 4 months now at home and at work and have had a very similar issue much like the one you describe. I tried uninstalling and reinstalling the NIC, the Microsoft Network Client, TCP/IP...and all for nought. Soo...with clenched teeth I reinstalled and viola' all was right again.

I know that this "brain transplant" seems a bit drastic, but in the 5 years I've been supporting Microsoft platforms, it is sometimes the easiest way to solve a problem.

[mbigna]

I've seen similar problems in networks that I set up for SOHO clients. Something I always try anytime I see a weird IP address assigned is to power down the computer, then UNPLUG the computer from the outlet. I let it sit for a minute or so and then reboot. This often clears up the problem for me. I believe that this works (sometimes) because peripherals like NIC's and video cards actually aren't ever powered down completely even when shut down. The PSU maintains a trickle charge to some of these devices and I think that allows them to maintain certain settings (even the unwanted ones) in order to facilitate a faster boot.

[CKTurbo128]

YES! YES! YES! I've fixed the problem entirely - no more System Restores and the network games work. The culprit? It turned out to be the firewall program that came with my virus scanner, McAfee VirusScan 6.0. (Glares at McAfee :mad: ) I uninstalled the program, suspecting that it's firewall components might be the cause of the problem. And it was. Anyway, I'm glad I could fix the problem without reinstalling Windows XP. Thanks again to everyone who helped me out on this problem.

- CKTurbo128

[frodoski]

Good Job!!

I'm glad you stuck with it and troubleshot the system. I never have been a McAfee fan. I had a virus infestation several years ago, McAfee coul not touch it. I lost over a years worth of data. I've had great success with Norton though.

Very well done.