Hi Rever

Did you see my reply above?

The driver update may help but I doubt it'll be permanent; I know because I had exactly the same issue as you.
The only permanent fix was the firmware update I referred to.

Regards

Edited by deleted (Fri 01-Mar-13 20:25:46)

Unfortunately I still have the problem.

Tried the firmware fix.

Still have the issue on every reboot or cold start. The diagnostics either says 'The default gateway is unavailable' or 'Ethernet doesn't have a valid IP configuration'.

Only way I can get it back is to power down the home hub (or modem) and restart them.

Sorry to hear that.

I can only recommend contactng your ISP for advice. Perhaps a config change in the modem/router is required for Win8 compatibility; ironically, possibly a firmware upgrade!

Good Luck!

I do not have windows 8, but q quick google suggests this may be possible.

Having started the computer,(with failed interent access) get the CMD prompt and type

ipconfig/release

ipconfig/renew

Would be interested to hear the result.

Seems to be hit and miss. Sometimes it worked and sometimes didn't.

Is IPV6 enabled for your network connection? If it is, and you don't actually use IPV6 you would be well advised to disable it.

May well fix the issue, but Windows will not amused if you disable the IPv6 stack. There are lots of built in services etc which have an assumption it will work. There is a Microsoft article to this effect related to Windows Vista/7 iirc - Windows 8 will probably have even more dependency.

I do not believe that, in the simple case of a standalone PC connected to an IPV4 router there will be any ill consequences of disabling IPV6; this is not an enterprise network. I guess the only way to know is to try it and see. If disabling IPV6 solves the problem, but creates other peculiarities, then the OP can determine which is most important to him.

I've never experienced any problems running Windows 7 with IPV6 disabled (though it has solved problems) on a small network of Windows, OS X, and Linux machines with local logons.

In reference to technet.microsoft.com/en-us/network/cc987595.aspx:

Q. What are Microsoft's recommendations about disabling IPv6?

A.

It is unfortunate that some organizations disable IPv6 on their computers running Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.

From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows 7, Windows Vista, Windows Server 2008 R2, or Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6�such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail�could be.

Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

It disables Home Group? How will I survive?