Issues logging in via linux or solaris telnet

[Cone]

I have an issue when using the command-line telnet program in linux or solaris.

I can connect to vitoc, but upon submitting data I get disconnected.

If I simply hit enter it's a straight drop. If I enter a username it'll print out the enter your password message before dropping me.

I get the impression that the telnet protocol may not be fully supported by the initial login screen.

Though if I make a call to configure the connection between my client and the server once I've connected, such as 'set binary', I can then log in normally.

So it seems that there's some garbage being buffered that's getting me dropped which is flushed once a configuration parameter has been set.

Probably not a huge issue as far as the list of issues is concerned but I thought it would be worth mentioning.

[Vitoc]

I had a similar issue when telnetting from my bsd box.? I had to tell telnet to use telnet crlf by typing "toggle crlf" before opening the connection to my server.? Not sure if there's anything I can do on the telnet server end, but if someone knows of a solution I'll implement it.

[Cone]

Essentially your issue, and potentially mine in disguise, is that bsd, linux, and unix telnet clients tend to default to sending {CR}{NUL} rather than {CR}{LF} when terminating a line.

So if you altered whatever piece of code on your telnet server is currently checking for the end of a line and allow CR NUL as a valid end of line it should alleviate the issue.

[Vitoc]

This is fixed.

[Vitoc]

This is fixed.

LIAR!

[yook]

you need to specify 8 bit clean operation.

Code Select Expand

telnet -8 vitoc.com

That should fix your problem. But the servers not up  :'(

[The Crazy Animal]

Fixed or not fixed? that is the question????

[Vitoc]

you need to specify 8 bit clean operation.

Code Select Expand

telnet -8 vitoc.com

That should fix your problem. But the servers not up  :'(

You can also toggle the crlf option in the linux/unix telnet command.  I forget the exact syntax, but that's the name of it.

[The Crazy Animal]

So I'm guessing this is fixed then?

[Vitoc]

So I'm guessing this is fixed then?

I believe we conquered it.  We need like a "fixed, but not tested" category.

[The Crazy Animal]

I think I'd like to move this into the FAQ section since it kinda explains how to do it if you having problems on those OS based clients... Does that sound like a fair idea?

[Vitoc]

I think I'd like to move this into the FAQ section since it kinda explains how to do it if you having problems on those OS based clients... Does that sound like a fair idea?

If it's ok with you I'd like to leave this thread here for the time being because I think it can be fixed serverside (and possibly already has).  I will verify it works from my freebsd box.  If it does, we'll just move this to the fixed section and not bother mentioning it in the FAQ section.

[The Crazy Animal]

sounds like a fine idea...

[Vitoc]

sounds like a fine idea...

I just logged in from my FreeBSD box and had no issues; didn't have to use any command line params or toggle any options.  Going to call this fixed.