Strange Win7 Networking Problem - No Internet but no Indications (wired ethernet)

[geobrick]

I agree the problem seems to go in circles. The articles I've read about that error never discuss a loss of connectivity but often mention BSODs which have not been an issue. The problem occurred yesterday as well and the error above was not listed but there was one other MS security error listed as well as 2 other seemingly unrelated errors (I'm not getting any critical errors). I'll list a summary of the 3 errors below to save space and if you want to see the detail from any of them, let me know.

With regard to IPv6, I've also read several posts about disabling it if the ISP is not using it (and as far as I know, FIOS is not using it - at least not with my current router). Verizon is pushing customers to upgrade to a faster router but I can't see why something faster that the 35Mb/s up and downstream I currently have would ever be noticeable. I haven't tried disabling IPv6 yet. I just assumed MS was handling the lack of IPv6 through those "Teredo" port forwarding items that get set up in the router (most have been set up by the Silicon Dust Cable Tuner on the network). I've been using the setup with the tuner and media server PC for a year before this problem started so I can't imagine that it is the problem.

The 3 errors listed the last time I noticed the loss of connectivity (at about 6:45 PM last evening).
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 6/6/2015 11:13:30 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Media-Server
Description:
The server {AAC1009F-AB33-48F9-9A21-7F5B88426A2E} did not register with DCOM within the required timeout.
************************************************************
Log Name: System
Source: Microsoft Antimalware
Date: 6/9/2015 4:16:08 AM
Event ID: 2001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Media-Server
Description:
Microsoft Antimalware has encountered an error trying to update signatures.
New Signature Version:
Previous Signature Version: 1.199.2034.0
Update Source: Microsoft Update Server
Update Stage: Download
Source Path: http://www.microsoft.com
Signature Type: AntiVirus
Update Type: Full
User: NT AUTHORITY\SYSTEM
Current Engine Version:
Previous Engine Version: 1.1.11701.0
Error code: 0x80240022
Error description: The program can't check for definition updates.
*********************************************************************
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 6/9/2015 10:07:00 PM
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: Media-Server
Description:
Session "Circular Kernel Context Logger" failed to start with the following error: 0xC0000035

 

[Ralston18]

I believe those errors are a result of not being able to connect. The 0x80240022 error represents the inability to download an update.

The GUID "AAC... etc." actually seems to be related to an application (?). I copied and pasted the entire sequence between the brackets into regedit and got a find. Again I think the error is connectivity related. Some "app1" (as it appeared on my system) could not find what it was looking for and timed out. Did not attempt to delve further than that.

One site claimed that the 10010 was a failing hard drive. Seemed to be too pat of an answer. Plus I think you would be seeing many more errors and consequences if Media-Server's hard drive was in doubt.

As for the last error "Kernel" I only looked at "Circular" and chuckled at the wording. Just feel that that would really lead me off track....

IPv6: I have Comcast and IPv6. Not sure where Verizon is with IPv6 in my area. We usually receive a mail flyer every week trying to get us to change plus an almost monthly "representative" at the door. Most likely they would be touting IPv6 just for the marketing effect.

Here is a useful link: http://test-ipv6.com/

There are other similar sites as well.

There is a relationship between Homegroup and IPv6. Homegroup uses IPv6. And the router must as well.

E.g.:

http://www.zdnet.com/article/use-ipv6-in-windows-7-today/

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/tcpipv6-and-homegroups-tcpipv6-is-active-but/0a1a90e5-cba9-41af-a781-c4cf41244597

My understanding would be that every Homegroup device needs to have IPv6 enabled and Peer Network Grouping plus PNRP Machine Name Publication Services running. Some articles cite registry edits to get it all working. Teredo would be needed for any devices communicating between IPv4 and IPv6. If some Homegroup function cannot get translated then communications flounder.

Unfortunately, in a way, I am falling back on configuration settings be they errors of omission or commision. Small typo in a submask maybe. Or just the result of some update or maybe a driver change. Microsoft seems to be tweaking things behind the scenes (IMHO) prepping for Windows 10. Should not be doing any harm but some of the current updates may be laying the foundation for the expected July 29th release date. Example: Have you noted the "Reserve your Windows 10" icon on any systems?

It would be easier to work on the problem directly versus from afar as we are doing. Not a fan of posting links but that makes more sense sometimes as a matter of convenience.

Here is one such link:

http://www.skycrystal.com.au/blog/2015/3/13/ipv6-may-be-the-future-but-right-now-it-can-be-painful

You are a Windows 7 environment I know. However, the article is current, seems relevant, and may just trigger some thought or idea that will help.

Please continue watching the logs - still hoping for some event that fits it all together. Thanks. And whew.....! 🙂.

 

[geobrick]

I just want to wrap this up for any others who are having a similar problem. I never was able to resolve it. I ending up reinstalling windows and It's been working well for about 3 weeks now. My issue was probably caused by the motherboard swap I made when the original motherboard died. Everything seemed to work fine initially but the PC would lose internet access after a few days. The fresh install of windows seems to have corrected the problem. This proves it wasn't a hardware issue.