I finnaly got my internet back up again, (yay! ^^) but...now I can't connect. *huffs* -.-
I can connect to all the other MU*s I'm on, except the XenoMUCK and Fa'Diel. So, it would seem that I'm only having problems here. ^^;;;
(I can't connect to it at all, not guest or player, but I can't even get to the start up)
The only reason I bothered to clutter the board with this, is that I just wonder if anyone has any suggestions, b/c I'm blank and computer illiterate for the most part. ^^;;;

By Brin on Saturday, June 02, 2001 - 09:15 pm:

Hm. 24.114.64.40 port 44321 seems to work fine.

By Xeero on Saturday, June 02, 2001 - 11:48 pm:

I had a similar problem in connecting to another MU once. We fixed the problem by bouncing the connection off another server, but I don't know if that'll work in this case *shrugs*

By Aya on Sunday, June 03, 2001 - 04:33 am:

Oh dear, this isn't fun at all. ^^;
I've now tried telnet, Zmud, Gmud, MUCKClient and SimpleMU* and none of those programs can connect to the MUCK for some reason, but they can connect to the rest of the MU*'s. ^^;;;

By Xenotech on Sunday, June 03, 2001 - 06:12 am:

What does the error message say?

Try opening an MS-DOS prompt. In the window, type:

ping xenomuck.mine.nu

If you get numbers, that's good. If you get "Request Timed Out", then that's bad.

If xenomuck.mine.nu doesn't work, then try
ping 24.114.64.40

ping is a diagnostic utility that sends a small packet to a remote server. It checks if it can reach a remote computer. If you can't ping, then there's something unique with your connection that prevents it from working.

If that fails, try connecting to the old Xenogears MUCK port (at 4321). If it is successful, you should receive a redirection message.

By Jalon on Sunday, June 03, 2001 - 07:42 pm:

I'm having the same problem Aya. I'll try and see if that ping stuff will work. If not, I guess I'll later post a message saying I won't be back anymore.

Of course, it could be that I'm using Telnet.

By Brin on Sunday, June 03, 2001 - 07:51 pm:

The client you use shouldn't matter at all, telnet, GMUD, and whetever all use the same method of connecting. Try using the IP address of 24.114.64.40 instead of xenomuck.mine.nu and see if that works.

Also, some networks might block ICMP (in fact, most should), so pinging mightn't work. Try typing

tracert xenomuck.mine.nu

into an MS-DOS prompt. Post the result, and I might be able to tell the problem.

Incidentally XT, why did the port have to be changed? Jus' curious.

By XenoTech on Monday, June 04, 2001 - 01:35 am:

The port was changed to avoid Port Scan detection from my ISP. It is illegal to host servers off of my connection. I should be paying $180 a month for a server-capable connection.

By Casske on Monday, June 04, 2001 - 05:01 am:

Joseph had some kinda problem. I told him to try doing something... it was either using the old adress or port, I have no idea. He said it worked, and logged into the new location, though.

By Aya on Monday, June 04, 2001 - 05:04 am:

Hrm, well the ping timed out both times, unfortunatly. :|

I tried the tracert like you said Brin, and I don't understand a word of it but this is what it came up with...

Tracing route to xenomuck.mine.nu (24.114.64.40)
over a maximum of 30 hops:

1 <10ms <10ms <10ms 192.168.0.1
2 * * * Request timed out.
(and then it just kept repeating that)

By Brin on Monday, June 04, 2001 - 03:25 pm:

XT, how do you know what ranges the ISP is scanning? They might be doing just less than 1024. And your ISP is evil >:|

Aya, that might look like your personal firewall being a nasty evil thing again. 192.168.* is an IP usually used on LANs. Do you have a LAN set up in your house?

Incidentally, the link on the front page of the MUCK page doesn't work, in case anyone is using it

By Jalon on Monday, June 04, 2001 - 08:03 pm:

Alright!

I'm on Telnet, but what I did was go to the connection drop-down menu, went to remote connection, and manually typed the new address and port in for a remote connection. Apparently it's working now, so I'll be able to connect again.

By XenoTech on Tuesday, June 05, 2001 - 03:07 am:

Brin,

It's in the license agreement. I accepted it. So it's my own fault.

I'm unsure if they scan only > 1024. I figured htat it's good not to take a risk. Also, Xenogears MUCK was running on the same port as a few known trojans, so anyone scanning for those trojans discovers Xenogears MUCK and wonders for a moment. The ISP might anyhow.

In any case it's to lessen the risk thorugh Obscurity. Not a good way to guarantee protection but it's easier than having my Connection suspended for a week without warning.

By XenoTech on Tuesday, June 05, 2001 - 03:11 am:

I think I'm going to write up a "Connection FAQ" to replace Domi's connection FAQ on her page. A lot of people get problems with their Personal Firewalls or Proxies.

If you're running on a Network, Ayame, you may have a Firewall blocking certain ports, including 44321. If you wish, E-mail me (or Brin) with more information about your Computers.

By Brin on Tuesday, June 05, 2001 - 06:18 pm:

Good Idea XT. And it's a pain about your ISP. Good plan to change the port, I doubt any ISP would be so anal as to scan anything that isn't a recognised port. 4321 is reserved for rwhoisd or somesuch. 44321 is much better.

Yeah, a connection FAQ is a good plan. Who knows how many potential players we might lose through connection problems?

Do you have the name of the Personal Firewall software Aya? And did you kill it completely that time, or just get someone to enable the correct ports?