Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bywater!scifi!watson!arnor!arnor!marc From: marc@watson.ibm.com (Marc Auslander) Newsgroups: comp.unix.aix Subject: Re: rs6000 Hostname problem Message-ID: Date: 10 Apr 91 13:07:35 GMT References: <1320@anaxagoras.ils.nwu.edu> Sender: news@watson.ibm.com (NNTP News Poster) Organization: IBM T.J. Watson Research Center, Hawthorne, New York Lines: 22 In-Reply-To: edelson@ils.nwu.edu's message of 9 Apr 91 19:04:30 GMT Nntp-Posting-Host: marc In article <1320@anaxagoras.ils.nwu.edu> edelson@ils.nwu.edu (Daniel Choy Edelson) writes: >I have a problem with an rs6000 that previously had a different >name. Even though we have reset the hostname (within smit), and the >hostname command returns the new name... >When I rlogin or rsh to another host, it tells the other host the >old name. Thus, to get appropriate permissions, I have to put the >old name in the remote machine's .rhost and hosts.equiv files. >Does anyone know why the machine is still broadcasting the >old name? (The old name has been removed from /etc/hosts, also). It doesn't work that way. The "other" machine gets what it thinks is the host name by looking up your machine's ip address in the "other" machine's /etc/hosts or asking the nameserver, if you are using one. So either the nameserver or the "other" machine's /etc/hosts file is the culprit. -- Marc Auslander