• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

A8N-SLI ethernet death?

N

NBomb

Junior Member
I've had this mobo for 4 months, GREAT, no problems, very happy, until this morning.

Some time after I went out, the connection died, and the PC would no longer connect to the network. When I checked it out, nothing I could do would make it re-connect to grab an IP, it would give me a DHCP error.

So I tried connecting to the marvell LAN, and it works fine. Any idea if the port itself is dead and I need to get this warranty fixed, or is there possibly some software problem?

I'm running the original drivers from back in january or so, haven't installed anything lately or whatnot, this is completely out of the blue.

Thanks!
 
If you're using the nVidia firewall, then it is probably blocking the DHCP renewal. One simple workaround would be to assign the nVidia an IP address manually so it never has to renew its DHCP lease.

Welcome to the Forums 🙂
 
Originally posted by: mechBgon
If you're using the nVidia firewall, then it is probably blocking the DHCP renewal. One simple workaround would be to assign the nVidia an IP address manually so it never has to renew its DHCP lease.

Welcome to the Forums 🙂
Click to expand...

Thanks! Well, as far as I know, I've never had the firewall on... unless it was installed by default. I'm using the stock ASUS nforce drivers rather than Nvidia ones, if that helps.
 
My guess is that it was installed by default, although a 4-month DHCP lease is rather unusual 😕 Try giving it a static IP address of 192.168.0.5 netmask 255.255.255.0, and manually enter your ISP's DNS servers' addresses. If it suddenly works again, well there ya go 🙂 That, or send your system to me for testing.*







*testing procedure may take 2-3 years
 
I had a similar problem -- it occured after updating to the latest nForce drivers, which happened to install the latest nVidia Firewall. I turned the firewall off (told it to use the Windows firewall instead) and my nVidia port started working again.

Good luck,

Carl
 
I had the same problem but worse - I would get a hard windows lockup with the port enabled in the BIOS. The Marvell port worked fine.

I had to RMA the board.
 
i recently had trouble with the nv port. i moved and when i plugged in the lan it would say i was connected but would not let me acess anything on the web, marvell port worked fine and my laptop as well. ended up unistalling the Network Acess Manager but had left the ethernet drivers on. after that i lost the firewall and still no go with the port. ended up uninstalling the ethernet drives and then when i loaded the chipset drivers this time, it installed the NAM and firewall and everthing. everything works fine now. i think it has something to do with renewing the address but i am not 100% confident with networking and everything that goes with it, but i do know that my trick did work. ( i am sure there is an easier way, hope someone can help you...and me!)
 
Originally posted by: carl
I had a similar problem -- it occured after updating to the latest nForce drivers, which happened to install the latest nVidia Firewall. I turned the firewall off (told it to use the Windows firewall instead) and my nVidia port started working again.

Good luck,

Carl
Click to expand...

As did I the firewall changed in the last update shut it off entirely, shame I kinda liked it.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top