Every 7 minutes this error is logged in event viewer.
I have wired connection disabled, wireless connection works fine. It actually works much better than it did with XP Pro. Lan transfers are much faster.
What's causing this and how to stop it?
It seems your system is trying to get a ipv6 dhcp response from somewhere..
I would suggest to disable ipv6 on your network adapter and see if the error continues.
take a look at this post of mine for instructions.
https://www.sevenforums.com/network-i...html#post26767
I can disable that protocol for the adapter, but I was mostly just trying to learn. On this clean install to new hard drive of Windows 7, only added software AVGFree 8, what would be trying to use it and for what purpose? Just curious.
Well, since there are several protocols supported and active for your adapter, they are trying to get their job done. So, for those you don't need, you can disable them so their job isn't bugging you anymore.
We're probably having the same errors in our configuration, provided we don't have an IPv6 DHCP server active on our network, so it's a logical thing to happen. By disabling the protocols / services you don't need , you disable future system attempts from trying to use them.
sheila it is trying to grab an ipv6 address from router/modem via dhcp... since your router/modem does not support ipv6 (i'm guessing), this is why the error pops up...
coincidently i just pulled this up 5 min ago.... i have the same thing in log as well, no worry.
If you are on a router and have UPNP enabled, and can also see which program is using UPNP and its port, you will see that Microsoft uses it with Toredo (ipv6) udp ports 58035 & 50604
also Microsoft media foundation (iexplorer.exe) udp ports 56368 & 56369
I had the same problem on my 780i, errors from that one every 7 minutes on the nose. Had to turn that off for sure. I wonder if updating the Router firmware would fix that sort of error message?
Now all I get is the Diagnoses scheduled error which I'am not too sure what that means.
I had the same problem. Removing IPv6 from the adapter sorted it. Microsoft are aware of this, so let's hope a permanent fix is forthcoming..
Quote