Switch causing Quake3 drop outs

[breakerfall]

Hi

Up until recently I have been running a small network consisting of 3 machines, all running at 10mbit through a small 5 port hub, connected to a LinkSys Befsr11 router and on one machine I run a public Quake3 server and connect over LAN with the other machine. This has been perfect for quite a while until I recently decided to upgrade to a 100mbit switch so I could transfer files faster.

The problem now is that when I connect to my own game server, as soon as someone else connect (traffic) or even if nobody connects, after a minute or two, I'm booted from Quake3 with an error message: usually along the lines of cl_parsepacketentities. After a small amount of research, one source stated it was a network issue but I don't see where I'm going wrong when everything worked with the hub.

I know the switch isn't the problem because I have tried 2 different switches, both 8 port. One Netgear and the other, the current one, a Dlink.

Both machines are running linux and are set for 100mbit Full duplex speeds. The server machine has an nforce2 onboard NIC and the client has a Realtek81xx onboard NIC. Diagnostics on both machines show now collisions and no errors.

If anyone has seen this kind of error message from Quake3 before and has any kind of fix I would really appreciate it.

Short of that, I would replace the NIC but I'm not sure which machine has the issue. I presume it's the client but I'm not 100% sure.

[fleed]

If you didn't replace the cabling, could that be it? If you transfer files simultaneously from/to different machines, do you notice any such problems?

[breakerfall]

I'm using CAT 5 cabling. There's no issues with anything else at all. I can transfer files just fine and ifconfig on both machines shows no collisions and no errors.