|
|
|
I recently purchased a new Windows 8 PC and since then have been experiencing continuous connectivity issues.(never had them with Windows 7)
I have BT Infinity on a wired connection with Windows 8. The modem and home hub are left on 24/7. Everytime I boot/restart my machine the network icon shows that I am connected and have internet access but no pages will load (page cannot displayed).
When I run a diagnostic the results come back with either 'Gateway is not available' or 'no DNS server'.
The only way I can get my connection back is to unplug the modem or power down the hub and then restart them. This connectivity only lasts until the next time I shutdown or restart the PC. Then I have to go through the whole process again.
Never had this issue with Windows 7.
Just to add, wireless connections to my other devices work perfect.
Any advise greatly appreciated.
|
|
|
Check the DNS settings in both the router and the PC. Best to have them in only 1 place, prefer the router, so they don't get confused,
Try a public DNS like OpenDNS, Google or Norton.
Is the router giving out DHCP IPs or does the PC fix its own?
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
|
Thanks for the quick reply.
Please excuse my lack of knowledge but could you expand on your suggestions.
DHCP is enabled on the hub and the PC.
Hub IP Gateway Address: 192.168.1.254
Hub DHCP Network Range: 192.168.1.64 - 192.168.1.253 (Default)
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
DHCP is enabled on the hub and the PC. I'm unsure what DHCP enabled on PC means.
Does the PC's Ethernet Adapter's TCP/IP Properties show Obtain IP addy Auto & Obtain DNS addy Auto?
Do ipconfig /all in a Command Window and post with your MAC addys & names asterisked out.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
|
Windows IP Configuration
Host Name . . . . . . . . . . . . : ****
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : **********
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
Physical Address. . . . . . . . . : **********
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.74(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 28 February 2013 18:18:57
Lease Expires . . . . . . . . . . : 01 March 2013 18:18:53
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{****************}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : *******************
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : ******************
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : ***************************(Preferred)
Link-local IPv6 Address . . . . . : ***************************(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : **********
DHCPv6 Client DUID. . . . . . . . : *******************************
NetBIOS over Tcpip. . . . . . . . : Disabled
|
|
|
Looks good! Confirms router is giving out IP & DNS.
Could it be anything to do with short, 1 day, lease? Mine go on to 2038 = Forever.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
|
I wondered at first whether it was the 1 day lease but that period would have been the same when I was running Windows 7 and Vista with no issues. Also my wireless devices have no issues with getting an IP,etc.
I'm pretty sure it is a Windows 8/adapter issue.
|
|
|
|
Might need an adapter driver update for windows 8
|
|
|
I just registered after many moons of lurking as I may have a solution!
I have the same Intel NIC and there is a known issue with this device and Windows 8.
Basically, it can suddenly be detected as a different model (82579LM) and stop loading the driver, thus rendering the connection useless...
There is, thankfully, a firmware fix to correct this issue:
Intel download page with info
It's very straightforward: just follow the relevant instructions, reboot as requested and I think you'll find the problem is resolved.
Hope that helps!
Regards
|
|
|
|
Thanks for the advise.
Fingers crossed, installed the latest driver from Intel and it connected from a boot up with no problems.
|
|
|
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.
Zen 8000 Pro
|
|
|
|
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.
|
|
|
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?
|
|
|
|
A further update.
Same as usual today. Turned on the PC, network icon showed I was connected but no pages would load.
Ran diagnostics on the connection and error came back 'Your computer appears to be correctly configured but the device or resource (DNS Server) is not responding'.
As previously, the only way I could a complete the connection was to reboot the hub.
|
|
|
|
That sounds more like a DNS server issue.
If your ISP is no help, you could try to change the DNS server addresses in the hub/router config to the Google (8.8.8.8 and 8.8.4.4) or OpenDNS (208.67.222.222 and 208.67.220.220).
Regards
|
|
|
That sounds more like a DNS server issue.
If your ISP is no help, you could try to change the DNS server addresses in the hub/router config to the Google (8.8.8.8 and 8.8.4.4) or OpenDNS (208.67.222.222 and 208.67.220.220).
Regards
And if this does not work then try those same setting for DNS in windows, so that the router is taken out of the equation.
If this works then try and borrow a different router and see if that cures the problem.
Edited by philippercival (Fri 08-Mar-13 00:23:51)
|
|
|
|
Hi,
Apologies for the delay in updating this but I changed some settings a couple of weeks ago and wanted to make sure the problem was resolved before replying.
I installed the latest Intel drivers which gives more settings options in device manager than default drivers. I disabled some power saving settings within the options and so far the issue has not returned.
|
Pages in this thread: 
Print Thread
deleted
