IPv6 & Connection Issues

[d3moliti0n]

Hi, earlier on I turned my computer on having been out, and the ethernet connection didn't want to connect to the internet (limited connectivity), even though earlier in the day it was working fine.

I went into the network adapter settings, as I had to manually configure the adapter to run on the '192.168.0.2' IP a few months ago when for some reason (after Windows Updates I think), the 'Obtain an IP address automatically' option just stopped working and wouldn't connect to the internet anymore (and it still doesn't work now having tried it). Everything was running fine on the static '192.168.0.2' IP until today when the above issues occurred.

I changed the IP to 192.168.0.3 and the internet kicked in again and has been working fine all evening but I notice on the 'Local Area Connection Status' that IPv4 Connectivity is listed as 'Internet' and is connected, but IPv6 Connectivity is listed as 'No internet access', which I haven't actually noticed whether this has just happened today since changing the IP or it's always been like that.

For reference we are with Virgin Media and have a Superhub which is connected up to my PC via ethernet and have a laptop which connects via wireless.

My questions are:

1. Why did '192.168.0.2' just randomly stop connecting to the internet earlier on, considering it's been working fine for months and there has been no computer changes/updates.

2. Why did the 'Obtain an IP address automatically' option stop working months ago and never worked since?

3. Is the IPv6 Connectivity supposed to say 'No internet access', if it isn't, what is the problem? And if it is, would it have said this anyway, even when I was using the automatic IP and .0.2 IP?

Thanks

 

[aln]

My questions are:

1. Why did '192.168.0.2' just randomly stop connecting to the internet earlier on, considering it's been working fine for months and there has been no computer changes/updates.

Nobody can really answer that one for you. However, you may be able to garner some information from logs, either within your OS or the router. I wouldn't worry about it unless it's a reoccuring problem.

2. Why did the 'Obtain an IP address automatically' option stop working months ago and never worked since?

Did you disable the dhcp service on windows, or dhcp on the router by any chance? Have you configured your PC within the superhub in anyway?

3. Is the IPv6 Connectivity supposed to say 'No internet access', if it isn't, what is the problem? And if it is, would it have said this anyway, even when I was using the automatic IP and .0.2 IP?

Virgin doesn't support IPv6.

For the record, they look more like this:- fe80::225:22ff:feec:5119/64. The IPs you're refering to are IPv4 specific.

 

[kerrgreg]

My questions are:

1. Why did '192.168.0.2' just randomly stop connecting to the internet earlier on, considering it's been working fine for months and there has been no computer changes/updates.

DHCP lease was probs stollen by another device

2. Why did the 'Obtain an IP address automatically' option stop working months ago and never worked since?

Windows lost the lease as above while the system was on and it glitched restarting the services or pc may have resolved the issues. Random problem could have been anything really.

3. Is the IPv6 Connectivity supposed to say 'No internet access', if it isn't, what is the problem? And if it is, would it have said this anyway, even when I was using the automatic IP and .0.2 IP?

Thanks

Chances are your ISP is not giving you an IPV6 address few do its pretty much standard for it to display this most of the time, since most ISP's dont do IPV6 to the home yet.

 

[d3moliti0n]

Hi, thanks for the responses.

I have not disabled any DHCP setting anywhere at any point. The Superhub is connected to my computer and was working fine for several months (it was installed in September 2011) with the 'Obtain IP automatically' setting, then back in January this year the 'Obtain automatically' setting stopped working after I had installed some Windows Updates I think. I then had to manually configure it to use 192.168.0.2, which stopped working for me yesterday and now I'm using 192.168.0.3.

How would I fix this DHCP issue and get the 'Obtain IP automatically' setting up and running again? Is this possible? Thanks.

 

[PistolPete]

You manually assigned an IP address whilst your Superhub is assigning DHCP address..... ding ding ding, we have a winner.

Check your event logs and you'll find a few complaining about IP address conflicts for 192.168.0.2.

 

[kerrgreg]

You manually assigned an IP address whilst your Superhub is assigning DHCP address..... ding ding ding, we have a winner.

Check your event logs and you'll find a few complaining about IP address conflicts for 192.168.0.2.

+1 just tick back over to auto get IP and all should be well.