|
|
djb3032
new user
Reg'd: Sun
Posts: 14
|
|
Hello,
I have an IP addressing problem with my home network. I'll try to be brief.
I've been using two PCs (one desktop, one laptop) with a Linksys 4 port switch for about two years. All are set up for DHCP and I've had no problems at all until recently. Both PCs are Dells running Windows XP Professional SP2.
In the last week, the laptop has begun exhibiting strange behavior. When I boot the laptop and then connect it to the switch, the router attempts to provide an address (usually 192.168.1.103) but the laptop will not accept it. Instead, I receive a limited or no connectivity notice and the IP address on the PC reads 169.254.73.173. Using Ipconfig /renew, release, etc. do not help.
If I connect the laptop to the switch before I boot, everything runs as I would expect. The laptop accepts the address given and all is well.
This isn't normal behavior for this PC. In the past, I would frequently boot then connect, disconnect, etc., throughout the day with no address assignment issues. Through all of this, the desktop runs as always with no problems. That leads me to suspect the switch is not the problem.
I've read that 169.254.X.X addresses are not valid addresses and are assigned if XP cannot obtain a serviceable address. That I understand, but this connectivity problem is new.
This problem occurs when I hardwire into the switch and when I attempt to connect wirelessly to a Linksys AP that is also connected to the switch.
Firewall and other security settings have not been changed recently.
Is TCP/IP or Winsock corrupted?
Thanks.
djb3032
|
|
BurrWalnut
Chippendaler
Reg'd: Tue
Posts: 3458
Loc: London, England
|
|
I haven’t tried it but this has helped others, download and run it http://www.snapfiles.com/get/winsockxpfix.html
--------------------
───────────────────────────────────
Fine English furniture is the new rock 'n' roll
The Chippendale Society
|
djb3032
new user
Reg'd: Sun
Posts: 14
|
|
Thanks for the reply.
The suggestion, unfortunately, did not remedy the problem.
Any other thoughts?
djb3032
|
mgmcc
regular
Reg'd: Thu
Posts: 220
Loc: Dundee, Scotland
|
|
Have you tried giving the laptop a fixed IP address in the 192.168.1.x range?
It could also be a hardware problem - failed ethernet cable or the laptop's network adapter.
--------------------
Mike
|
djb3032
new user
Reg'd: Sun
Posts: 14
|
|
Yes, Static addressing works. However, due to my home network set up, dynamic addressing is a more desirable arrangement and that's what I've been using with this equipment for years.
It could be a hardware problem, however the failures occur very consistently depending on whether I connect to the network before or after I boot.
|
mgmcc
regular
Reg'd: Thu
Posts: 220
Loc: Dundee, Scotland
|
|
Quote:
However, due to my home network set up, dynamic addressing is a more desirable arrangement
Why? There shouldn't be a problem giving an individual item in the network a fixed IP address in the same Subnet as the router, but outside the router's DHCP pool. The rest of the networked items can continue to get their addresses by DHCP.
--------------------
Mike
|
djb3032
new user
Reg'd: Sun
Posts: 14
|
|
OK. I tried what you've suggested. A static address gets me part way there: I have a valid address but still no connectivity.
As to your question regarding my preference for all dynamic addressing: I hope to solve the root cause, not resort to static addresses and leave a problem lurking in the system. The PC has worked with dynamic addressing for years and suddenly stops? I want to discover what happened or what I did wrong so I can correct it and learn from it.
Thanks for your help. I appreciate you taking the time to contribute.
|
djb3032
new user
Reg'd: Sun
Posts: 14
|
|
Hello all,
This is a quick note to say I've managed to correct the problem I posted. I changed the APIPA settings found under the TCP/IP protocol "Alternate Settings" tab.
I left the machine set for DHCP, then set up a static address under the Alternate Settings tab. Initially the machine used the alternate static address, however, since then, the PC has been accepting the address offered by my router. In fact, I'm typing this response from the formerly troublesome machine.
Thanks for the assistance.
djb3032
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
