Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hi I have a AMD XP 3200 1.6 with 256 ram.
I have a 30 gb hard drive and a on board network card. I use a cable modem and have been using it on this computer for 1 year now. All of a sudden I can't go online. But if i use another computer they go online w/o any problems. I brought 2 laptops from work. When I go to check the ip # I get a 169 #. I can not release or renew all in dos. I am suprised I see a 169 #. I called my cable provider and they said to return the pc because it is no good. I cant believe they don't knwo how to fix this. Does anyone know why I would get this 169 ip and how to fix it?Thank you.
Paul
I'm sure you have already checked this but
do you have on "Obtain an IP address automatically" on your adapter? The IP isn't already in "Use the following IP address" is it?
0 
This is the default NIC autoconfig ip address. When DHCP client failed to get an ip address from the network, it return to this address.
Apparently, your cable-modem is offline and is using this addressing sheme for diag/setup purpose. After a reboot, if the modem still off-line, call your ISP.
0
There are a number of reasons why your computer may not be connecting..
If you cannot release/renew there are 3 things that could be the problem.
One the most obvious is the physical layer. Is the ethernet cable pluged into the NIC and the other end pluged into the router/switch/cablemodem?
Next is your NIC bound to TCP/IP set to "obtain IP address automatically" (DHCP). You wont be able to release and renew if your IP is set statically.
Thirdly your TCP/IP stack is corrupted and needs to be reinstalled. This is an easy task on any OS prior to Windows XP because TCP/IP is vital to the operation of XP you have to reinstall windows in order to fix the TCP/IP stack. On previous versions of windows you can just delete the TCP/IP stack and re-add it to the list of protocols bound to that Network Adapater.
I've run into this problem many times with windows XP clients (I noticed that's what you're running). You don't need to reformat the PC just reinstall the WindowsXP OS. However whenever reinstalling anything dealing with the OS I recommend you backup your data. Usually if this is a corrupt TCP/IP stack you'll get the following error message when trying to release and renew your IP address:
"An operation was attempted on something that is not a socket."
(from the CMD prompt I don't believe you'll get it by using the GUI).
Another problem is that your ISP's DHCP server is down and not functioning, and in that case they'd have a s--- LOAD of phone calls! So i doubt that to be the problem. :D
ALSO dont ever take advice from a level 1 tech. THEY KNOW NOTHING! If he told you to return the computer and I was his manager I'd fire him in a second. I hate it when techs overstep their boundaries or try to place blame on other vendors/manufacturers.
wirelessGuru
MCSE,MCSA,MCP
0
I just checked the MS KnowledgeBase and you may be able to reinstall TCP/IP on WinXP useing the following command:
netsh int ip reset resetlog.txt
Here's the KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;817571I've yet to see this method work in the field. I know it hasn't worked in the past for me, but feel free to give it a shot before you reinstall XP.
0
I have seen netsh int ip resetlog.txt work, but only if you get your ISP to restart your entire dsl line for you at the same time. It does however not work everytime.
0
Also check to see if any windows updates where done recently on your machine. There where two recent microsoft updates that where sent out to XP users that seem to cause people to keep the autoconfiguration ip(169.X) ip. I would also say that the info that wireless guru presented was flawless, these steps should have been used by any tier1 representative of your ISP...trust me, I was one. I am now tier 1.5 Helpdesk. Another possability for you to point out to your isp if you have not had that windows update, there is a possibility that your ISP ip pool is low. They have to many subcribers in a particular area and the DHCP server cannot server all requests. This is not a direct impact to the DHCP server, so the call center would not necessarily be able to easily identify this problem because we would not receive a vast number of callers. Hope this info helps!!
0
i went thru the issue and i have solved several issues like this. It is because the tcp/ip is corrupted.
Go to the websitewww.urls.youthizens.com
and click on the link which says winsocks.
download this file on to the desktop and run it on the desktop computer which has got the problem ie the error message "An operation was attempted on something that is not a socket."click on fix.
once it has fixed the issue restart the system and try to connect to the internet. i believe that the issue must be solved.
send me a mail incase ur issue is fixed.
bye
0
with a 169 ip address:
there are two main groups that could be causing this problem.
1. hardware ( the most frequent caused) A. Defective Nic. B. Defective Ethernet cable (mostlikely - attempt with usb to eliminate possibility) C. Defective port on modem(most unlikely)
2. Software - A. Misconfigured firewall/antivirus blocking communication to modem. B. Misconfigured tcp/ip settings. C.Corrupt Tcp/ip D.Corrupt drivers for nic. E. winsock(most unlikely but possible). F. which should be tried first but i forgot is a complete powercycle. Unplug the modem, wait a full 30 secs. plug back in. Reboot the computer or release/renew ip. Hope this helps but more then likely its the ethernet cable.
0
Many thanks Lokesh. Spent several hours trying to fix TCP/IP problem on daughter's PC. Then found your tip to download winsocks file from youthizens.com . Problem fixed in minutes. Would recommend to anyone else whose XP has got in a mess. Brilliant program!
0
I have seen this quite a bit myself, what I have got to work almost 100% of the time is to shut down all equip (including router and modem) connect modem to usb (most new modems have this option) power up everything starting with modem, should have a valid ip now, if not release/renew then if you get a valid ip power down all equip reconnect ethernet, release/renew if needed.
0
I have a similar prob I get the 169 number randomly it gets a valid IP from DHCP sometimes but not all the time any thoughts?
0
Dcetta,
Follow Lokesh's advice in response 8. I've been trying to solve this for a long time. Nothing seemed to work .................until now!!!
Way to go Lokesh!!!
SullyD
0
WARNING: Lokesh (message #8) offers a third-party link to download a winsock repair utility at www.urls.youthizens.com which in turn links to the file file named ws.exe, which is downloaded from http://unix.za.net/~youthhizens/.
This file appears to be an old version of WindowsXPFix.exe which is available from
http://members.shaw.ca/techcd/WinsockXPFix.exe
The author of both programs is:
http://members.shaw.ca/techcd/
Option^Explicit Software Solutions
cc Theron Skryba
Winnipeg, Manitoba
Canada
Comments email techcd@shaw.caws.exe claims in its title bar to be version 1.2, but the file's properties indicate that it is version 1.0.0.0. The version of WindowsXPFix.exe that is available is 1.1.0.13.
I recommend getting the version 1.1.0.13.
More information and other winsock repair utilities are available from
http://www.cexx.org/lspfix.htm
More information about the possible causes of this error as related to spyware is available at
http://www.cexx.org/newnet.htm
Another possible cause is if you uninstall McAfee Personal Firewall via Control Panel's Add/Remove Programs. See
http://support.microsoft.com/?kbid=316522
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
