poppassd port read-only from windows???

Thread View: comp.os.linux.networking

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Donovan Baarda Mon, 05 May 1997 00:00

#101

Author: Donovan Baarda
Date: Mon, 05 May 1997 00:00

46 lines
2656 bytes


G'day all,

I've got a wierd problem with poppassd from windows machines. I'm running
Debian 1.2 with the poppassd .deb installed.

When I try and change passwords using Eudora, it times out with error
messages. So I tried telnet to port 106 (used by poppassd according to
/etc/services and /etc/inetd.conf), and I got different things depending
on what OS I was running.

I always "see" the poppassd prompt come up, and from a linux machine, I 
can type responces and see what I type echoed back. But from windows,
anything I type seems to go nowhere. It's like windows treats port 106 on
my linux machine as read-only. There is also a subtle difference between
the poppassd prompt from windows and from linux. It appears that windows
sucks up or misses the first character sent.

From linux, I get;
200 minkirri poppassd v1.2 hello, who are you?

From windows, I get;
00 minkirri poppassd v1.2 hello, who are you?

When using linux, I have tried from localhost, and from another machine
over ethernet. Both worked fine.

When using windows, I've tried from a dialup connection, and over
ethernet (the same machine and IP address as used for linux ethernet 
test). Neither worked, and both showed the same symptoms.

I've been using teraterm and win3.11 with TCP32B stack over ethernet for
the win-ethernet test, and win3.11 with Trumpet for the dialup-win test.
Everything else works fine for any of the configurations tried, only
poppassd from windows is broken.

I can't understand why port 106 would be "read-only" from a machine 
running windows, and yet work fine from the same machine (and ip address) 
running linux. I didn't think you could even make a port "read-only". At
first I thought it might be the TCP32 stack that was the culprit, but the
behavior is the same using Trumpet.

Any clues anyone?

ABO

Re: poppassd port read-only from windows???

#102

Author: Donovan Baarda
Date: Wed, 07 May 1997 00:00

35 lines
2573 bytes

On Tue, 6 May 1997 bofh@snoopy.virtual.net.au wrote:

> >I've got a wierd problem with poppassd from windows machines. I'm running
> >Debian 1.2 with the poppassd .deb installed.
> 
> >When I try and change passwords using Eudora, it times out with error
> >messages. So I tried telnet to port 106 (used by poppassd according to
> >/etc/services and /etc/inetd.conf), and I got different things depending
> >on what OS I was running.
> 
> >I always "see" the poppassd prompt come up, and from a linux machine, I 
> >can type responces and see what I type echoed back. But from windows,
> >anything I type seems to go nowhere. It's like windows treats port 106 on
> 
>    Check the local echo settings of the telnet client software to get it to
> display what you type.  You may have to explicitely enable local echo on
> the Windows telnet program.
> 
local echo in the telnet client is not the problem. When telneting from
linux, I have local echo disabled, and the poppassd at the other end does
the echo for me. Under windows, I have the same setup, but nothing echoes
back, because poppassd is not getting anything. 

I know poppassd is not getting anything, because under linux, if I type an
invalid responce and hit enter, poppassd sends back a message about
"invalid responce, username expected" and terminates the connection. 

Under windows, I can type crap all day and nothing happens. If local echo
was turned off, typed characters should still get through, right? When I
do a "ps -ax" on the poppassd end, I can see the poppassd process hanging
there waiting for a responce. This is consistant with Eudora timing out
waiting for a responce.

ABO

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads