I just recently downloaded the latest TWGS and installed it on Windows 2000 Server. The first time I ran Bigbang on Game1 and tried to log in, when I selected "A" it went back to the same menu. So I ran Bigbang again, and then it worked. Until a few hours later when logging in and selecting "A" for Game1 causes an infinite loop lockup for the Telnet client. Any ideas what could be causing this? I want to evaluate the game to see if I want to purchase it later, but I cannot even get the game to work so far without locking up.

Any ideas?

have you bought the game or is it just the unregistered version...The unregistered version only allows 3 minutes at a time to run before kicking you off....That might be a reason
Strider

It is unregistered, I think I said that. It does not kick me off, it locks up. I was playing it earlier and after 3 minutes it logs me off and lets me log back on. But then later it just locks up as soon as I select Game1 and type in "A". I use Putty, and as soon as I get logged off Putty exits. But in this case Putty doesn't exit, and the terminal sits there for over 15 minutes doing nothing, still connected.

Next time that happened, without disconnecting your first client, log in with a second and see if you can get into the game. There are occasional problems with certain nodes that make them unable to enter a game. It does the sort of thing you're describing. Another thing that may cause the sort of problem you're having is game corruption. If the problems continue, you may want to renstall the software and rebang your game.

No luck, I logged into a second session while connected to the first and got the same lockup.

I'll try to reinstall the software and Bigbang the universe next. Thanks for your advice.

Ok I uninstalled TWGS, reinstalled TWGS, ran Bigbang again. This time I created a Game A and Game B. Ran locally, ran fine. I went to another machine and telnetted to the server, ran fine. A few hours later I get home, telnet into it, and choose Game A, it locks up. So I logged into a second session tried Game A and it locked up. So then I thought, well maybe Game B is up, so I tried that and got the same results.

I have the current version of Anti-Virus updated and no virus scans, ran Spybot, no Spyware/Adware loaded. I ran the disk checker, no errors found. I am not sure how the game is getting messed up, but it is.

I run Windows 2000 Server, are there any issues with W2K Server that I should be aware of? NTFS32 partition is being used.

The game runs great for a few hours, and then locks up. This is fustrating.

Weird, if I quit TWGS and reload it, it works fine. No need to run Bigbang. Somehow it is getting clobbered in memory after a few hours of running. The TW games that is, the login screen for TWGS works, but as soon as someone selects a game, it locks up.

I'm sorry, I have no idea on what the problem is. Never run across anyone having that happen. It might be related to being an unregistered server, but I'm not sure.

Just out of curiousity what other processes are running on the machine? I have found a couple that screw up the TWGS and/or TW2002 sessions, namely Open File Manager and the NovaNet backup software (version 7.x). Another thing that comes to mind is are you using an ISP such as SBC that has DHCP set to hourly IP address aging? I don't know how gracefully the TWGS handles that. Possibly conflicts with other 3rd party winsock applications such as time synchronizers and such could be part of that mix also. There's plenty of places to look but I'd start with background processes.

What I have running:

AVG Anti-Virus
MS SQL Server 2000
DirectUpdate (Using SBC DSL, this updates my domain name to the current IP)
GameSVR (Telnet Server for my WWIV BBS, on a different port)
VNC Server
Seti@Home screensaver

I also have the .NET Framework 1.1 installed with IIS running as a server.

That is it. Any of those processes conflicting with TWGS? How can I tell?

I can provide more info if it will help debug the software or figure out problems for other people.

I think i am having the same sort of problem.. People can log on to my server, but when they try to get into a game, their client locks up, and it just blinks the letter of the game they selected.

you can see for yourself at jama.no-ip.info port 23

My current set up is dsl modem -> router which points port 23 to ---> server..

Do i need open another port for people to actually play?

Jama, what OS are you using? I am using Windows 2000 Server.

Is your DSL a static IP or a dynamic IP? I have a Dynamic IP which DirectUpdate updates every 5 minutes to the current IP for the domain name I use. I think SBC is doing something goofy on their end to prevent Server apps from working properly on Dynamic IPs. I cannot seem to find anything that would be causing this on my server.

Yeah, i have a dynamic IP.. I use software called no-ip.. I load a no-ip client on my comp and it sends my ip to the no-ip server. The server then takes the name jama.no-ip.info and points requests to myip. So then my router redirects requests for port 23 to this specific machine on the network. It is weird that people can connect to the server, but when they pick a game, the client locks up.. Do i have to open another port in my firewall for when people select playing a game?

telnet to jama.no-ip.info and see what happens.. Maybe one of you gurus will figure it out in a split second

I think what is happening is that your ISP is blocking Server Protocols for Dynamic IPs. I have SBC DSL and the same thing happens to me, not locally, but over the Internet. They detect a Telnet session and then block it as soon as it gets some activity. The reason for this is so that Dynamic IP users have to upgrade to a Static IP to run a server, and Static IPs cost more. One ISP, Speakeasy.net, allows you to run Servers over their DSL lines, and cite that many other ISPs block the Server Protocols in some way.

It really bites that they do this. I use DirectUpdate, it does the same as No-IP, synchs up my Dyanmic IP with a domain name.

What ISP are you using, so I know not to do business with them?

I have SBC DSL and have no problems with telnet or SSH (ports 23 and 22) dropping incoming connections. I do not run a web server locally in an attempt to stay under the radar to a certain extent but I can stay connected all day long to my GameSrv and Linux boxes without any problems. My work blocks port 2002 so I cannot get directly to my TWGS to test it from outside but reports that I have back are that it works fine. *shrug*

quote:Originally posted by Orion_Blastar
I think what is happening is that your ISP is blocking Server Protocols for Dynamic IPs. I have SBC DSL and the same thing happens to me, not locally, but over the Internet. They detect a Telnet session and then block it as soon as it gets some activity.