MUSH appears to run, telnet fails to connect

Hello there!

I've been running the NT-only version at home and it works fine.

Right now, at the office, I've tried to run the "generic" Win32 version. I double-click on it, it says "redirecting output to game.log" and stays there.

I check the log, and the last few lines read like this:

...
ANALYZING: data/indb
ANALYZING: data/indb (done)
LOADING: data/indb
READING: done
LOADING: data/indb (done)
02/13 10:06:01 RPT: No access.cnf file found.
Listening on port 4201
56 file descriptors available.
RESTART FINISHED.


It seems that the server is up and running. When I connect via telnet, it just stays there with a blank screen, after 5 mins or so it says "connection to host lost" or something like that.

I've tried "localhost", "127.0.0.1", "192.168.0.1" (my LAN IP) all with port 4201, but no cigar. (i've also tried modifying the MUSH.CNF accordingly to fit each address, AND i've tried leaving it blank)

Any help is welcome.

I don't suppose you have any sort of firewall on the work PC? It should work, but what you describe suggests it isn't.

I am having the same difficulty.

I have the pennmush172p29.zip file. I have the minimaldb and indb all set up, but after I run the program it says:

C:\pennmush\game>pennmush /run
Running under Windows NT
Redirecting output to: log\game.log
Starting MUD listening thread ...


and here is the bottom of the game.log

Input database verified. Proceeding to analysis.
ANALYZING: data/indb
ANALYZING: data/indb (done)
LOADING: data/indb
READING: done
LOADING: data/indb (done)
02/22 19:31:50 RPT: No access.cnf file found.
Listening (NT-style) on port 4201
56 file descriptors available.
RESTART FINISHED.

My question is there any known difficulties running on Win2k sp2? I have no internal firewalls or anyother port blocking software that would block the local host from connecting to itself... Thanks in advance!

Brooks

All I can suggest is turning of DNS lookup, which might be causing a lengthy hang. Edit mush.cnf file, and look for this:


# Should the MUSH attempt to resolve IP numbers to hostnames?
# If yes, you'll see hostnames on the wizard WHO. If no, IP numbers.
# No makes sense if you're running PennMUSH at home and don't have
# a DNS server you can access.
use_dns yes


Try changing "yes" to "no".

Thanks for the help! That actually worked out for me. Then I put it on a server and connected from an outside address and it also worked... Maybe there was something wrong with the internal address stuff... Who knows, but thank you for the assistance!!

Actually that had me confused for a while when it first happened to me, but it was a few years back and I had forgetten about it. :)

When someone connects the server tries to resolve their IP address (eg. 1.2.3.4) to a name (eg. openbsd.org), and if there is no path to the DNS (domain name server) it keeps trying for quite a while before timing out.

This makes the server appear to hang, and conceivably the connection you are establishing would time-out before the server recovers.