|
Looking at the logs the first failures are due to MS's ISATAP adapter failure. Both Teredo and ISATAP are mechanisms for IPv6 connectivity on IPv4-only networks, therefore possibly a network adapter issue.
If you can get it to restart try the following to disable the ISATAP adapter:
Open a cmd promptenter : netsh interface ipv6 isatap set state disabledSee if it makes a difference.
You can also do the same with the TOLEDO adapter with the cmd:
netsh interface ipv6 set teredo disabledAfter doing the above get a print of the log file again.
If it's not these they can be set back to enabled by the cmd:
netsh interface ipv6 set isatap enablednetsh interface ipv6 set teredo enabled
No promises, but you have to start somewhere, so let us know how you get on please. |
|