[serverguy]

Also, can you try pinging another computer on your network?

Just open up Command Prompt as before and type in ping and then an IP address of another computer on your network.

Then, try and ping your suspect computer from another computer in the same way.

Then, try and ping www.google.com and see what happens.

Lastly, open up command prompt on the suspect computer and type in tracert www.google.com

It will try and find Google. When it finishes, or returns an error, right click and choose Select All and then press Enter. That will copy it all to the clipboard.

Post that in your next reply.

Then do exactly the same tracert on a computer that does connect to the internet.

[serverguy]

I'm off to bed in a second but if all the results of those pings / tracerts turn out to be negative you can try running LSP Fix.

Download here: http://www.spychecker.com/program/winsockxpfix.html

Open the program and first of all make a backup of your registry by clicking ReG-Backup. Save the backup to your desktop or similar.

Then run the actual tool by clicking Fix.

Reboot.

Test internet.

[Anticleptic]

Originally Posted by serverguy

Also, can you try pinging another computer on your network?

Just open up Command Prompt as before and type in ping and then an IP address of another computer on your network.

Request timed out.

Then, try and ping your suspect computer from another computer in the same way.

Request timed out.

Then, try and ping www.google.com and see what happens.

Request timed out.

Lastly, open up command prompt on the suspect computer and type in tracert www.google.com

It will try and find Google. When it finishes, or returns an error, right click and choose Select All and then press Enter. That will copy it all to the clipboard.

Post that in your next reply.

C:\Documents and Settings\Steven>tracert www.google.com

Tracing route to www.l.google.com [72.14.205.103]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.

Then do exactly the same tracert on a computer that does connect to the internet.

C:\Documents and Settings\Kim>tracert www.google.com

Tracing route to www.l.google.com [72.14.205.103]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 9 ms 7 ms 7 ms 10.67.208.1
3 13 ms 15 ms 12 ms d226-8-21.home.cgocable.net [24.226.8.21]
4 13 ms 14 ms 13 ms cgowave-0-105.cgocable.net [24.226.0.105]
5 29 ms 14 ms 12 ms 74.125.49.25
6 15 ms 18 ms 14 ms 66.249.94.90
7 16 ms 27 ms 18 ms 72.14.232.66
8 16 ms 14 ms 14 ms qb-in-f103.google.com [72.14.205.103]
Trace complete.

[Anticleptic]

Originally Posted by serverguy

I'm off to bed in a second but if all the results of those pings / tracerts turn out to be negative you can try running LSP Fix.

Download here: http://www.spychecker.com/program/winsockxpfix.html

Open the program and first of all make a backup of your registry by clicking ReG-Backup. Save the backup to your desktop or similar.

Then run the actual tool by clicking Fix.

Reboot.

Test internet.

Didn't fix it.

[Anticleptic]

Also, I can access files on other computers on my network from the suspect computer, but I cannot access files on the suspect computer from other computers on my network. Just noticed this as last time I only tried from my suspect computer.

[serverguy]

OK. I have absolutely no more ideas.

Everything I can think of has been tried.

Can you try restoring back to a System Restore Point before the problem started?

http://www.microsoft.com/windowsxp/u...emrestore.mspx

[Anticleptic]

Originally Posted by serverguy

OK. I have absolutely no more ideas.

Everything I can think of has been tried.

Can you try restoring back to a System Restore Point before the problem started?

http://www.microsoft.com/windowsxp/u...emrestore.mspx

I tried system restore already with no luck. I suppose I'll take it in to a repair shop this afternoon and see if they can find something wrong with it heh.


Thanks for all the help.

[serverguy]

Originally Posted by Anticleptic

I tried system restore already with no luck. I suppose I'll take it in to a repair shop this afternoon and see if they can find something wrong with it heh.


Thanks for all the help.

Sorry I couldn't help you get it fixed.

Hopefully the repair shop will notice something wrong.

Make sure you tell me what was wrong so I know for next time