Networking Problems (Unidentified Network)

[al4nw31]

Tried taking out the 660ti, nothing changed. I'm not sure if I should RMA this mobo or what... Is there a hardware diagnostic?

 

[al4nw31]

Oh yeah this problem was also occurring on a fresh format, so I'm not sure what's happening.

 

[chev65]

You might try clearing the cmos on the board and setting to defaults.

 

[al4nw31]

Alright, updated BIOS, re-installed drivers (updated), and cleared CMOS. Let's see if the internet dies now.
I'll keep you updated. It's working for now.

 

[chev65]

Alright, updated BIOS, re-installed drivers (updated), and cleared CMOS. Let's see if the internet dies now.
I'll keep you updated. It's working for now.

I am presently at the edge of my seat.

 

[al4nw31]

Well, it's still intermittent.
I'm absolutely stumped now.
Are there any diagnostics that come to mind?
I believe this may be an issue with Windows 8...

 

[chev65]

I'm sure you have tried this but have you reinstalled the Op system yet, http://www.eightforums.com/tutorials/2299-clean-install-windows-8-a.html

Trying a direct connection to the modem might be an option.

 

[al4nw31]

I'm sure you have tried this but have you reinstalled the Op system yet, clean install?

Unfortunately, yes I have.
This is such an unbelievably obscure problem.

 

[fafhrd]

When your connection is working your IPv4 address is 192.168.1.6, but this sometimes gets lost and Windows gives you an address of 169.254.171.129.

Try giving yourself a fixed IP address, say 192.168.1.10. Just perhaps, there is another Machine claiming 192.168.1.6, and kicking you off, leaving your system looking for an IP address, which Windows supplies - but an address that will not talk to your router. I imagine that there are some malware exploits that can do this, so run Malwarebytes to see if there is a security problem.

How to do this?

Control Panel, Network and Sharing Center, Change Adapter Settings, Ethernet, rightclick Properties, Internet Protocol Version 4 (TCP/IPv4), Properties, General tab, Use The Following IP Address, and enter 192.168.1.10
In the Subnet mask, 255.255.255.0, and in the Default gateway 192.168.1.1 for your router's address.
then OK and close down the properties dialogs and then reboot, and see how you fare.

 

[chev65]

I was thinking trying a direct connection to the modem just to cut the router out of the picture but a static IP might work who knows.

 

[al4nw31]

When your connection is working your IPv4 address is 192.168.1.6, but this sometimes gets lost and Windows gives you an address of 169.254.171.129.

Try giving yourself a fixed IP address, say 192.168.1.10. Just perhaps, there is another Machine claiming 192.168.1.6, and kicking you off, leaving your system looking for an IP address, which Windows supplies - but an address that will not talk to your router. I imagine that there are some malware exploits that can do this, so run Malwarebytes to see if there is a security problem.

How to do this?

Control Panel, Network and Sharing Center, Change Adapter Settings, Ethernet, rightclick Properties, Internet Protocol Version 4 (TCP/IPv4), Properties, General tab, Use The Following IP Address, and enter 192.168.1.10
In the Subnet mask, 255.255.255.0, and in the Default gateway 192.168.1.1 for your router's address.
then OK and close down the properties dialogs and then reboot, and see how you fare.

The problem is that I reformatted, and it had this problem.
When I set a static address I only get network access, not Internet access.
Trying modem now.
When I look at ethernet status says no network access however.

 

[al4nw31]

Yeah, and static IP doesn't work.
It will never give me access to the internet for some reason.

 

[chev65]

Yeah, and static IP doesn't work.
It will never give me access to the internet for some reason.

It sounds like TCP/IP or winsock is messed up from what you are saying.

Try running the following two commands "in bold", type them into an elevated command prompt one at a time, hit enter after each one then reboot your machine.

netsh winsock reset catalog (reset winsock entries)

netsh int ip reset reset.log hit (reset TCP/IP stack)

 

[fafhrd]

al4nw31 - When you set a static IP address, what does ipconfig /all show?

Do it this way, please:

Control Panel, Network and Sharing Center, Change Adapter Settings, Ethernet, rightclick Properties, Internet Protocol Version 4 (TCP/IPv4), Properties, General tab, Use The Following IP Address, and enter 192.168.1.10
In the Subnet mask, 255.255.255.0, and in the Default gateway 192.168.1.1 for your router's address.
then OK and close down the properties dialogs and then reboot.

 

[al4nw31]

al4nw31 - When you set a static IP address, what does ipconfig /all show?

Do it this way, please:

Control Panel, Network and Sharing Center, Change Adapter Settings, Ethernet, rightclick Properties, Internet Protocol Version 4 (TCP/IPv4), Properties, General tab, Use The Following IP Address, and enter 192.168.1.10
In the Subnet mask, 255.255.255.0, and in the Default gateway 192.168.1.1 for your router's address.
then OK and close down the properties dialogs and then reboot.

I'm getting a 169.xxx address after setting static addresses. Same with getting weird dns servers. If you need the entire ipconfig tell me and I'll post it when the Internet is working.

 

[al4nw31]

Yeah, and static IP doesn't work.
It will never give me access to the internet for some reason.

It sounds like TCP/IP or winsock is messed up from what you are saying.

Try running the following two commands "in bold", type them into an elevated command prompt one at a time, hit enter after each one then reboot your machine.

netsh winsock reset catalog (reset winsock entries)

netsh int ip reset reset.log hit (reset TCP/IP stack)

Tried this before, hoped it would do something but it didn't fix the problem .
Tried it again and same results .

 

[fafhrd]

If you are setting static addresses in the way I instructed and still getting a 169.x.x.x address, it could be a good old hardware conflict, but you uninstalled the 660Ti and used the onboard graphics with no improvement.

It's a Sherlock Holmes problem - eliminating the impossible. If you had the problem before, then the Hard disk is the only remaining common factor. However, coincidences happen too.

I am assuming that you completely wiped the Caviar Green before installing Windows 8 on it (diskpart /clean) to eliminate any remnants of what might have been causing the problem before? I know you said you reformatted, but /clean removes all partition info too. Can be done from the Windows 8 Installation DVD setup WINPE, shift+F10 to get to command prompt after you set language and keyboard options.

Can you try a different hard disk? Can you try your disk on your Dad's system?

Have you tried a different network adapter, instead of the onboard Atheros?

You have already considered that the mobo may be faulty.

Finally the PSU may not be delivering the correct voltages under load. Recheck all connectors are seated properly (including CPU and memory, disks and PCI expansion slots, usb and other case connectors.

One more thing - try a linux live CD to see if that manages to run the network OK. Or a Windows to Go setup from a Windows 8 Enterprise evaluation, perhaps.

 

[al4nw31]

If you are setting static addresses in the way I instructed and still getting a 169.x.x.x address, it could be a good old hardware conflict, but you uninstalled the 660Ti and used the onboard graphics with no improvement.

It's a Sherlock Holmes problem - eliminating the impossible. If you had the problem before, then the Hard disk is the only remaining common factor. However, coincidences happen too.

I am assuming that you completely wiped the Caviar Green before installing Windows 8 on it (diskpart /clean) to eliminate any remnants of what might have been causing the problem before? I know you said you reformatted, but /clean removes all partition info too. Can be done from the Windows 8 Installation DVD setup WINPE, shift+F10 to get to command prompt after you set language and keyboard options.

Can you try a different hard disk? Can you try your disk on your Dad's system?

Have you tried a different network adapter, instead of the onboard Atheros?

You have already considered that the mobo may be faulty.

Finally the PSU may not be delivering the correct voltages under load. Recheck all connectors are seated properly (including CPU and memory, disks and PCI expansion slots, usb and other case connectors.

One more thing - try a linux live CD to see if that manages to run the network OK. Or a Windows to Go setup from a Windows 8 Enterprise evaluation, perhaps.

So I'm almost definitely sure it isn't the harddrive, because although I did in fact have 2 different harddrives with different OSes on my other build. I bought the green because the others were failing and clicking so I threw them away. I did have the issue on those harddrives after upgrading into windows 8. I will try the Linux live cd in a bit.
Oh and by the way, how come when I install a new harddrive and try to boot into it with a os installed on it, it always fails. I have to install an os with that mobo in and stuff like that before it will work? I'm saying SATA connection not USB.

 

[al4nw31]

Just tried Ubuntu and it just said no network connections... I don't know if it happened to be a problem with drivers though.

 

[chev65]

Just tried Ubuntu and it just said no network connections... I don't know if it happened to be a problem with drivers though.

I'd have to point my finger outside the box at this point>router or modem problem. Try different hardware.