talk program error: couldn't bind to control socket

talk program error: couldn't bind to control socket

Post by Norm Walk » Wed, 10 Aug 1994 14:34:12



can someone tell me what this error is really trying to say
or better what I am doing wrong?
I get the error message
Couldn't bind to control socket: cannot assign requested address (99)
the talk program works when I am running my ppp connection but
will not run when I am only running locally.
all I was trying to do is talk to another user on my own system.
--
Merritt Secondary School - Computer Support Teacher

 
 
 

talk program error: couldn't bind to control socket

Post by Gary Mort » Fri, 12 Aug 1994 08:05:54



>can someone tell me what this error is really trying to say
>or better what I am doing wrong?
>I get the error message
>Couldn't bind to control socket: cannot assign requested address (99)
>the talk program works when I am running my ppp connection but
>will not run when I am only running locally.
>all I was trying to do is talk to another user on my own system.
>--
>Merritt Secondary School - Computer Support Teacher

Aha, I have had exactly the same problem and error message. I have just
managed to get it fixed tonight.

You are (probably) not running a talk daemon. On my Trans-Ameritech CD-ROM
(Slackware 1.2) I couldn't find 'talkd', however I did locate some sources
for talkd. I compiled them and ended up with a 'ntalkd' executable. After
running this (as root) I was able to use talk, although for some reason
'ntalkd' then terminated itself (?). I have now installed 'ntalkd' in
rc.inet2 and wait to see how well it runs when I next reboot.

If you need the sources or binaries, let me know I can email you a copy.

Cheers...

-- Gary
--
*******************
* tacky signature *
*******************

 
 
 

1. Q: talk error--[Couldn't bind to control socket : Cannot assign requested address (99)]

I am using Slackware 2.2 with linux kernel 1.2.8 and whenever I try to intiate
a talk session with anyone (even myself), or reply to someones talk request I
get the following error message:

        [Couldn't bind to control socket : Cannot assign requested address (99)]

When I try to do the same thing using ytalk I get the following message:

                 ##############################################
                 #                Ytalk Error                 #
                 #                                            #
                 #  No talk daemon on planitia.cybercom.net   #
                 #         No such file or directory          #
                 ##############################################

I am pretty sure that everything is set up correctly in /etc/services and
/etc/inetd.conf since I have compared them to several working systems and found
nothing to be different. Any help on this error would be greatly appreciated.

Thank you.


2. OS/2 and failure

3. talk - says: Couldn't bind to control socket

4. ip mask .0 vs .252

5. talk client fails: "Couldn't bind to control socket"

6. ttyS1 is not a terminal device

7. DIP and Talk error message "Can't Bind control socket"

8. linux-firewall-tools.com question

9. Talk cant bind to control socket

10. Talk: Cannot bind to control socket

11. talk can't bind socket

12. network programing : How to program in 'logical link control (LLC)' level?

13. Unix : Bind error's when program dies