LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Password
Ubuntu This forum is for the discussion of Ubuntu Linux.

Notices


Reply
  Search this Thread
Old 07-19-2007, 11:27 PM   #1
sulekha
Member
 
Registered: Dec 2004
Location: India
Distribution: ubuntu 10.04 , centos 5.5 , Debian lenny, Freenas
Posts: 324

Rep: Reputation: 36
Question talk command


Hi all,

I am trying to run the talk command. i am getting the following results:

1)[No connection yet]
2)error from talk read daemon:connection refused. press
any key

then i googled for any possible solution and i found this thread.

http://ubuntuforums.org/showthread.p...33#post1398433

i was reading the step:
1. Paste the following lines into '/etc/xinetd.d/talk'

but in my dapper 6.06.1 machine when i tried
cat: /etc/xinetd.d/talk, i am getting the message
No such file or directory

in my /etc directory there is no directory named xinetd.d
 
Old 07-20-2007, 05:26 PM   #2
wjevans_7d1@yahoo.co
Member
 
Registered: Jun 2006
Location: Mariposa
Distribution: Slackware 9.1
Posts: 938

Rep: Reputation: 31
In your /etc directory, is there a file called inetd.conf? If so, then do this:

Code:
grep talk /etc/inetd.conf
You probably need to uncomment those lines; that is, edit the file so that the initial "#" is removed from each line.

If those lines already don't start with "#", then come back here and post those lines.

Hope this helps.
 
Old 07-20-2007, 11:39 PM   #3
sulekha
Member
 
Registered: Dec 2004
Location: India
Distribution: ubuntu 10.04 , centos 5.5 , Debian lenny, Freenas
Posts: 324

Original Poster
Rep: Reputation: 36
Question

Quote:
Originally Posted by wjevans_7d1@yahoo.co
In your /etc directory, is there a file called inetd.conf? If so, then do this:

Code:
grep talk /etc/inetd.conf
You probably need to uncomment those lines; that is, edit the file so that the initial "#" is removed from each line.

If those lines already don't start with "#", then come back here and post those lines.

Hope this helps.
I tried what you said.

the command grep talk /etc/inetd.conf
gave me the following results:-

talk dgram udp wait nobody.tty /usr/sbin/in.talkd in.talkd

ntalk dgram udp wait nobody.tty /usr/sbin/in.ntalkd in.ntalkd

there is no line that starts with #
in fact the whole contents of the file are as follows

talk dgram udp wait nobody.tty /usr/sbin/in.talkd in.talkd
ntalk dgram udp wait nobody.tty /usr/sbin/in.ntalkd in.ntalkd
finger stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/in.fingerd
 
Old 07-21-2007, 06:21 AM   #4
wjevans_7d1@yahoo.co
Member
 
Registered: Jun 2006
Location: Mariposa
Distribution: Slackware 9.1
Posts: 938

Rep: Reputation: 31
Your /etc/inetd.conf seems very, very stripped down if there are only three lines in it, and no comment lines. I'm curious as to whether this is a clean install of your distribution.

Could you please post the content of /etc/hosts.allow and /etc/hosts.deny?

Last edited by wjevans_7d1@yahoo.co; 07-21-2007 at 06:27 AM.
 
Old 07-21-2007, 09:53 AM   #5
sulekha
Member
 
Registered: Dec 2004
Location: India
Distribution: ubuntu 10.04 , centos 5.5 , Debian lenny, Freenas
Posts: 324

Original Poster
Rep: Reputation: 36
Question

Quote:
Originally Posted by wjevans_7d1@yahoo.co
Your /etc/inetd.conf seems very, very stripped down if there are only three lines in it, and no comment lines. I'm curious as to whether this is a clean install of your distribution.

Could you please post the content of /etc/hosts.allow and /etc/hosts.deny?

Here are the contents of /etc/hosts.allow

# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper, as well as for
# rpc.mountd (the NFS mount daemon). See portmap(8), rpc.mountd(8) and
# /usr/share/doc/portmap/portmapper.txt.gz for further information.
#

here are the contents of /etc/hosts.deny

# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/portmap/portmapper.txt.gz for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address.

# You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
# ALL: PARANOID
 
Old 07-22-2007, 01:08 AM   #6
wjevans_7d1@yahoo.co
Member
 
Registered: Jun 2006
Location: Mariposa
Distribution: Slackware 9.1
Posts: 938

Rep: Reputation: 31
Try adding one of the following lines (or the appropriate variation thereof) to the end of /etc/hosts.allow.

Code:
in.talkd: localhost
in.talkd: 10.0.0
in.talkd: 192.168.1
Repeat for in.ntalkd and in.fingerd if you wish.

Do this for each affected machine.

Then reboot and see if it makes a difference.
 
Old 07-22-2007, 10:25 AM   #7
sulekha
Member
 
Registered: Dec 2004
Location: India
Distribution: ubuntu 10.04 , centos 5.5 , Debian lenny, Freenas
Posts: 324

Original Poster
Rep: Reputation: 36
Question

Quote:
Originally Posted by wjevans_7d1@yahoo.co
Try adding one of the following lines (or the appropriate variation thereof) to the end of /etc/hosts.allow.

Code:
in.talkd: localhost
in.talkd: 10.0.0
in.talkd: 192.168.1
Repeat for in.ntalkd and in.fingerd if you wish.

Do this for each affected machine.

Then reboot and see if it makes a difference.

Then reboot and see if it makes a difference.[/QUOTE]

I tried all what you have said but still no result.
BTW what does the above steps signify????
note : i didn't try for in.ntalkd and in.fingerd

what you have said earlier may be true I doubt if this is a clean installation. I actually installed breezy then upgraded to dapper via internet
 
Old 07-23-2007, 06:14 AM   #8
wjevans_7d1@yahoo.co
Member
 
Registered: Jun 2006
Location: Mariposa
Distribution: Slackware 9.1
Posts: 938

Rep: Reputation: 31
Quoth sulekha:
Quote:
i didn't try for in.ntalkd and in.fingerd
Since nothing else is working, try all this for at least in.ntalkd.

Otherwise, I'm at a loss.

For more information on files /etc/hosts.allow and /etc/hosts.deny, google for this (including the quotation marks):

Code:
"hosts.allow"

Last edited by wjevans_7d1@yahoo.co; 07-23-2007 at 06:18 AM.
 
Old 07-24-2007, 11:32 AM   #9
sulekha
Member
 
Registered: Dec 2004
Location: India
Distribution: ubuntu 10.04 , centos 5.5 , Debian lenny, Freenas
Posts: 324

Original Poster
Rep: Reputation: 36
Question

Quote:
Originally Posted by sulekha
Then reboot and see if it makes a difference.
I tried all what you have said but still no result.
BTW what does the above steps signify????
note : i didn't try for in.ntalkd and in.fingerd

what you have said earlier may be true I doubt if this is a clean installation. I actually installed breezy then upgraded to dapper via internet[/QUOTE]


There is no result yet again. it is as if telling back to square one.

well this is what i tried after editing /etc/hosts.allow

i brought up 2 terminals and tried

celsius@ubuntu:~$ who
celsius :0 2007-07-24 21:50
celsius pts/0 2007-07-24 21:50 (:0.0)
celsius pts/1 2007-07-24 21:51 (:0.0)
celsius@ubuntu:~$ tty
/dev/pts/1
celsius@ubuntu:~$ talk celsius pts/1
celsius@ubuntu:~$

[No connection yet]
[Error on read from talk daemon: connection refused.Press any key...]

[Checking for invitation on caller's machine]

with mouse cursor blinking
___________________________________________________

and when i press any key

it is back to the terminal
 
Old 07-25-2007, 07:25 AM   #10
wjevans_7d1@yahoo.co
Member
 
Registered: Jun 2006
Location: Mariposa
Distribution: Slackware 9.1
Posts: 938

Rep: Reputation: 31
I'm at a loss here. I've used "talk" before, with no problem.

If I were in your position, I might try a clean installation.

Maybe someone else can jump in and help.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Talk command doesn't work! zahadumy Linux - Software 2 05-22-2005 01:22 PM
talk talk daemon configuration ananthkrk Red Hat 1 10-16-2004 11:45 AM
talk command not working Longinus Linux - Newbie 6 07-12-2004 04:28 PM
network talk command JPawlak Linux - Newbie 2 02-16-2004 11:21 AM
talk command indy317 Linux - General 1 04-23-2003 06:04 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu

All times are GMT -5. The time now is 01:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration