home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.admin:5123 comp.unix.admin:4392
- Path: sparky!uunet!sf!raminf
- From: raminf@ms.mdss.pge.com (Fubar)
- Newsgroups: comp.sys.sun.admin,comp.unix.admin
- Subject: SunOS "talk/talkd" problem
- Message-ID: <725@sf.PGE.COM>
- Date: 31 Jul 92 00:06:46 GMT
- Sender: news@sf.PGE.COM
- Followup-To: comp.sys.sun.admin
- Organization: PG&E
- Lines: 30
- Originator: raminf@fubar
-
-
- A Sun SparcStation 1 stopped accepting "talk" requests a few weeks ago.
- The local administrator can not remember changing anything on the system
- (yeah, right!) The machine is running Sun OS 4.1.1. talkd is uncommented
- inside /etc/inetd.conf and there's an entry for talk in /etc/services.
- The machine is a YP and DNS client.
-
- When a user tries to talk to a logged-in user on that machine, the
- message returned by talk is "[Target machine does not recognize us]".
-
- Now the IP and name of both machines is in their corresponding /etc/hosts
- *AND* DNS and YP files and they can telnet/ftp/ping to each other...
-
- I've looked all over for magic files or settings. The in.talkd daemon on the
- target doesn't come up at all when the source machine initiates the "talk"
- session even though inet is supposed to crank one up on demand... Even if I
- start in.talkd by hand, I get this message. Even worse, if I initiate
- a session from a user account *ON THE SAME MACHINE* I get this message as well.
-
- In other words... talk is very confused...
-
- My question is what does this message mean and why should it pop up all of
- a sudden... I've looked hither and yon with no success so far...
-
- Any suggestions would be appreciated... Please Email and I'll summarize back...
-
- Cheers,
- Ramin
- raminf@ms.mdss.pge.com
-
-