[GhostInAProgram]

I've been cleaning my room and rearranging some things (one of which happened to be my modem). I turn my computer on and restart my MUD's server and everything loads fine. I turn on my client and wam my MUD won't boot up. I restarted my modem and the same things happens. I restard my computer and modem and still the same thing. I even went as far to think that something broke some how in my files so I backed up my player files and city files then reinstalled the stock. Still... It won't work.

I'm thinking that something got really f*cked when I unhooked my modem and now my IP is messed up some how. Also, I've tried to start my MUD using the telnet client and still nothing.

Can anyone tell me how this happened or how to fix it?

Thanks.

[Kylotan]

If you're running a mud, you should know how to check the server's log files. You can do that, right?

[Newworlds]

Originally Posted by GhostInAProgram I'm thinking that something got really f*cked when I unhooked my modem and now my IP is messed up some how. Also, I've tried to start my MUD using the telnet client and still nothing. Can anyone tell me how this happened or how to fix it? Thanks.

The trouble with running a server (which is what a mud is) on a home computer is that your IP is never completely static. Depending on your ISP (Comcast/Qwest/Etc) your router will dynamically assign a new ip periodically, which makes your home mud worthless when you gain a playerbase because you will have to continually post the new IP.

Now to answer your question: Your MUD is likely running, but you are trying to connect to an incorrect IP addy. Try going to an IP identity site and look at the IP it shows you (or ping out from DOS or whatever operating system you are using) and write down the IP. Then log in on that IP. Bingo!

[Newworlds]

Oh one more thing as just an FYI. It is against any ISP's general use agreement to use your home computer as a server. Read the fine print, if they catch you they will disable your service.

[GhostInAProgram]

I got this resolved on a different forum.

Thank you.