Error 10065

Alright, I just downloaded and installed version 3.55, upgrading from 3.50. As soon as I try and open a connection to any MUD, it waits for a couple of seconds then sends me an error 10065 dialog box. If I retry, same result. I tried a backup of my files: same result. Reinstaling 3.50: same result. Restarting everything: you guesssed it, same result. I've tried turning off the firewall, but it still doesn't connect. This is on Windows ME. Any suggestions?

What have you done recently? Sounds more like a computer/ISP problem rather than MUSHclient. Have you tried using Quick Connect? Did you try turning off all firewalls, virus protectors, and so on? What OS? This only started happening after you upgraded?

You sure the mud is up?
10065 is no route to host. It's probably not a MC issue.
Theres something blocking you from connecting. But not a MC thing (if you want to test it, connect via telnet).

Could be a router, could be your ISP, youve turned off your firewall... hmm, I think if the mud is down you get a 'timed out' error, but you might want to check that anyway.

I'm 100% sure the MUD is up. I can connect to it via normal telnet, but when I get MUSH to connect it fails. And no, Quick Connect does not work either. This only started happening once I started using 3.55, and the OS is Windows ME.

Make sure you don't have any proxy options turned on. The only thing I know that does this is your computer/firewall is blocking outgoing connections to a certain port.

That is the "host unreachable" message.

I don't think any networking code has changed in this version, and personally I can still connect to MUDs, and I presume others would have said something if it was a major bug.

Can you try a couple of things?

• You say Telnet works, is that from exactly the same PC? And to the same MUD?
  
• Can you find the IP address, and use that? (eg. rather than www.smaug.org try 216.251.47.10). Looking up the name to IP address is another step in the process.
  
• Try version 3.50 again, see if the problem goes away.
  
• If you are using a firewall like ZoneAlarm, check its configuration. With ZoneAlarm you let applications through, but I think it checks it is exactly the same file (in case a virus replaces one by another of the same name). So, you may have let mushclient.exe through, but that is the *old* mushclient.exe, not the new one.

It's exactly the same PC, and exactly the same MUD. 3.50 doesn't work, I reinstalled it and it works with neither the backup or the real file now. I turned off all firewalls, the only things running that show up on the task manager are Explorer, Systray, however many Firefox windows are open at that given moment and MUSHclient.

I just upgraded from 3.54 to 3.55, and I have no problem. In fact, I do use ZoneAlarm and I have never had a problem like this. Nick, does reinstalling MC reset all client settings?

It shouldnt. If you uninstall, it will remove the registry, but installing overtop shouldnt change anything.

Unless of course youre asking about with zonealarm.
With norton, then yes, reinstalling is a new instance, and you have to allow stuff through again.

Which Ill bet is his problem, he probably, inadvertantly set something so he disallows MC to connect via whatever firewall. Although he says he turned them off, so who knows.

What else have you installed to change things? Could his winsock be bad?

So the problem isn't really the upgrade, as the earlier version doesn't work either.

You could try an uninstall and reinstall of MUSHclient. That will delete all registry entries that MUSHclient put there.

However I can't think of anything it puts in the registry that would stop it connecting.

I haven't used Firefox, but a quick browse of their web site seems to indicate it has some sort of filtering or blocking system. Here is a quote from them:



Did you install Firefox recently? The fact that your earlier versions of MUSHclient also do not work seems to indicate it is not a problem with MUSHclient per se, but how your system is configured.

It is possible that Firefox, or whatever the problem is, is configured to allow telnet through but not MUSHclient. Try another client. Try checking your Firefox configuration/logs.

I don't understand what Firefox could possibly have to do with the connection, I don't think it messes with any other programs, it just minds its own business.

Oh, that Firefox is a company, I think he means the browser.

Oh I see. My mistake. However I stand by my statement that this not a bug in MUSHclient. After all, it happens to his earlier versions, which used to work.

Yes, I agree with that too, it's unlikely that it's a MC bug. Try to have MC connect to a port on your machine, if it can, then it's not MC's fault. If it can't, it means that the fault is on the PC, before it reaches the network adapter.

Ok. I purged all trace of v3.50 and 3.55 from my PC. I then install 3.56, put in one of my backup world files and...same thing. Trying to connect to localhost elicits the same response. So, what fault on my PC could be getting in the way?

Are you only trying localhost? Have you tried other MUDs?

I've tried localhost, the 5 top muds on topmudsites.com or whatever it is and the MUD I'm trying to connect to. Safe to say it's not confined to this one.

And only MUSHclient does this? Telnet works? Have you tried something like Gmud?

Yes, only MUSHclient does this. I can acess it through normal telnet and the in-house Java client that is provided on the MUD's website. I haven't tried any other, 3rd party clients, but I can't do anything on them I can't do on telnet; the main reason I want to get MUSH back is for my extesnsive triggers/scripts so I can do stuff.

Hmm odd. Nick, does MC use a different connection protocol or way to connect?

Hmm. Try renaming mushclient.exe to something else? Maybe the firewall is not stopping when you quit... I really can't think of anything else.

Yeah, the only thing I can think of, is boot in safe mode (with networking) with nothing else running, and try it. Actually, do you have a router? Routers come with firewalls, or certain ones do.

MUSHclient does not use a different way to connect - to do so would only make headaches for me (like this one).

I know it sounds like a MUSHclient bug, if that is the only program it is happening to, but it can't be. You say yourself that version 3.50 used to work, and now it doesn't. The suggestion about other clients was not to use them as a long-term solution, but to see if the problem is either:

• Only telnet works, but everything else doesn't (eg. another client also doesn't work); or
  
• Only MUSHclient doesn't work, but everything else does.

This would then show that the problem, which is almost certainly in the firewall configuration, is that MUSHclient is blocked, but everything else can get through, or telnet is allowed through, but everything else is blocked.

I think some programs like ZoneAlarm can actually block accesses to localhost too, basically they detect any network access.

I agree with the "safe mode" idea, that will hopefully let you in with the network but without the firewall.

Ok, I dug up my oooold copy of zMUD and it works on that. Safe mode is very problematic for me, it refuses to acknowledge the presence of my mouse, broadband connection or anything else. So, yeah. No drivers is proving very difficult, safe or not.

Check Zone alarm. If MC is in the list, check if its blocked (unblock it) if it isnt in the list, make a point to add it (and allow everything).

Norton asks me twice about MC. Once about listening to connections (when I start it) and then again about connecting to a DNS, or a world or whatever (when I connect).
So it needs (maybe not needs, but at least Im asked) to be able to both send, and listen to connections.

Dont know how crippled it would be if it isnt allowed to listen. Nick could answer that.

Point being, check zone alarm, your router, anything else.

I just tested 3.56 on Windows 98, at it works fine. However on that PC I had ZoneAlarm installed, and it asked me three times if it could let MUSHclient through:

• One for "acting as a server" because one world had chat listening enabled
  
• One for "connecting to localhost" - for DNS lookups
  
• One for "connecting to the internet" - for connecting to an external MUD

If I denied those I got "network is down" I think, however it seems to me that your problem must be with your firewall, although conceivably it is the Winsock DLLs. If you had previously (somehow) denied MUSHclient access and told the firewall to remember that denial, then you probably won't get through until you un-deny it.

What you could try is, rename mushclient.exe as something else, eg. mushclient2.exe, and try that. The different name might get through the firewall. However if it remembering the file location that might not work.

In that case, download version 3.56, which is a different file, and after installing, but before running it, rename that to mushclient2.exe. Then try that.

Finally, see if you can upgrade your Winsock DLL. Have you changed it recently (eg. installed a service patch, changed your Winsock DLLs)?

ok, i have something like this happening to me but i think that my case is a little different. I installed Mushclient on my PC at school running windows XP and it worked just fine useing quick connect. Then i go home i have Version 3.65 installed so i try to run it and i get the same error message at anonymous. Now i did just as he did and purged it, downloaded it and then instaled it again. But there is something that i nitoced, just behind the error message is a thing that thanks me for evaluating version 3.50. That kinda confused me, why am i evaluation version 3.50 of I downloaded version 3.65?

Are you sure youre running the correct instance of MC?

Go to Help > About, Whats the version? Perhaps you have both of them installed?

nope, it only says that mushclient 3.65 is installed, granted it is an unregistered copy, would that have anything to do with why it wouldnt work?

Wouldn't work as in connecting? No. Mushclient is fully functional (save the spell check limit) as a trial.

It might be an old message that nick didn't catch when upgrading, but that seems unlikely.

Try connecting to the server via telnet, it might very well be that the server is down at the moment.

and call me an idiot...but what is telenet? cus i've never heard of that before in my life.

telnet

Telnet is a client for plain text communication with a server. You probably have it on your Windows computer: just go to start -> run and type "telnet" - that should give you a prompt.

MUD clients such as MUSHclient are, sort of, very sophisticated pseudo-telnet clients. Ideally, people can connect to a MUD with either a telnet equivalent or a MUD client and get the same game experience. MUD clients tend to add things like macro/trigger/logging/etc. support. Telnet just lets you type and be typed at. :-)

start > run and type in "telnet" hit enter.

then at the prompt, type "o [host]:[port]"
You can view the help by typing "?".

Telnet is a protocol. Muds use telnet, mud clients are just fancy telnet clients.

And on a side note, you can edit your posts by clicking on the edit button (while logged in).

ok, no telnet isnt on my computer but i found a place to download it, now before i do i just want to make sure. Telnet does stand a good chance of fixing the problem right?

ok nevermind im a liar. I do have telnet i just have no clue how to use it for anything.

type "o [host]:[port]" of your mud server. We're trying to get a 'second opinion' of if the server is down (or if its Mushclient, or a problem with TCP/IP).

If you have any friends who also play, you could ask them (assuming you can get ahold of them at the moment) or if your server has a website that reports whether it is up or down, check that as well.
I believe the mud connector has a page to check if your mud is up.

I'm almost willing to bet that its the TC/IP. im going to try to get on useing telnet cus i think i worked it out with my simplton mind....here goes nothin

nope...still nada. I also am starting to get anouther error message as well. This one is 11001 i think, or maybe it was 10011. one of those two but it says that it is unable to resolve host name.

Whats the server info? Check on Mudconnector to see if it's up.

What makes you think its TCP/IP?
You can go ahead and reinstall your protocol, see if it helps.

at least the TPC/IP on my version. My friend got on just fne and is talking to the game staff about my problem, they're trying to figure out whats going on too. so i know that the game server is up so it must be something else

now, if i wanted to reinstall my protocol, how would i go about doing that?

Can you connect to any other mud servers?
If you can, it's not a protocol problem (or a Mushclient problem).

Double check your firewall settings.

problem 1. I only know of 1 game and this one is listed as a MOO

Problem 2. Dont know how to get to my firewall. my computer has a sercurity stsyem like a labridth

I'm willing to bet you a great deal that the problem is not coming from a faulty installation of your TCP/IP protocol... do you think yourself a victim of a conspiracy theory? :-)

Think about it a bit - you're posting here aren't you? Clearly your networking is working right at least for that much. There are many factors here; for one, it might be as simple as a firewall blocking the port somewhere along the way.

I would suggest that you talk to a system administrator or somebody who can help you out locally to figure out your computer system. This kind of problem is extremely difficult to debug remotely if you can't look at your firewall and tell us something about its settings.

I'm a little curious about this message. What is the wording exactly? The version number is stored in a single place in the program, it shouldn't show one version and thank you for evaluating another.

In fact the little window that pops up when you first use MUSHclient does not have the word "evaluating" in it.

Are you by any chance using a "cracked" version? Whoever did the cracked version may have put in a screen about "thanks for evaluating version 3.50", and not updated that screen for recent versions.

If you are using a cracked version the error message may relate to the program trying to connect to the cracker site in order to send personal information from your PC. Naturally this code is not something I put there, but a risk you take when using cracked versions.

Not to mention a bloody stupid way to crack it... It would probably take less effort and time to generate a key to break it than hardcode a possible trojan, keylogger or other gadget into the program. With cracked versions, where the guy went into that much trouble, you are likely to end up paying for what you get, just not with money. A bit different in the days of games you couldn't copy the bloody disks for, so you had to hack their boot loaders as the only way to make backups. But today, its just damn stupid to trust people that go to that much effort on something as relatively unprotected as this...

Thank you for evaluating MUSHclient version 3.50!

----> This is an UNREGISTERED copy <----

To purchase your registration please visit:
http://www.mushclient.com/fee.htm

For information and assistance about MUSHclient visit our forum at:
http://www.gammon.com.au/forum/

This message does not appear once you have registered.
(The above links can be found under the Help menu)

Thats what the window behind the error message reads Nick. That shows up after i use the quick connect option, i fill it out correctly

World Name: acadiana
TCP/IP: acadiana.acadianamoo.com
Port:9999

It works on three computers, just not mine, I'm haveing a friend come over who is a total software guru. I'll have him find out what the problem is and let you guys know so we can get some closure on this.

And i dont know if i got a cracked version but i downloaded the version that is available from this site. Granted, i dont know if that is the right copy to get or not, but seen as how its comming from you, i figure it almost has to be a good copy...anyway...ill try to figure out what is wrong in the mean time

Oh, that message. :)

That is in the output window when you connect to a world. However that should still be the correct version, it shows 3.65 when I try my 3.65 copy unregistered.

So what you're saying is that when i see that i am connected to the world? Cus when i do the correct logon {Connect Tycho Bradock} it tells me it has no clue what im trying to do. So like someone sugested i went and tweaked with my firewalls, unblocked the correct port, only now when i downloaded the version from the link on this site, there was no .exe file in the package so now i have a version with no "go" button

You've lost me a bit here. The download *is* an exe:

http://www.gammon.com.au/files/mushclient/mushclient365.exe

When you run that you get - amongst other things - mushclient.exe which is the actual program.

What "go" button are you referring to?