Re: Problems with Talk under Debian

1996-12-27 Thread Guy Maor
Gerry Jensen [EMAIL PROTECTED] writes:

 I had trouble with this too.  I believe one problem is that the host name
 of your machine must match the IP address of your machine.

That's exactly right.

 And lastly, Sun's talk seems to be incompatible with just about every
 other OS's talk that I've tried, including Linux.

Unless you use ytalk.  ytalk can communicate with both kinds of talk
daemons.  Unfortunately there is no ytalkd, a talk daemon which could
communicate with both kinds of clients.


Guy


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: Problems with Talk under Debian

1996-12-27 Thread Gerry Jensen
On 26 Dec 1996, Guy Maor wrote:

 Gerry Jensen [EMAIL PROTECTED] writes:
 
  And lastly, Sun's talk seems to be incompatible with just about every
  other OS's talk that I've tried, including Linux.
 
 Unless you use ytalk.  ytalk can communicate with both kinds of talk
 daemons.  Unfortunately there is no ytalkd, a talk daemon which could
 communicate with both kinds of clients.

Even using ytalk on Linux, I am unable to establish a talk connection with
the Suns at my school.

Gerry
[EMAIL PROTECTED]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

From miss
Received: from mongo.pixar.com (138.72.50.60)
  by master.debian.org with SMTP; 27 Dec 1996 23:20:52 -
Received: (qmail 25261 invoked from network); 27 Dec 1996 23:10:24 -
Received: from primer.i-connect.net (HELO master.debian.org) ([EMAIL PROTECTED])
  by mongo.pixar.com with SMTP; 27 Dec 1996 23:10:24 -
Date:   Fri, 27 Dec 1996 17:08:42 -0600 (CST)
Sender: Roy C Bixler [EMAIL PROTECTED]
From:   Roy C Bixler [EMAIL PROTECTED]
To: Nelson Posse Lago [EMAIL PROTECTED]
cc: debian-user@lists.debian.org, Christoph Lameter [EMAIL PROTECTED]
Subject: Re: Poppasswd
In-Reply-To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Resent-Message-ID: GEsUH.0.yP5.pS5no@master.debian.org
Resent-From: debian-user@lists.debian.org
Resent-Reply-To: debian-user@lists.debian.org
X-Mailing-List: debian-user@lists.debian.org archive/latest/2019
X-Loop: debian-user@lists.debian.org
Precedence: list
Priority: non-urgent
Importance: low
Resent-Sender: [EMAIL PROTECTED]

On Wed, 25 Dec 1996, Nelson Posse Lago wrote:
 Hi,
 This is a very tricky problem. poppassd is a small app that calls passwd 
 to change the password. Well, it passes some arguments to passwd and 
 expects some responses from it. All very fine. Now, the newer debians use 
 a passwd program that does a few checks on the password. If the 
 new password is too similar to the old one, or if it is too short, or if 
 it has too many repeated characters, etc. it will issue an error message 
 and prompt you for a new (hopefully better) password. poppassd was not 
 desinged to deal with this. It just waits for passwd to issue the prompt 
 re-enter new password while password is saying too simple: try again.
 Try entering a very random, 8 chars password to see if it works. To solve 
 your problem, you must try to find a passwd program that doesn't do these 
 checks (at the expense of security) or hack poppassd to be smarter. I 
 don't know if debian has a simpler passwd program.

I checked to see if this is the problem by logging into the server
directly and changing my password to the same thing I attempted to change
it to with Eudora and 'poppasswd'.  That worked just fine the first time. 

My configuration is Debian 1.2 stable (poppasswd_1.2-4) and Eudora Pro v.
3.0 flailing away on Windoze '95.  The connection just hangs after I
specify the new password for the second time.  The Eudora dialog box just
sits with a 'newpasswd' text. If I look on the server, there are idle
'poppasswd' and 'passwd rcb' processes running.  Also, as expected, typing
in my original password incorrectly will cause Eudora to abort the
operation.  It really appears as if 'poppasswd' itself is just hanging
after it receives the 'newpass' command - this is what I got if I 'telnet'
direct to port 106 and go through the protocol sequence.

Any ideas?

Roy
[EMAIL PROTECTED]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: Problems with Talk under Debian

1996-12-25 Thread Gerry Jensen
On Sat, 21 Dec 1996, John Goerzen wrote:

 I have been having problems with talk and ytalk under Linux.  Any help would
 be greatly appreciated!

I had trouble with this too.  I believe one problem is that the host name
of your machine must match the IP address of your machine.  Otherwise,
other talk daemons won't talk to you.  If you are given a dynamic IP
address by your ISP, then it almost certainly doesn't match.  So, you must
set the host name of your machine to match the given IP number after you
establish your PPP/SLIP connection.  You can set it with the hostname
command.  I have the following line in /etc/ppp/ip-up to do this for me
automatically whenever I establish a PPP connection: 

  /bin/hostname `/usr/bin/host $4 | head -1 | cut -f 2 -d  `

Also, reverse name lookup must be set up correctly by whomever is in
charge of your domain (probably your ISP).  Otherwise, you will not be
able to initiate a talk connection, although I think you can still reply
if someone else initiates the talk session with you. 

And lastly, Sun's talk seems to be incompatible with just about every
other OS's talk that I've tried, including Linux.  So, if you're trying to
talk to someone on a Sun, you're probably SOL.  It would be nice if
someone would hack the talk that comes with Linux so that it could talk to
Suns as well.  

Gerry
[EMAIL PROTECTED]


--
This message was delayed because the list mail delivery agent was down.


Re: Problems with Talk under Debian

1996-12-25 Thread Jonas Bofjall
On Tue, 24 Dec 1996, Gerry Jensen wrote:

 I had trouble with this too.  I believe one problem is that the host name
 of your machine must match the IP address of your machine.  Otherwise,

thank you for this information! I've had this problem too ;)

 And lastly, Sun's talk seems to be incompatible with just about every
 other OS's talk that I've tried, including Linux.  So, if you're trying to

At least on my schools sun's running SunOS, they've got at least two, but
I think three talk-clients. Maybe you should try some other.. When someone
requests a talk with me when I use my school's sun the talk daemon tells
me which talk-client to use.

  // Jonas [EMAIL PROTECTED] [2:201/262.37]


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Problems with Talk under Debian

1996-12-22 Thread John Goerzen
Hello,

I have been having problems with talk and ytalk under Linux.  Any help would
be greatly appreciated!

Both programs work fine when trying to talk to somebody else on the local
machine.

When trying to use talk or ytalk to talk to somebody on a remote system,
neither program works.

Talk just locks up displaying [Checking for invitation on caller's
machine].  Ytalk complains of  find_daemon: recv() failed Connection
refused and then complains sendit: recv() failed Connection refused.

On IRC #linux, somebody told me that there might be a problem in /etc/hosts,
but did not know what the problem might be.

I am using PPP and have dynamic IP addressing.  My system also is
UUCP-connected, so for the purposes of things like hostname, it is known as
complete.org (the domain name used for news, mail, etc.)  Everything seems
to work OK -- IRC, News, etc.  But not talk.

So I hope that somebody here can help me.  I have tried setting localhost to
127.0.0.0 but that seems to break more things than it fixes.  People have
told me that everything else is supposed to be 127.0.0.0 so I did that.

Here is my /etc/hosts file:

127.0.0.0   complete.orgcomplete
127.0.0.1   localhost

# These below are rarely used.

127.0.0.0   centre.complete.org centre
127.0.0.0   mail.complete.org   mail
127.0.0.0   news.complete.org   news

# Some other irrelevant stuff trimmed.

My /etc/hostname contains the word complete.  This file is fed to the
hostname program at boot time by using hostname --file.

-- 
John Goerzen  | System administrator  owner, The Communications
Custom programming| Centre and Complete Network (complete.org)
[EMAIL PROTECTED] | Free Unix shell access, 316-367-8490 w/ your modem.
-- 
John Goerzen  | System administrator  owner, The Communications
Custom programming| Centre and Complete Network (complete.org)
[EMAIL PROTECTED] | Free Unix shell access, 316-367-8490 w/ your modem.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: Problems with Talk under Debian

1996-12-22 Thread Mr Legendary
On Sat, 21 Dec 1996, John Goerzen wrote:

 Hello,
 
 I have been having problems with talk and ytalk under Linux.  Any help would
 be greatly appreciated!
 
 Both programs work fine when trying to talk to somebody else on the local
 machine.
 
 When trying to use talk or ytalk to talk to somebody on a remote system,
 neither program works.
 
 Talk just locks up displaying [Checking for invitation on caller's
 machine].  Ytalk complains of  find_daemon: recv() failed Connection
 refused and then complains sendit: recv() failed Connection refused.
 
Have a look in /etc/inetd.conf

talk  dgram udp waitroot /usr/sbin/tcpd  /usr/sbin/in.talkd
ntalk dgram udp waitroot /usr/sbin/tcpd  /usr/sbin/in.talkd

Make sure these two lines are uncommented, then kill -HUP inetd (i think
that's it, or just do a ps -aux, get the process number for
/usr/sbin/inetd and do a kill -HUP ##)

Good Luck.

Paul



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: Problems with Talk under Debian

1996-12-22 Thread Boris D. Beletsky
Hi Mr, You wrote:
 Mr  Ytalk complains of  find_daemon: recv() fail Connection refused 
 Mr Have a look in /etc/inetd.conf
 Mr
 Mr talk   dgram udp waitroot /usr/sbin/tcpd  /usr/sbin/in.talkd
 Mr ntalk  dgram udp waitroot /usr/sbin/tcpd  /usr/sbin/in.talkd

Ytalks find_daemon: recv() fail Connection refused mean that
Connection is refused _by_ the daemon. I am having this problem too.

Try to run in.talkd with '-d' option, the daemon will write some
debug info via syslog (should be notice.debug), i.e

---
talk   dgram udp waitroot /usr/sbin/tcpd  /usr/sbin/in.talkd -d
ntalk  dgram udp waitroot /usr/sbin/tcpd  /usr/sbin/in.talkd -d
---

Regards,
Borik

--
Boris D. Beletsky [EMAIL PROTECTED] 
For pgp public key, e-mail me 
with subject get pgp-key
borik

--
Boris D. Beletsky [EMAIL PROTECTED] 
For pgp public key, e-mail me 
with subject get pgp-key


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]