My NetGear DG814 has started to drop the external network connection when ET grabs the list of servers. This only started yesterday. Anyone else experiencing this?
Tried ET from another client machine and the same thing happens. Both machines are XP with all the latest Windows updates.
Any ideas?
Thanks.
Chris.
Having the same problem here. And its not just the server list, but you cant connect to any servers either. It happens even more frequently when playing the game on 2 different pcs of the lan. I have tried several supposed fixes I found on the Activision web forum with the net_port and client_port to the shortcut etc for each pc on the lan and have not found a single fix for this.
Activision/Splash Damage provide no support for the game behind a router so this answer seems to be hard to find. Only fix I have found is to completely reset my router and lan network and then the list will come back up normally and I can connect to a server once again, but usually for only a short time.
If anyone has a fix for this problem, it would be greatly appreciated. I havent been playing the game much lately, cause it has been too annoying to reset the entire lan.
Sounds like a buggy firmware to me. Have you tried a different (not necessarily newer) version?
A friend (Charming_fox) and I have had the same problem. We just manage to connect to the master server before the internet connection drops.
I seem to have cured my problem by downgrading the firmware of my DG814 to version 4.7. Everything seems to be fine now I have just tried connectiong to a couple of game and my connection has not dropped yet.
All I can say it try it and see what happens.
Good Luck!
The DG814 is really the worst ADSL modem/router you could possibly ever own, I know because I have owned one since they were released. The router crashes when you generate lots of UDP traffic (like you describe), and you have to manually reboot the thing. You will find the same thing happening every time you try anything really UDP intensive - like EDonkey, or Overnet stuff.
This will never be fixed, I have been in contact with Netgear support for ages, had new routers, all the Beta firmware releases and nothing fixes the basic fault. The fact of the matter is that the router is just not up to the job.
If you can limit the amount of UDP you are generating it might crash less often. For example, I use ASE to find servers, and you can limit the number of packets it sends per second when you scan servers.
The only long term fix is to get another modem/router box (I have used DLink boxes without any problems), and never to buy anything from Netgear ever again. Which is a shame, as all the stuff I bought from them before was cool.
Well I didnt say, but my router is a dlink di-604. I did upgrade to the latest firmware cause there were so many fixes in regards to the mac address translation which is needed for my cable modem.
Fwuffy Kitten you say you havent had any problems with dlink? Is there a certain setup or something you are using? Any suggestions would be greatly appreciated.
a friend of mine who is network/IT oriented and used to work for an isp was having the same problem. So he did a little research on it and it seems to be a limitation of the router itsself. Supposedly the router can only track a theoretical limit of open connections on any given port. I have this problem with my own router when i get portscanned. incidently we both have linksys BEFSR41’s
-sendep
Velma - I am afraid I only have experience of the DLink DSL-504. I installed one at the same time as I installed my DG814 and to my knowledge it hasnt crashed yet. Whereas my DG814 was crashing about 100 times a day isn the early firmware releases.
The DSL-504 is an ADSL modem/router, I don’t know much about the cable options. I do know that lots of these boxes are based on underpowered hardware, so the less load you put on the thing the better. If you can try and limit the number of concurrent connections the box wont have to maintain such a complex NAT table. A posssible solution might be to put your computer in the DMZ (if there is one) - which might mean the router doesnt have to maintain a NAT table, but I would be worried about doing that in the longterm.
Sorry I couldnt be of more use, but good luck.