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
Printable View
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
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:
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:Quote:
sfc /scannow
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
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
:)
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
Pffffffffffft ... We want to know what happened! Feedback is always good!Quote:
Sorry if I offended anyone by dragging out a 2 week old thread. My judgment might be a little off.
Indeed!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?
:drink:
edit: CybertecOne, IBID on using SFC, if then!
What? lol.Quote:
Originally Posted by IKnowNot
[edit] Oohhhh.... Yea, it really is last resort only. [/edit]