How to troubleshoot your connection to ArmageddonMUD
Author: CRW, Technical Helper
Note: Before doing any of the following connection diagnosis steps, go to
http://www.armageddon.org (if possible), and scroll down to the bottom of the
page. Right below the text "Armageddon runs at ginka.armageddon.org 4050." there is a status line that is
automatically
updated. If it suggests that Armageddon is not running, then there is a problem with
the
MUD itself and the staff will resolve it in short order.
--MAKE SURE TO HIT the REFRESH or RELOAD button on your web browser if it has
one.--
If the status line says otherwise, you should continue with this guide.
NOTE - This guide should work with Windows, OS/2, and Unix/Linux operating
systems.
The intent of this guide is to walk you through some basic troubleshooting
steps
that you can do to better diagnose where your connection problems lie.
Step 1 - Check your own internet connectivity
- In a web browser open http://216.115.102.75
(This is the IP address of www.yahoo.com)
Success Means: Your computer is connected to the internet.
Goto Step 2
Failure Means: Your computer is not talking to the internet
Recheck your connections and reboot. Contact support staff
where applicable.
Step 2 - Check basic connectivity to ArmageddonMUD's server.
-
In a web browser open http://www.armageddon.org.
Success Means: The path through the internet from your machine
to ArmageddonMUD is working. A more technical way to put it is
that traffic is being successfully 'routed' from your client
to the ArmageddonMUD server.
Goto Step 2b.
Failure Means: There may be a problem with your connection.
Goto Step 3.
- In a command prompt window (Start->Run-Command.com for windows
users)
type the following, hitting enter afterwards:
telnet ginka.armageddon.org 4050
This should bring up your operating system's default telnet client and
will attempt to connect to the mud. You should see the ArmageddonMUD
menu appear on connection.
Success Means: Your computer is able to successfully connect to
ArmageddonMUD.
If you are connecting from work, school or some other managed network
you may
need to look at the proxy server settings for your mudclient.
If you are connecting from home you will need to check your mudclient
settings.
Make sure that the hostname is: ginka.armageddon.org and the port is:
4050
in the appropriate configuration section for your mudclient.
Failure Means: A few possibilities.
Goto Step 3
Step 3 - Check DNS name resolution
- In a web browser open http://64.252.79.51
Success Means: You appear to have a problem resolving names in
the
armageddon.org domain. Replace ginka.armageddon.org with
64.252.79.51
in the appropriate section of your mudclient. You may want to
contact
support staff where applicable.
Failure Means: There is a problem communicating from your
computer to
ArmageddonMUD.
- Go back to Step 1 and verify a Success there.
- ArmageddonMUD may be experiencing a service outage.
- There may be an issue in transit between your machine and
ArmageddonMUD. This happens when one of the machines en route
from
your own to ArmageddonMUD is having an outage. These are rare
and
shortlived when they do happen and are normally due to a large
storm or
some other large scale event.
Goto Step 4
Step 4 - Email tradebledsoe@yahoo.com, with a CC: entry in your mail client to send a
carbon
copy to mud@ginka.armageddon.org. I or one of the staff will test
connectivity
from our end to see what might be at issue.
The Webmaster / webmaster@www.armageddon.org
© 2001 Armageddon MUD. All rights reserved.
