B
bhin293
I have a Windows 10 Pro desktop with an Intel Pro/1000 server adapter and Comcast network service.
I'm using DHCP to get my ipv6 addresses. ipv6 comes up after booting and is working. I verified that using test-ipv6.com.
After almost exactly 4 minutes, it goes down - I get a "No Internet Access" status and my ipv6 default gateway is gone - no address. I can disable the adapter, reset ipv6 using the netsh command, enable the adapter and it will connect, but fail again after 4 minutes. There are no messages in event viewer, and I've tried tracing using built-in netsh tracing profiles. There are no telltale error messages related to any network problem. Kind of strange it happens almost exactly at 4 minutes every time.
There are some ipv6 addresses still there after the failure:
ipv6 address is there and valid
temp ivp6 address is there
Link-local ipv6 is there
ipv6 DNS servers are there
I have another desktop, and three laptops (all have windows 10 home) none of which have this problem.
I have managed to get it back working after a failure if I manually add a default gateway using netsh commands (shouldn't have to do that).
A funny thing I discovered during troubleshooting, when the status says that ipv6 is down, I can ping the ipv6 default gateway address. However, the responses are intermittent and there is a definite pattern. If I increase the number of transmitted packets to 40 or more, I get 8 succeeded, 8 timed out, then 8 succeeded, then 8 timed out, etc. until the requested number of packets are sent. Not sure what if anything that means. Just interesting symptom, I guess
Here is what I've tried already:
tried 3 different nic's
onboard Realtek PCIe Gbe controller (motherboard nic)
TP-Link Gigabit PCIe network adapter
Intel Pro/1000 PT server adapter (also PCIe)
Tried netsh int ipv6 reset commands
and tried putting in a startup script so it executes every boot
Tried static protocol settings
still fails, and the settings magically get set back to DHCP (!??) after failure
Tried deleting adapter from devices and reinstalling
Tried DisabledComponents registry entry (set to 0).
If you get to this point, thanks for reading it this far.
I need some help. Can anyone figure out why this is happening?
Continue reading...
I'm using DHCP to get my ipv6 addresses. ipv6 comes up after booting and is working. I verified that using test-ipv6.com.
After almost exactly 4 minutes, it goes down - I get a "No Internet Access" status and my ipv6 default gateway is gone - no address. I can disable the adapter, reset ipv6 using the netsh command, enable the adapter and it will connect, but fail again after 4 minutes. There are no messages in event viewer, and I've tried tracing using built-in netsh tracing profiles. There are no telltale error messages related to any network problem. Kind of strange it happens almost exactly at 4 minutes every time.
There are some ipv6 addresses still there after the failure:
ipv6 address is there and valid
temp ivp6 address is there
Link-local ipv6 is there
ipv6 DNS servers are there
I have another desktop, and three laptops (all have windows 10 home) none of which have this problem.
I have managed to get it back working after a failure if I manually add a default gateway using netsh commands (shouldn't have to do that).
A funny thing I discovered during troubleshooting, when the status says that ipv6 is down, I can ping the ipv6 default gateway address. However, the responses are intermittent and there is a definite pattern. If I increase the number of transmitted packets to 40 or more, I get 8 succeeded, 8 timed out, then 8 succeeded, then 8 timed out, etc. until the requested number of packets are sent. Not sure what if anything that means. Just interesting symptom, I guess
Here is what I've tried already:
tried 3 different nic's
onboard Realtek PCIe Gbe controller (motherboard nic)
TP-Link Gigabit PCIe network adapter
Intel Pro/1000 PT server adapter (also PCIe)
Tried netsh int ipv6 reset commands
and tried putting in a startup script so it executes every boot
Tried static protocol settings
still fails, and the settings magically get set back to DHCP (!??) after failure
Tried deleting adapter from devices and reinstalling
Tried DisabledComponents registry entry (set to 0).
If you get to this point, thanks for reading it this far.
I need some help. Can anyone figure out why this is happening?
Continue reading...