NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/unix/ultrix/6912

Internet Message Format | 1992-09-15 | 1.9 KB

Xref: sparky comp.unix.ultrix:6912 comp.sys.dec:4994
Path: sparky!uunet!news.claremont.edu!ucivax!news.service.uci.edu!draco.acs.uci.edu!iglesias
From: [e-mail] (Mike Iglesias)
Subject: Re: talk: how to fix - "[Checking for invitation...]"?
Nntp-Posting-Host: draco.acs.uci.edu
Message-ID: <[e-mail]>
Newsgroups: comp.unix.ultrix,comp.sys.dec
Organization: University of California, Irvine
Lines: 28
Date: 15 Sep 92 14:50:42 GMT
References: <[e-mail]>

In article <[e-mail]> [e-mail] (Karl A. Nyberg) writes:
>I have several vaxes running Ultrix (4.0 & 4.2) that can talk together
>just fine between themselves.  However they can't talk to other machines
>on the network (locally a Sun4, or remotely also a Sun4, I think).  I get
>the "[Checking for invitation...]" message when running talk.  When running
>"otalk", the second machine will get a message from the Talk_Daemon requesting
>a connection, but the talk itself will fail with:
>
>Unable to connect with initiator :
>    Address family not supported by protocol family (47)]
>
>How do I fix that?  (I'm presuming it's a problem on the VAX/Ultrix side,
>since the Suns will gladly talk between themselves).

Sun, in their infinite wisdom, still distributes the old talk software on
their systems.  That talk does not work correctly when the two systems
trying to talk have different byte orders.  The talk on Ultrix uses the
newer protocol that deals with this situation correctly.

Your best bet is to get a copy of the 4.3bsd talk/talkd and run it on your
Suns, and complain to Sun that they need to move to the newer release
of talk.


Mike Iglesias                        Internet:    [e-mail]
University of California, Irvine     BITNET:      iglesias@uci
Office of Academic Computing         uucp:        ...!ucbvax!ucivax!iglesias
Distributed Computing Support        phone:       [phone]