Specific 10060 Error

Posted by Marinredwolf on Fri 22 Jan 2010 11:55 PM — 8 posts, 31,756 views.

#0
I just purchased a new laptop running Windows 7, and this seemed like a perfect time to get the newer MUSHclient 4.43 running on both that and my current desktop. I followed the instructions here for setting the program up in Windows 7, and all seemed to be well - I was able to connect to two different MUCKs with no problems.

On one specific one, however, I keep getting a 10060 timeout message, but only on the new computer. The desktop connects fine with the same (copied) world settings. This seems to rule out an issue at the router (or ISP), as both computers are using the same one and I didn't see any settings there that should be blocking anything. MUSHclient is allowed access on the laptop's Windows Firewall (even disabling it temporarily didn't seem to help), and I'm not finding any other firewall program.

Any further advice on what might be blocking a specific world/host on only one computer on this small network?
Australia Forum Administrator #1
Maybe the port number? Can you tell us the IP address and port?

Also try using straight telnet (assuming that comes with Windows 7).
USA #2
Nick Gammon said:
Also try using straight telnet (assuming that comes with Windows 7).

In Vista, I think you have to enable it from Control Panel -> Programs and Features -> "Turn Windows features on or off". I don't think W7 would be that different.
Australia Forum Administrator #3
Some searches appear to indicate that it might be an issue with Windows 7 automatically trying to use a proxy server on some ports. For example:

http://www.west-wind.com/Weblog/posts/3871.aspx


Frustrating though this stuff is, it seems it can't really be the fault of MUSHclient, as it works perfectly on your desktop. And indeed, connects to some MUCKs perfectly as well. It seems the thing that has really changed is .... Windows 7!

Strange though it may be that some sites work and not others, this is exactly the sort of thing I have come to expect from Windows where it tries to "help" you by second-guessing what it thinks you want.

A bit like the other case recently where the log files were not being written where they appeared to be.
#4
I figured it had to be something Windows 7-based, but this seemed like as good a place as any.

The MUCK in question is at 99.21.44.60 port 1492

After enabling telnet (thanks for pointers on that), I can connect fine that way, but still not with MUSHclient. For what that's worth.
USA #5
I can connect to that just fine with MUSHclient in Win7 64bit.
#6
Hmm. Okay, so connecting by IP number rather than name works. The name resolves correctly, but... I still should have tried that. It still seems odd to me, but that'll work.

Thank you for the replies.
Australia Forum Administrator #7
I connected OK too with Windows 7, assuming I was supposed to see this:


Welcome!
0 players on right now.  Log on and become another one!

The help file is missing, the management has been notified.


However I have to say that waiting for Windows 7 to do something is incredibly boring. I thought it was supposed to be faster than Vista?