This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Basically, my partner noticed it doing this, but i was unable to reproduce this on my Linux PC or my Macbook, so i brushed it off as an odd windows issue or possibly a wifi one. However, i've been able to observe the same behavour on another windows PC connected by ethernet to the switch, it also has doen this for a friends laptop, so at this point I am forced to believe there is an issue on samba (nas) and not the clients.
Things I have already tried:
Rebooting the nas
removing one of the 2 ethernet cables (which are bonded) rebooting the netgear switch
Sorry to answer my own question on this one.. Im not 100% why, but i deleted the bond interface, rebooted the switch, and it still did it.
I then re-created the bond interface and used XOR (Layer 2) this time around (i was using adaptive load balancing last time) and it has stopped behaving oddly.
Sorry to answer my own question on this one.. Im not 100% why, but i deleted the bond interface, rebooted the switch, and it still did it.
I then re-created the bond interface and used XOR (Layer 2) this time around (i was using adaptive load balancing last time) and it has stopped behaving oddly.
I then re-created the bond interface and used XOR (Layer 2) this time around (i was using adaptive load balancing last time) and it has stopped behaving oddly.
An RN100 series can't keep up with a single gigabit connection, so I wouldn't spend much time on bonding.
Even with a faster NAS, bonding (like jumbo frames) often isn't worth the bother. It only really helps if you have multiple simultaneous clients.
So if this also misbehaves, you might try just turning it off, and see if there is any perceivable performance dropoff.
I know this reply is late, but i've since spent some time with the RN104 without a bonded interface, I installed soft ether on it since, and needed one of the itnerfaces to use as the bridged port (With no tcp/ip settings) so that accessing the nas was possible without complicated routing, so it's since been running off a single port without any flapping or odd issues. I've also since done a complete factory reset, so any issues i was having are basically resolved at this point.
