PDA

View Full Version : ibm thinkpad 600 wont connect to the internet

90GT50
02-13-2008, 06:59 PM
xp, netgear card, used to work back in the day, but now it wont, any ideas? And yes, it shows connection, and all the other computers on the network work fine.
PWTRTXSS
02-13-2008, 07:02 PM
Tried reloading the netgear card drivers yet?
90GT50
02-13-2008, 07:04 PM
[QUOTE=PWTRTXSS]Tried reloading the netgear card drivers yet?[/QUOTE]Yep, it shows it has a connection, but no internet pages working.
trey85stang
02-14-2008, 04:08 AM
wtf, quit using a fossil and it might work.
black90gt
02-14-2008, 08:07 AM
maybe you are having a DNS problem?

Click on start > run

type in cmd

Now type in ping 4.2.2.1

Do you get any results?
90GT50
02-14-2008, 09:08 AM
[QUOTE=black90gt]maybe you are having a DNS problem?

Click on start > run

type in cmd

Now type in ping 4.2.2.1

Do you get any results?[/QUOTE]I'll try this when I get a chance, I left it at home today.

Shut up, Trey! It worked fine before, lol.
1BADPONY
02-15-2008, 05:08 AM
I you get results then try pinging google.com
black90gt
02-17-2008, 06:45 AM
any luck?
90GT50
02-17-2008, 04:41 PM
[QUOTE=black90gt]any luck?[/QUOTE]
it said destination host unreachable. 100% lost.
black90gt
02-18-2008, 03:06 AM
[QUOTE=90GT50]it said destination host unreachable. 100% lost.[/QUOTE]

Hmm, ok. What kind of router are you using? Can you: goto start > run, type in cmd. Now type in ipconfig. Paste the results.
90GT50
02-18-2008, 07:52 AM
[QUOTE=black90gt]Hmm, ok. What kind of router are you using? Can you: goto start > run, type in cmd. Now type in ipconfig. Paste the results.[/QUOTE]It's a netgear router.

autoconfiguration IP address: 169.254.109.117
Subnet mask:: 255.255.0.0
black90gt
02-20-2008, 03:50 AM
Wireless or wired connection?
90GT50
02-20-2008, 08:43 AM
[QUOTE=black90gt]Wireless or wired connection?[/QUOTE]wireless
Hunt4m3x
02-20-2008, 10:57 AM
Its not getting an IP. Make sure you are using the right wep and the WIRELESS BUTTON IS ON!
90GT50
02-20-2008, 11:16 AM
[QUOTE=Hunt4m3x]Its not getting an IP. Make sure you are using the right wep and the WIRELESS BUTTON IS ON![/QUOTE]Right wep, and no wireless button, it shows connection, but no intarnetz still.
Hunt4m3x
02-20-2008, 11:20 AM
[QUOTE=90GT50]Right wep, and no wireless button, it shows connection, but no intarnetz still.[/QUOTE]


start run -> cmd


ipconfig /release

wait 2 mins.

ipconfig /renew


what does ti say now/
90GT50
02-20-2008, 11:40 AM
[QUOTE=Hunt4m3x]start run -> cmd


ipconfig /release

wait 2 mins.

ipconfig /renew


what does ti say now/[/QUOTE]I'll check in about an hour or two, and get back to you, it's in my delivery van, and another employee is out doing a delivery in it, waiting on him to get back.
90GT50
02-20-2008, 04:18 PM
[QUOTE=Hunt4m3x]start run -> cmd


ipconfig /release

wait 2 mins.

ipconfig /renew


what does ti say now/[/QUOTE]
Windows IP Configuration

An error occurred while renewing interface Windows Network Connection 3: An operation was attempted on something that is not in a socket.
90GT50
02-21-2008, 03:34 PM
Any other ideas?
Hunt4m3x
02-21-2008, 06:58 PM
[QUOTE=90GT50]Windows IP Configuration

An error occurred while renewing interface Windows Network Connection 3: An operation was attempted on something that is not in a socket.[/QUOTE]

http://support.microsoft.com/kb/318584

SYMPTOMS
After you install a modem on your system, you may not be able to connect to the Internet. When you try to release and then renew the IP address, you may receive the following error message:
An operation was attempted on something that is not a socket.
Back to the top

CAUSE
This behavior may occur if the WinSocks library or the TCP/IP stack are corrupted.
90GT50
02-21-2008, 08:37 PM
[QUOTE=Hunt4m3x]http://support.microsoft.com/kb/318584

SYMPTOMS
After you install a modem on your system, you may not be able to connect to the Internet. When you try to release and then renew the IP address, you may receive the following error message:
An operation was attempted on something that is not a socket.
Back to the top

CAUSE
This behavior may occur if the WinSocks library or the TCP/IP stack are corrupted.[/QUOTE]How would I go about fixing that
Hunt4m3x
02-21-2008, 08:50 PM
[QUOTE=90GT50]How would I go about fixing that[/QUOTE]


http://www.xp-smoker.com/freeware.html

Download the XP TCP/IP Repair

and do both. If it doesn't work after that, you need to reinstall windows.
90GT50
02-25-2008, 08:24 AM
[QUOTE=Hunt4m3x]http://www.xp-smoker.com/freeware.html

Download the XP TCP/IP Repair

and do both. If it doesn't work after that, you need to reinstall windows.[/QUOTE]Will do now, thanks.
edit: tried it, and no luck, guess I need to get it reinstalled.