Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Bug reports
➜ Problems Connecting to Achaea
|
Problems Connecting to Achaea
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
Pages: 1
2
| Posted by
| Twisol
USA (2,257 posts) Bio
|
| Date
| Reply #15 on Sun 11 Jul 2010 02:49 AM (UTC) |
| Message
| | Rather interesting that it's saying WONT at all; I'd expect it to either say WILL and wait for a response, or not say anything at all. Wonder what's up with that. |
'Soludra' on Achaea
Blog: http://jonathan.com/
GitHub: http://github.com/Twisol | | Top |
|
| Posted by
| Nick Gammon
Australia (23,162 posts) Bio
Forum Administrator |
| Date
| Reply #16 on Sun 11 Jul 2010 03:15 AM (UTC) Amended on Tue 07 Apr 2015 01:37 AM (UTC) by Nick Gammon
|
| Message
| According to:
www.mudstandards.org/forum/viewtopic.php?f=7&t=107
[EDIT] (April 2015) Warning: Domain name mudstandards.org has been abandoned. That site is now an adult products shop.
Normal Telnet Option negotiation protocol is used with a telnet option number of 201 (un-registered).
Server sends:
IAC WILL 201
Client responds with
IAC DO 201
if it supports ATCP2
There isn't anything there about the server sending WONT 201. The first couple of packets might clear that up (and perhaps Twisol see what happens to your first few packets).
Possibly this happened:
Server: IAC WILL 201 (in packet 1)
Client: IAC DONT 201
Server: IAC WONT 201
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Twisol
USA (2,257 posts) Bio
|
| Date
| Reply #17 on Sun 11 Jul 2010 03:18 AM (UTC) |
| Message
| Aaah, that's an excellent point. MUSHclient sends a WONT when no plugin returns true on an OnPluginTelnetRequest, doesn't it? So that's probably not the problem here...
The first packet was probably Achaea sending the title screen and options, and the second packet was likely MUSHclient replying to the option requests. |
'Soludra' on Achaea
Blog: http://jonathan.com/
GitHub: http://github.com/Twisol | | Top |
|
| Posted by
| Nick Gammon
Australia (23,162 posts) Bio
Forum Administrator |
| Date
| Reply #18 on Sun 11 Jul 2010 11:10 PM (UTC) |
| Message
| Strictly speaking I don't think we should be getting a WONT from Achaea.
Assuming in packet 1 they sent:
Server: IAC WILL 201 (do you want to use ATCP2?)
And then we respond:
Client: IAC DONT 201 (no thanks)
That should be the end of the negotiation. For them to then reply (to the DONT):
Server: IAC WONT 201 (I won't use 201)
... is getting into a negotiation loop. It's like they think they are being told to not use 201 (and are replying "OK I won't do that") but *they* started the negotation, not us.
The loop goes like this, translated into normal English:
Server: Do you want to use 201?
Client: No don't use 201
Server: Ah you don't want me to use 201? I won't then.
Client: Don't use 201? Ok then.
Server: Ah, 201 is out is it? OK I won't use it.
Client: So we aren't using 201 today? I won't use it then.
Server: I notice you don't want me to use 201. I wont then.
Client: OK, me neither.
Server: Nor me.
Client: I won't be using it.
...
And so on for thousands of lines.
So basically the server should remember it started the negotiation, and not keep replying to the reply. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Roam
(6 posts) Bio
|
| Date
| Reply #19 on Mon 12 Jul 2010 06:53 AM (UTC) |
| Message
| Just popping in to see what's happening. Started playing midkemia a bit to while the time. (might be relevant; my character in Midkemia is named Roam as well, and has no issues.)
You guys mind translating a bit of what is or might be going on in laymans terms? I have a basic understanding of lua and mush (enough that I can code a system and plugins ect...) but you guys lost me somewhere around the wonts and iac's.
Also, anything I can do or post to help out lemme know. Seems like this may have to do with achaea's playing around with atcp, and I'd assume it would eventually effect others as well.
Off topic. Viva Espana!!! World Cup! | | Top |
|
| Posted by
| Twisol
USA (2,257 posts) Bio
|
| Date
| Reply #20 on Mon 12 Jul 2010 07:09 AM (UTC) Amended on Mon 12 Jul 2010 07:13 AM (UTC) by Twisol
|
| Message
| It was more or less just a lot of figuring out what could be going on. You might want to pay attention to this post though:
Nick Gammon said:
The fact that you cannot connect, even with a new world file, strongly indicates to me that there is something about the configuration of Roam on Achaea. Using another client (like the Nexus client) I would check all your Roam character options (and change his password while you are at it). There must be some ATCP / MXP / MCCP or other configuration option that is turned on, that is confusing the client. Or maybe the server is just waiting on some response it is not getting.
Specifically, try toggling CONFIG MXP to ON or OFF in Achaea, then try connecting with MUSHclient again. Also try disabling compression in MUSHclient in Game -> Configure -> Output. I'm 99% certain Nexus doesn't use compression (or it didn't last time I watched it with Wireshark), so that's a potential (but still unlikely) cause.
Also, I know you've reformatted and everything, but try connecting from another computer. I'm shooting in the dark, unfortunately.
Roam said:
Seems like this may have to do with achaea's playing around with atcp, and I'd assume it would eventually effect others as well.
Maybe, but you would think that it would affect every character. Not only that, but Achaea isn't even sending you ATCP (that's what the IAC WONT ATCP thing is all about). So that's probably not it... |
'Soludra' on Achaea
Blog: http://jonathan.com/
GitHub: http://github.com/Twisol | | Top |
|
| Posted by
| Nick Gammon
Australia (23,162 posts) Bio
Forum Administrator |
| Date
| Reply #21 on Mon 12 Jul 2010 07:54 AM (UTC) |
| Message
| The short answer is that since you can connect to all your other characters, and it fails even on a new world file, that there isn't really something major wrong with MUSHclient, but more likely some way your character Roam is configured on Achaea.
Twisol plays on Achaea with MUSHclient, and he hasn't noticed it either. Plus, around 1,000 downloads a week are made of MUSHclient and I haven't heard of this problem before.
If you can't resolve it I would contact the Achaea admins, and state that this particular character seems to hang after connecting, and can they look into it for you?
I seem to recall a bug report a while back that under Windows XP (from memory) MUSHclient may exhibit similar symptoms, unless you run it with Admin privileges. However again, if this was a daily occurrence I would be hearing about it much more often. Plus, you can connect to your other characters, so this probably isn't it.
It seems more likely to me that since only one character (of yours) on Achaea is having this problem, it is an issue at their end rather than the client end. And remember Achaea are playing around with enhancing their server with ATCP2 code. Conceivably some combination of flags for a character might confuse their server output routines. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
60,057 views.
This is page 2, subject is 2 pages long: ![[Previous page]](/images/thin_prev.gif)
1
2
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top