"CL_ParsePacketEntities" and other "CL_Parse.

[imported_da80m8]

I've got a small 8-player server up on my cable connection at home (256k upstream). My problem is that when people connect, within a minute or so they get disconnected and are greeted with a "CL_ParsePacketEntities" error or sometimes a "CL_PareseGamestate: error bad command byte". I've been able to duplicate the error by connecting to my server from work (very stealthily, I might add :) and then hopping on the mg42 on the brecourt map and firing it non-stop. Within 15 seconds or so I get booted with the ParsePacketEntities error.

My server is a P-III 866, 512 RAM behind a Linksys router with ports 28960-28961 UDP forwarded to the server's IP. I installed CoD to its default path, C:\Program Files\Call of Duty. Activision support and the IW Nation forums have been of no help thus far. This is driving me nuts. Any ideas? Thanks.

da80m8

[imported_da80m8]

On a hunch I disconnected my old Linksys router and picked up a D-Link DI-604. I had myself and five friends playing CoD tdm for 2+ hours last night without a single interruption. It was quite sweet.

I'm pretty certain my Linksys is fine, I just probably would have only needed to release and renew its public IP from my ISP (Comcast). The public IP I've had for the last couple of years (I've never had reason to release/renew before) was 12.254.x.x. When I hooked up the new router, I was surprised to see that my new public IP was 24.8.x.x. I believe the 12.254 address belonged to AT&T's network before Comcast bought them out. Comcast must be using the 24.8 network. I'm guessing the problems I was experiencing may have been caused by latency due to routing between the two networks. Anyway, I'll test that theory this weekend by hooking up my Linksys again and renewing its public IP. I'll report my findings. Hopefully this might help someone having the same issue (although since I'm the only reply so far, I must be the only one :)

da80m8