I tried running PennMUSH under Windows NT, though, and it tells me it can't run as a service, so it runs locally. I can connect to it locally, but remote users cannot.
I am an administrator, so I should be able to start services.
I downloaded a new NT version of PennMUSH but I get the same error.
You have two separate problems here. I would solve them one by one.
1. You can't start a service.
2. Others can't connect.
For 1 - check that under the User Rights policy in the User Manager you have the right to Log On As A Service.
For 2 - what else have you changed? Are you giving them your external IP address? Is there a firewall? NAT router? There have been other posts about this subject recently.
I'm getting similar problems when I try to run on XP, and, again, I'm the only one using the PC, as an admin. And, yes, it worked fine on '98 back when I had that, but now it cannot start as service and so doesn't accept external connections. It's not a firewalling issue, since all the firewalls there are disabled and I've tried in on quite a few ports.
Attempting to start PennMUSH as a service ...
Unable to start service, assuming running console-mode application.
You can save time on the next invocation by specifying: pennmush /run
Redirecting output to: log\game.log
There's usually quite a wait between the first line and those following it.
Using /start parameter flashes up a window briefly, but it's too quick to read. The same with /install.... if you really need the messages I've got screen capture around somewhere.
Last night, after fiddling around with the local security policy (allowing local and network access to start as service), I somehow ended up with no delay between the first line and the rest, which I then managed to get back by manually starting Telnet as a service.... I can't see anything about servers in my ISP's AUP, are there tests I can run to narrow the problem down? As said, it used to run fine on '98, so I doubt it's the ISP and more likely the OS.
Ah, I see what is happening. For a start, I would run it under a console window so you can see the error messages. The pennmush.exe is not intended to be run double-clicked, for this reason.
To start a console window, go to: Start -> Run and type "cmd" (or under Windows 95/98/ME type "command").
First I would type:
pennmush /run
and see if there are any error messages (eg. can't load config file)
If that works OK, then shut the MUSH down and install it as a service:
pennmush /install
Then you can start it:
pennmush /start
Here is an example:
F:\pennmush\game>pennmush /install
Service successfully installed
F:\pennmush\game>pennmush /status
The service is not running.
F:\pennmush\game>pennmush /start
Start request sent to service
F:\pennmush\game>pennmush /status
The service is running.
[mono]D:\Games\MUSH\pennmushNT\pennmush\game>pennmush /start
Start request sent to service
D:\Games\MUSH\pennmushNT\pennmush\game>pennmush /status
The service is not running.[/mono]
Seems to be an unwanted not there.... :P It was already installed so I removed, restarted, and re-installed.... still nothing.
Also, by trying to run it manually from the services dialogue under the control panel, I get an "Error 1067: The process terminated unexpectedly".... things aren't looking good, thinks me.
Just says "Redirecting output to: log\game.log", then runs.... I can get into it locally, but it seems external conns still can't happen.... no termination (unless, of course, you click the little X.... :P).
Ok, wierdness, that.... MUSH connectivity checker that was there in the other post (moosh.net) says that my MUSH is running, and yet people can't connect when I give them the IP and port.... also tried with TinyMUX, and the same, they can't connect but it says it's up.... what's with that?
That sounds like a firewall issue to me. Either you have one on your local computer (Windows XP has a built-in firewall for instance), or you have one on your local network somewhere (if you have one), or you have a router that has one (possible if you are using ADSL for instance.)
Grue, I'm on ADSL.... there's no way around that? And I know it's not the XP firewall, 'cause I killed that.... but we've had ADSL longer than XP, and I remember it working on XP.... I think.... not sure, I'll find the logs....
My (current) IP's 80.46.213.235, but that changes every time I sign on....
Ok, yep, I had it working on XP, that was back when I was playing around with the firewall and found out you had to disable it to allow external conns....
Do you mean, you had it working on 98? That is what your original post said.
It seems likely that if you can connect locally that there is indeed a firewall issue at work, assuming you established your correct IP address.
One possibility is that your ISP is also blocking incoming connections, perhaps your user agreement does not permit running servers?
An interesting thing to do would be to try running a MUSHclient chat server temporarily, to see if you can get incoming connections working with a different program. You can configure that chat port (eg. make it 4000), and then get a friend to try establishing a chat connection.
If that doesn't work either, it rules out the issue of the service, or PennMUSH as such.
I meant I had it working on '98, then when I upgraded to XP it continued to work (for a while.... :P). How do you make a wierd chatty servery thing thing then? :P (and I'll have to poke my ISP for being firewally.... :P)
Ok.... did it.... and.... a timeout. So, I guess that means we're talking ISP not allowing the running of servers, and there's no way around that without switching ISPs, right?
Ok, you're all gonna hate me.... I.... erm.... kinda.... found that my virus scan has a built in firewall.... and.... turned it down a setting.... and.... IT WORKS! HOOOORAY! ^_^
Apologies for timewasting! *dances a jig into the sunset*
Apache - ip = 10.1.1.3 - port 80
TinyMUX - port 6060
PennMUSH - port 6161
Now what you will need to do is firstly;
Add a NAT rule to allow outside access to your webserver (apache in my case)
Rule ID: 5
Rule Flavor: RDR
IF Name: ALL
Protocol: ANY
Local Address From: 10.1.1.3
Local Address To: 10.1.1.3
Global Address From: 0.0.0.0
Global Address To: 0.0.0.0
Destination Port From: 80
Destination Port To: 80
Local Port: 80
Then for your mu*;
Rule ID: 11
Rule Flavor: RDR
IF Name: ALL
Protocol: TCP
Local Address From: 10.1.1.3
Local Address To: 10.1.1.3
Global Address From: 0.0.0.0
Global Address To: 0.0.0.0
Destination Port From: 6161
Destination Port To: 6161
Local Port: 6161
Hope this helps..You may not need to forward a port for the webserver - but you never know lol