I bought a new motherboard (Gigabyte GA-870A-UD3) two weeks ago. Everything was running fine until Tuesday morning when I woke up and couldn't get to my email. I noticed the icon in the taskbar saying it was disconnected from the network. First thing I tried was rebooting the router... no change. I decided to take a look at the system thinking maybe my IP reset or something strange (I use a static IP since I have SSH access and a web server). Everything was right, and even tried DHCP just to be sure... still nothing. I decided to restart the computer.
After restarting the computer I saw it (the icon in the taskbar) start to connect, then immediately disconnect, then connect, then immediately disconnect, and so on as shown below:
I thought I might have a bad cable, so I switched cables. Same problem. I was looking online and someone mentioned a bad router port, so I switched ports on the router. Same problem. I plugged the connection into both my laptops and it worked as expected.
I'm stumped. I have no idea what to try next. I have a feeling my ethernet is broken on the mobo... or am I missing something?
SYSTEM SPECS: Windows 7 Professional 64-bit Gigabyte GA-870A-UD3 motherboard AMD Phenom II X4 955 8GB DDR3-1333 MSI GeForce GTX 460 1GB
I have that same motherboard and the only thing that has worried me so far is I keep reading horror stories of the built in ethernet port dying quickly. I'm 3 weeks in with mine and so far no problems. The only solution is to just get a network card. Apparently the built in **** is faulty by nature I guess.
IP: Logged
10:15 PM
wikid_one Member
Posts: 2838 From: Ocean City, MD Registered: Dec 2003
Well, I was screwing around with the device settings and was able to get it to connect. Unfortunately I have to set it to 10Mb Half Duplex in order for it to connect. 10Mb Full duplex cause the problem shown above as well as 100Mb Full/Half Duplex and Gigabit.
At least I have access back on the computer, albeit horribly slow access.
I do have to say though, so far a kickass board. Overclocks easy and unlocked my proc's 2 extra cores in a breeze. I like it. You can't beat the price either.
IP: Logged
10:40 PM
Marvin McInnis Member
Posts: 11599 From: ~ Kansas City, USA Registered: Apr 2002
Well, I was screwing around with the device settings and was able to get it to connect. Unfortunately I have to set it to 10Mb Half Duplex in order for it to connect. 10Mb Full duplex cause the problem shown above as well as 100Mb Full/Half Duplex and Gigabit.
At least I have access back on the computer, albeit horribly slow access.
How fast is your internet connection? My cable modem only uses a 10Mb connection because the internet speed is less than that. I can only get higher connection speeds between PCs on my LAN.
What happens when you set it to Auto/Auto? Is Power management on the NIC enabled? If so, disable it.
Or, just pick up a Killer NIC and be done with it.
quote
Originally posted by N3M3S1S:
I keep reading horror stories of the built in ethernet port dying quickly.
quote
Originally posted by N3M3S1S:
Overclocks easy and unlocked my proc's 2 extra cores ...
quote
Originally posted by Marvin McInnis:
Do you think there might be a connection?
This could be an issue. I'd set everything back to factory default settings while troubleshooting to rule out any anomalies you might have caused with overclocking. That's assuming the OC'ing didn't damage anything. Even though it's unlikely, it's always a possibility when you run the hardware outside it's design parameters.
[This message has been edited by Formula88 (edited 03-10-2011).]
This could be an issue. I'd set everything back to factory default settings while troubleshooting to rule out any anomalies you might have caused with overclocking. That's assuming the OC'ing didn't damage anything. Even though it's unlikely, it's always a possibility when you run the hardware outside it's design parameters.
quote
Originally posted by Marvin McInnis:
Do you think there might be a connection?
It's the risk I take for cranking out a few extra "ponies" from my rig. I'm alright with the risk. My old setup (a 1.8ghz Core 2 Duo e6300) is overclocked at 3.2ghz and stayed that way for 3 years(and is now pulling Ubuntu box duty) without so much as a hiccup or failed overclock on startup. I'm alright with it.
Besides, I didn't say my ethernet port was blown. Not yet at least, knock on wood.
IP: Logged
01:06 AM
wikid_one Member
Posts: 2838 From: Ocean City, MD Registered: Dec 2003