XP LAN problem

Printable View

January 29th, 2008, 03:02 AM
westin

XP LAN problem

Hello all, I have sort of an interesting issue... I have a desktop computer dual booting XP SP2 and Ubuntu. It has a wired internet connection... the connection has been working without any trouble... today my wife booted to XP, and could not load a page... I was at work and told her I would look at it when I got home. The puzzling thing is that it works in Ubuntu, but not windows. In XP I can ping the router, and the external gateway. Ping the DNS servers, but cannot pull a page, or ping a hostname. I tried manually entering the DNS information, but that didn't help. I tried bypassing the router and plugging directly into the DSL modem, but still no luck... rebooted to Ubuntu just to make sure... worked like a dream... I even refreshed the page a couple of times just to be certain... then booted back to windows, and reset TCP/IP

Quote:

netsh int ip reset asdf.txt
netsh winsock reset

rebooted. still no luck. Killed the firewall. No change. It was working fine yesterday... no programs were installed/uninstalled. No new hardware... I am pretty well puzzled at this point... I would reinstall the drivers for my nic, but I find it weird that I can ping all over inside my network, and some external addresses, but cannot resolve hostnames. The other two computers [both XP] connected wirelessly, are working fine. Any help or suggestions would be greatly appreciated.

Thanks,
Westin
January 29th, 2008, 03:33 AM
oofki

Try lspfix?
January 29th, 2008, 03:35 AM
westin

Thanks for the reply oofki I have not heard of that... I will give it a shot... I presume it is an application? I am starting to suspect malware... I am doing an adaware scan, and it has picked up a few items... just have to wait until it finishes...

edit: turns out the malware it detected were just cookies. I tried LSPFIX, but it found no errors.
January 29th, 2008, 08:37 AM
fourdc

Had a similar DNS issue with my network. Had to call the DSL provider and get the passwords for the DSL modem as it had a DNS configuration that was overriding the XP DNS config.

I'm using OpenDNS for my DNS server and its been working great.
January 29th, 2008, 09:04 AM
SirDice

If ping works the TCP/IP stack and NIC drivers are fine.

Did you check the hosts file?
January 29th, 2008, 01:05 PM
oofki

What did LSPfix find for LSPs? Even if it doesnt find errrors that doesnt mean that there arent problems I am sorry for not specifying. The other thing you can try is WinsockFix it has a lot of fixes built in that you may have over looked.
January 29th, 2008, 04:09 PM
moxquito

This sounds like a browser issue too me if your able to ping out to external IP's. If you try going through explorer does it work? Also have you tried to browse by IP?
January 29th, 2008, 04:28 PM
morganlefay

Sounds like a DNS issue..

From command prompt> ipconfig /flushdns

MLF
January 29th, 2008, 05:55 PM
westin

oofki - mswock.dll, winrnr.dll, rsvpsp.dll were all in the keep box. The remove section was empty.

SirDice - Host file looked ok. Thanks for the suggestion.

moxquito - I actually was mistaken. I can ping my dns servers, but not any other external address, I tried browsing by ip, but had no luck.

MLF - I will give it a shot. thanks...

just tried it... didn't work... :( thanks for the idea though.
January 29th, 2008, 06:31 PM
xiphias360

Weird. A friend called me a couple days ago with the same problem. He had a 2wire dsl modem and everything looked good but he wasn't able to surf. He was looking at it for a friend of his, and he brought his laptop over and everything worked but just not on the original machine. After I was all out of ideas he resorted to the tried and true wipe & reload, lol. Everything worked after that so I assume there was some malware at play. There's a few new IE6 & 7 exploits running wild and some exisitng FF ones, so it doesn't surprise me...
January 29th, 2008, 06:48 PM
morganlefay

Yeah....sounds like crapware....

If the nic works with Ubuntu...its not hardware??

Could be a driver issue...and there was that recent MS patch for TCP\IP.

Hard to say.....

Try pulling your DNS from your ISP\Router???

MLF
February 12th, 2008, 03:40 AM
westin

Sorry to pull this one out of the archives, but I just today was able to fix the problem. After trying countless suggestions from people online and at work, I decided to ask the trainer at my job. This guy is incredible. He knows more about the inner workings of these blasted machines than anyone I have ever met... after explaining the problem and all of the attempts I had made at solving the issue, he suggested running:

Quote:

sfc /scannow

The process had barely started when I noticed AVG updating itself. I was ecstatic. I immediately sent him an email asking what kind of beer he wanted me to buy him. I am sure many of you are familiar with this command, but for those that aren't, it is the 'System File Checker'. It checks the integrity of your system files, and repairs anything that is either corrupted or not present. So I want to thank the members of AO for all of the suggestions I received, and also present this fix as a possible solution to other's problems. Sorry if I offended anyone by dragging out a 2 week old thread. My judgment might be a little off. :drink:
February 12th, 2008, 04:41 AM
CybertecOne

Does anyone else find it odd that the SFC fixed the problem even though the files that would have been 'corrupted' had already been repaired through the manual commands already tried?

Eg; Reset TCP/IP Stack, host file etc.

I am curious to know what files (probably dll/sys files) would have been replaced with the originals that were not checked by all the previous work. Perhaps something was missed ?

CTO
February 12th, 2008, 09:12 AM
Cider

Well I just opened up command prompt and did the sfc /scannow.

It found errors but I didnt have any problems.

Thanks for the tip

:)
February 13th, 2008, 02:56 AM
CybertecOne

SFC will always find errors.

All it does is compare system files with the original files (The ones installed from disc or perhaps changed in a Windows Update). Any program that gets installed that changes system files, and even drivers, will cause SFC to find errors as the original file has been modified.

This causes a problem as when SFC replaced the modified file with the original it can cause the driver/hardware and programs to stop working as they should. However i have never seen this happen - But the theory works.

Note: The only time i have used SFC is when it was utterly nessecary and hence it resolved a bigger issue than being worried about a driver or program to stop working.

Cheers, CTO
February 13th, 2008, 07:55 AM
IKnowNot

Quote:

Sorry if I offended anyone by dragging out a 2 week old thread. My judgment might be a little off.

Pffffffffffft ... We want to know what happened! Feedback is always good!

Quote:

Does anyone else find it odd that the SFC fixed the problem even though the files that would have been 'corrupted' had already been repaired through the manual commands already tried?

Indeed!

:drink:

edit: CybertecOne, IBID on using SFC, if then!
February 14th, 2008, 01:51 AM
CybertecOne

Quote:

Originally Posted by IKnowNot

edit: CybertecOne, IBID on using SFC, if then!

What? lol.

[edit] Oohhhh.... Yea, it really is last resort only. [/edit]