| View previous topic :: View next topic |
| Author |
Message |
weezel
Voice
Joined: 07 Oct 2010
Posts: 3
|
 Posted: Wed Nov 03, 2010 8:01 pm Post subject: Connection Refused (login details are correct) |
 |
|
hey!
so my problem is this. I have (Eggdrop v1.6.20 (C) 1997 Robey Pointer (C) 2010 Eggheads) running, with a few scripts. When i try to log in via putty, i get the following error:
| Code: | BusBot (Eggdrop v1.6.20 (C) 1997 Robey Pointer (C) 2010 Eggheads)
Please enter your nickname.
weezel
You don't have access.
|
however: if i change "Answerback to ^E:" under "terminal" in the putty settings for that stored account so that its blank, it WILL let me log in but the login then looks like this :
Now, that looks horrible. And i've no idea why it's doing that either. But! when i leave it logged in, and then try to login again, this time using putty it its rather default state, again i will see the above error on the new window, but in the window that's already logged in (the messy one), i see this:
| Code: |
[23:54:18] Timeout/EOF ident connection
[23:54:42] Refused telnet@weezel (invalid handle: PuTTYweez) |
it's worth noting that the thing in the settings dialogue "Answerback to ^E:" is "PuTTY"
what i cant figure out, is why this is happening. all i want is for the terminal window to look clean! im sure that i've not changed anything to disallow logins as it tells me, but i cant see what effect "Answerback to ^E:" has, and if it's causing that horribly messy terminal window.
Any ideas ? :E |
|
| Back to top |
|
 |
pseudo
Halfop
Joined: 23 Nov 2009
Posts: 88
Location: Bulgaria
|
| Posted: Thu Nov 04, 2010 3:03 am Post subject: |
|
|
What PuTTY sees as ^E is part of the telnet autodetection added in 1.6.20. Clients speaking telnet will have no problems with it. What you are doing wrong is using the Raw connection type instead of Telnet. Why?
To be able to work normally with the raw type, you must remove the ^E answerback, leaving the field empty. After that you need to type .fixcodes when you log in. The easier and preferred solution, however is to choose Telnet in the initial connection dialog, cause it's actually telnet what you are supposed to use with Eggdrop. That way you won't have problems. |
|
| Back to top |
|
|
weezel
Voice
Joined: 07 Oct 2010
Posts: 3
|
| Posted: Thu Nov 04, 2010 12:01 pm Post subject: |
|
|
| pseudo wrote: | What PuTTY sees as ^E is part of the telnet autodetection added in 1.6.20. Clients speaking telnet will have no problems with it. What you are doing wrong is using the Raw connection type instead of Telnet. Why?
To be able to work normally with the raw type, you must remove the ^E answerback, leaving the field empty. After that you need to type .fixcodes when you log in. The easier and preferred solution, however is to choose Telnet in the initial connection dialog, cause it's actually telnet what you are supposed to use with Eggdrop. That way you won't have problems. |
to be honest, i am not sure why i am using RAW there. i think (im sure) i always used that, not for any particular reason, but just because that's what was recommended. true enough before the version i have now, i did use an older one so i guess that's where my methods became outdated 
just tried using the method you suggested, now working fine! thankyou for your help  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
