help me please with ethernet connection!!

[adamr]

the modem is the netgear DG632... with firmware 3.40

ok, so i have been using the modem/router connecting it via usb for some time, all is fine ... today i decided to connect via ethernet (marvell yukon) ... it worked great. went out came back, switched the pc back on, everything still great. Then decided i need food and when i switched the pc on the thing is always just "acquiring network" and then "limited or no connection" ... when i try and connect to net there is no connection. rebooted and the error still persists

funny enough if i overide the autosensing option and choose 10mbs full duplex it works again ... why cant i leave it on "autosense" or 100mbs full duplex??? with these options it never connects ... but initially it was ok

 

[stocksie]

Hi
It's worth updating your networkcard drivers - link for Win XP GigE Driver
http://network.free-driver-download...-GigE-Driver-7.14-Windows-XP-2003-Server.html

 

[koffiejunkie]

you don't need full duplex or 100mbit. Even with 10mbit running at half duplex, your network card will still cope with the theoretical 1mbit thet iBurst offers.

I have a 10mbit ISA card (Intel server nic though) in my firewall...

 

[adamr]

i am on the 4meg adsl .. i know the 10meg will be fine ... but why did the 100meg work and now it does not ... it just stopped working ... !?

btw i did update drivers ...

 

[koffiejunkie]

Oops sorry! Got my forums mixed up.

I have no idea why it stopped working. What I can tell you is the Marvel Yukon is about the worst network contrller I've ever come accross.

Two things to try:

1. If there is a bios update for your board (assuming the network is onboard), do it.

2. If there is a driver update, do it. Try the one from Marvel itself instead of your motherboard manufacturer (especially if it's an ASUS board).

 

[adamr]

yeah i hav the msi k8n neo 4 plat mobo. i updated the bios to the latest version, updated the drivers for the controller .... managed to get it working again by erasing all the info off the modem, powering the modem off and then trying the ethernet
and then after about 3 reboots of the machine it stopped wokring again ... i dunno ... its so weird ....

 

[bekdik]

Autosense sometimes gets its knickers in a knot and the port needs to be set manually.

If the netgear's ethernet can be manually set, set it to 100 dup and powercycle the pc.

You can try setting the pc to 100 dup and then power cycling the netgear. then run ipconfig /renew from a cmd prompt.