Lag/Freezing up

I just installed a new router yesterday and have been having problems with MUSH Client ever since.

It could just be a coincidence and there might be a local node that's having trouble, but I figured it couldn't hurt to ask.

I had been using a Linksys router with a Linksys cable modem. I switched to a new Linksys router with wireless capability.

However, the problem occurs on both my wireless notebook and my desktop which has a direct connection to the router.

I have no problems with any other programs I use (Everquest, Outlook, AIM, ICQ, Internet Explorer), only with MUSH Client.

The problem is that after roughly five to ten minutes, the connection starts lagging horribly and then freezes up altogether.

Is there possibly a setting in MUSH Client I need to change? This problem has been occurring since early last night and has continued through this morning.

Thanks for any help!

Is the port forward?? That could be your problem. If its not go forward that port on the router.

My apologies for sounding stupid, but what exactly do you mean by 'forward the port on the router?'

Thanks for the quick answer! I wasn't sure if I should post this in General or in Bugs because I wasn't sure if it was me or a problem mush client had with certain routers.

I think I talked about port forwarding recently, so search this forum for "port forward". However, I doubt that is the problem.

Try also searching for "router" - I think some routers disconnect you after no activity for 5 minutes (which some programs work around by doing some sort of activity periodically).

You should be able to configure the router to disable this "disconnect after no activity" feature, or failing this, get MUSHclient to do something every few minutes (using a timer), like sending "look" or something like that.

And hope that the router is smarter than the same 'feature' in Windows. Some software and hardware seem to think that only FTP, HTTP and other similar protocals constitute 'activity', they will ignore Telnet completely and disconnect anyway... I think I heard of at least one router or something of that sort with a similar flaw.