I keep loosing my shares whilst in mid transfer. Its says "there is a problem accessing X: Make sure you are connected to the network and try again"

 

I have attached my syslog. There is nothing on the router log.

 

Any ideas?

link_beat.txt

First try a different port in your switch - sometimes one can go bad - then try a different cable, and last I'd put in a new network card.  I'm partial to the Intel PRO1000's myself.

 

 

Of course if you have a box full of network cards and cables - do it all at once

I have tried changing the port no that didn't work. I will try changing out the cable.

 

Do different cables really make a difference?

 

The motherboard I have has the Realtek 8111E gigabit lan. I thought that this was fully compatable?

 

Is there a way to update the driver on the LAN?

I have tried changing the port no that didn't work. I will try changing out the cable.

 

Do different cables really make a difference?

 

The motherboard I have has the Realtek 8111E gigabit lan. I thought that this was fully compatable?

 

Is there a way to update the driver on the LAN?

Yes, cables do make a difference, sometimes in freaky weird ways. 

Also, there have been reports of people having problems with Realtek chipsets. Try an Intel one as they seem to be the most bullet proof.

Turn off autoneg.

 

ethtool -s eth0 autoneg off

so what does setting autoneg off do?

 

why would someone want it on, or would want it off?

Autoneg is a detection routine to identify what speed the NIC port should run at for any given NIC/cable and switch/hub port combination.

 

It is still fairly common to see ports flapping due to autoneg not being able to find a steady state. If you know you have a Gb NIC, cat 5e or cat 6 cable and Gb switch port, turn off autoneg (R8169 is prone to this bahaviour). If that doesnt work then also force the driver to use 1000Mb.

 

What is more annoying is that autoneg can work great for a week, a month or a year then decide to start playin up and nothing will fix it until you turn it off. Of course it could also indicate a bad cable, port or NIC but usually simply turning off autoneg works. This is a general network observation, not linux specific.