Hi, sorry for the naff title

I recently upgraded to a 100mbit switch from a 10 mbit hub and the speeds are perfect, the only issue I have now is that I can no longer connect to my Q3 server on another box. When I connect, after a few minutes I am kicked with this error: cl_parsepacketentities

Now I did a little searching around and discovered that this is a NIC issue (which would make sense considering this started after I upgraded to a switch) and I really don't want to go back to 10mbit speeds

Has anyone else experienced this error or know a way of resolving the issue? Is it worth me trying the released drivers from via? The NIC is an onboard realtek 8100 with a VT8235 southbridge chip on the mobo.

I am presuming that this is an error with the client machine because nobody else is kicked from my server with this error.... but the ifconfig of the server looks squeaky clean. 800megs received and a gig n' a half transmitted with no packets dropped and no collisions.

However, the server machine is running an nforce (the bain of my life) and the the ifconfig looks lightly different for the server machine:

A gig n' a half received and 800 Megs transmitted... but on the received channel I'm seeing "errors:18" and "dropped:9"

I don't have a clue where to start... with the server or the client...

Any help is much appreciated

Sounds like you have it pinned as a client problem (since no one else is getting dropped). I've heard tons of bad experience with Realtek cards, and the one time I bought a Realtek against my better judgement (was an emergency and I couldn't wait for shipping) it died on me two weeks later.

I would recommend an Intel Pro/100 card (with the 8255[5|7|9] chipset) or a 3Com 3c905x.

I have always had realtek and they've never let me down... I may have been a little bit ahead of myself with my post

I calmed down a bit and thought about the possible causes. I tried switching transfer speeds, I tried changing the duplex mode... but the one thing I didn't even take into consideration (don't ask why because I really have no idea why) was the fact that I had just bought a new switch. Hmmmm, could it be this new switch causing all my problems? Let's see. Threw my old hub back in place and tada, problems have gone.

It's a turd switch anyway... Netgear. Why make a switch with LEDs when the whole bunch light up when one does? Seriously... I would never put out a product so bad with my name on it. Ah well... I get to take it back and hopefully get a D-Link one

Let's just hope that it's a switch issue and not a card issue.

Thanks