Server-hosted games - machine going to sleep? - Page 2

Norfleet · #11 January 18th, 2004, 08:46 PM

I've only noticed this to be especially prevalent when the server is chewing on a new turn: There's a time between when it announces that the hosting will occur, and the time when it actually completes the process. If you try to connect during that time, the game will wait for game data for a goodly amount of time, because the server is busy chewing on a new turn and won't respond to your request until it finishes.

alexti · #12 January 18th, 2004, 09:00 PM

Quote:

Originally posted by Zen:
Maybe someone who knows more about such things than me could offer some help or advise.

I could give some ideas, but I need more details:
- if dom2 doesn't allow to connect anymore, does restarting dom2 cure the problem?
- if it doesn't:
- do other application using TCP/IP work? (email, browser etc)
- is it necessary to restart OS, router, both or either

Alex.

[ January 18, 2004, 19:02: Message edited by: alexti ]

ceremony · #13 January 18th, 2004, 10:13 PM

Quote:

Originally posted by alexti:
I could give some ideas, but I need more details:
- if dom2 doesn't allow to connect anymore, does restarting dom2 cure the problem?
- if it doesn't:
- do other application using TCP/IP work? (email, browser etc)
- is it necessary to restart OS, router, both or either

Alex.

Restarting the game hasn't fixed the issue. Restarting the router has. Also, taking the game down and putting it on another port has fixed it. No other TCP/IP services are affected - when the game freezes like this, all comuter on the network still have network and Internet access.

alexti · #14 January 19th, 2004, 12:53 AM

Quote:

Originally posted by ceremony:
Restarting the game hasn't fixed the issue. Restarting the router has. Also, taking the game down and putting it on another port has fixed it. No other TCP/IP services are affected - when the game freezes like this, all comuter on the network still have network and Internet access.

Could somebody run

code:
netstat -na

(and post here its output) when this problem happens? Please run it one time before restarting anything, second time after restarting Dom2 (with the same port) and third time after resetting the router?

Alex.