Difficult Networking Problem..Possible broken port

sid

sid

sid

Soldato
Joined
9 Feb 2003
Posts
5,178
Location
London
Hello , I am having issues with Nforce Networking port on a Asus p5ne-sli mobo.

This problem doesn't appear to be OS specific as I have tried linux/windows variants. I have also loaded bios defaults

The port is unable to obtain an IP address via dhcp?? Clearly this would point to a configuration problem, but it has happened with w7 and freenas and other live usb discs which I have tried.

I have tried different network cables and changed ports on network switch.
In windows 7, it says the network is connected. Green lights are flashing on network ports on mobo and also at router end. The ip it obtains is in the 169.xx.x.xx range not 192.168.xx.xx range
Freenas sets ip to 0.0.0.0

router is VM superhub with dhcp server enabled. A multitude of other devices don't have any issues just this motherboard.

I should point out that I was trying to setup freenas and it worked only once, after a restart, this computer has not been able to get a network ip. Manual settings do not work either..

It could just be broken but I appreciate any sensible solutions
 
Try a different cable and try a different port on your switch or router. I'd also try it on another network if you can (a friend's house maybe). Are there any BIOS settings to do with how the interface works? Have you tried restarting the Superhub?
 
Do the lights on the connector show it's getting a link at all?

As shad says try it with a different cable and possibly on a different port on the switch, or connected to an old router.

After a lot of "fun" with dodgy cables and the odd faulty NIC I tend to keep some spare cables, and an old router for testing in such situations (I also have a cheap cable tester to help if the cabling is fixed).
 
As per OP , I have tried different cables and ports on the routers/switches.

I don't have a separate router to test but the dhcp server is fine for all other devices.

I think I will order another NIC to test I guess.

I dont think this is a driver problem as it happens in different OS'es
 
Check the router first. The "VM superhub" is an obvious weak link.
Just because other devices seem to work doesn't rule it out. I seriously doubt it's the most reliable router going by all the bad things written on here about VM.
 
PanMaster said:
Check the router first. The "VM superhub" is an obvious weak link.
Just because other devices seem to work doesn't rule it out. I seriously doubt it's the most reliable router going by all the bad things written on here about VM.
Click to expand...

What exactly should I check?
I have done the obvious and reset it
 
Disable it in the BIOS, reboot.
Shutdown Windows
Re-enable in the BIOS.
-Check if there are options for setting the MAC address, some boards let you change it. In case there's something odd going on there.
Disable any extra 'features' it may show for ethernet in the BIOS.

If it's still not working and you've tried other cables/ports/OS's, then I'd just disable it for ever and buy yourself a PCI-E Intel Gigabit card. They're the dog's danglies

EXPI9301CTBLK
 
This turned out to be the network port in the end.

I wonder how it is possible to damage it? Also with regards to the mac address suggestion, is it possible to for the port to loose if the motherboard battery dies?

Cheers
 
They can just 'fail' sometimes, only seen about 3 or 4 ever fail. (from thousands of machines)

Can also be taken out by lightning and the most probable cause, someone tripping on a cable connected to the port.
 
You must log in or register to reply here.
Back
Top Bottom