Good day everyone

I recently installed suse 9.2 pro on my home desktop system running a VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet Adapter (Copied from ifup eth0).

I have noticed when I copy a file from one computer to another through samba the system stalls about 40Mb in.

I have also noted that my connection to the Internet host computer (192.168.0.1) is no longer available when I try to ping it. This lost connection happens every couple of minutes (especially when I try to download updates with YAST). To restart the card I type Ifdown Eth0 then ifup eth0 to restart the card, after which it works again.

The Internet Connection server is a Winblows XP system. I have given myself a static address 192.168.0.2 and set all other parameters to connect to the XP system no problem (for a few minutes anyway).

Basicly, everything is fine as long as I don't copy files or try to surf for more than a few minutes.

any ideas anyone? I am considering the possibility that my onboard network card is giving problems. If anyone has a link to a web page I will greatly appreciate it

Sincerely

Marc Arndt

I am using Linux Mandrake Community 10.1 and i have a problem about diconnecting to the ADSL router via Realtek
ethernet. when uploading file size will be high in the aMule, it is interesting but aMule server connection does not disconnect.(It is still downloading and uploading) but network connection is shown as disconnected. So it will not connect to the web sources. CONNECTION REFUSED. When i want to connect LAN again i apply your procedures and it will solved...

Also i was decided to install Suse 9.2 for my system to solve this problem. If you are right i will be very angry about that

i am using suse 9.2 and my onboard NIC is a gigabit, everyhting worked sweet untill i upgraded to this motherboard, i have tried so many different things to correct my network lock up problem, but it never occured to me untill today - i am going to use a standard 100mbps ehternet card plugged into my PCI slot, i'll see how that works, and let you know.

I also found this problem on another forum, seems like we're not alone:

arstechnica