You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Ram C <ra...@mybc.com> on 2001/03/26 18:35:17 UTC
RemoteManager problems(was RE:logging on)
I did some investigation based on problem reported by a JAMES user (i
think Grant Peters) regarding having problems loggin on to the remote
manager even if all his configuration is correct.
A few changes can be done to the RemoteManagerHandler to fix these problems.
1) RemoteManagerHandler is using println() to output the response to
the client(Telnet). If JAMES is running in *UNIX, and the RemoteManager
client(Telnet) runs on a Windows* platform, there is a problem with linefeed/carriage
return. (/n vs /r/n).
Solution:
I have changed RemoteMangerHandler to use print() & flush(), and the
response message now includes "/r/n".
2) Certain Telnet clients (Token, PuTTY to name a few) are sending some
wierd characters("�" followed by 2 other characters - several sets of
these 3 characters repeated) at the begining of the session.
Workaround (based on testing with PuTTY):
Try logging in to remote manager using either Token or PuTTY telnet client.
You should see the message "Login failed for root". Keep trying the same
login for 4 times. The fifth time the login will be successfull and you
will be able to use the remote manager without any problems from then
on.
Solution: (based on testing with PuTTY)
(beware....ugly ugly hack)
I just added the few lines after reading the login id and this seems
to fix the problem. This change should not impact the other Telnet clients.(the
only thing is you cannot have your admin acount starting with "�")
String login = in.readLine();
while ( login.startsWith("�") ) {
login = login.substring(3);
}
I know this is not a very eligent way, but will work till we move away
from the Telnet remote manager.
PS: I don't understand the internals of the Telnet protocol.(i have heard
its an ugly monster). It will be nice if someone who understands Telnet
protocol better can validate that these fixes would work for all Telnet
clients(and not breaking any).
If the core JAMES developers are happy with these fixes can you guys
commit this change for me.
Cheers,
Ram.
___________________________________________________________
FREE voicemail, email and fax, all in one place. Sign Up Now! http://www.mybc.com
RE: RemoteManager problems(was RE:logging on)
Posted by Danny Angus <da...@thought.co.uk>.
I've just had a similar experience to the one you mention, with a twist,
James running on NT (sun's JDK) wont let me login using putty
(localhost:4555).
Putty makes a connection & accepts the input, \r\n displays correctly , but
I get rejected, I guess because when I hit return my p/w ends - \r\n ?
NT telnet wont display anything.
d
> At 08:35 26/3/01 -0800, Ram C wrote:
> >I did some investigation based on problem reported by a JAMES user (i
> >think Grant Peters) regarding having problems loggin on to the remote
> >manager even if all his configuration is correct.
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
RE: RemoteManager problems(was RE:logging on)
Posted by Danny Angus <da...@thought.co.uk>.
I've just had a similar experience to the one you mention, with a twist,
James running on NT (sun's JDK) wont let me login using putty
(localhost:4555).
Putty makes a connection & accepts the input, \r\n displays correctly , but
I get rejected, I guess because when I hit return my p/w ends - \r\n ?
NT telnet wont display anything.
d
> At 08:35 26/3/01 -0800, Ram C wrote:
> >I did some investigation based on problem reported by a JAMES user (i
> >think Grant Peters) regarding having problems loggin on to the remote
> >manager even if all his configuration is correct.
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
RE: RemoteManager problems(was RE:logging on)
Posted by Danny Angus <da...@thought.co.uk>.
I've just had a similar experience to the one you mention, with a twist,
James running on NT (sun's JDK) wont let me login using putty
(localhost:4555).
Putty makes a connection & accepts the input, \r\n displays correctly , but
I get rejected, I guess because when I hit return my p/w ends - \r\n ?
NT telnet wont display anything.
d
> At 08:35 26/3/01 -0800, Ram C wrote:
> >I did some investigation based on problem reported by a JAMES user (i
> >think Grant Peters) regarding having problems loggin on to the remote
> >manager even if all his configuration is correct.
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re: RemoteManager problems(was RE:logging on)
Posted by Peter Donald <do...@apache.org>.
At 08:35 26/3/01 -0800, Ram C wrote:
>I did some investigation based on problem reported by a JAMES user (i
>think Grant Peters) regarding having problems loggin on to the remote
>manager even if all his configuration is correct.
>
>A few changes can be done to the RemoteManagerHandler to fix these problems.
>
>1) RemoteManagerHandler is using println() to output the response to
>the client(Telnet). If JAMES is running in *UNIX, and the RemoteManager
>client(Telnet) runs on a Windows* platform, there is a problem with
linefeed/carriage
>return. (/n vs /r/n).
>
>Solution:
>I have changed RemoteMangerHandler to use print() & flush(), and the
>response message now includes "/r/n".
At one stage I was going to adapt telnetd (from sourceforge) to use in
Avalon which fixes a lot of these issues. (You may want to have a look at it).
>2) Certain Telnet clients (Token, PuTTY to name a few) are sending some
>wierd characters("�" followed by 2 other characters - several sets of
>these 3 characters repeated) at the begining of the session.
Yep that would be the control characters. Attached is a basic
implementation of null telnet protocl streams. If you could integrate them
then that would be the "proper" fix.