From: Kenny McCormack on 8 Jul 2010 08:58 I put in my /etc/hosts file: 192.168.99.99 myhost Then I do: ping myhost and it works. But when I do: telnet myhost it says: myhost: No address associated with nodename Why? How to fix? Tested repeatedly over the course of about 10 minutes (because I know there is some latency in OSX where if you edit the Unix-y configuration files, the OS doesn't always pick up on it right away). In all tests, the ping worked but the telnet did not. Note: telnetting directly to 192.168.99.99 works fine. -- > No, I haven't, that's why I'm asking questions. If you won't help me, > why don't you just go find your lost manhood elsewhere. CLC in a nutshell.
From: David Schwartz on 8 Jul 2010 16:49 On Jul 8, 5:58 am, gaze...(a)shell.xmission.com (Kenny McCormack) wrote: > I put in my /etc/hosts file: > > 192.168.99.99 myhost > > Then I do: ping myhost > and it works. But when I do: telnet myhost > it says: myhost: No address associated with nodename > > Why? How to fix? > > Tested repeatedly over the course of about 10 minutes (because I know > there is some latency in OSX where if you edit the Unix-y configuration > files, the OS doesn't always pick up on it right away). In all tests, > the ping worked but the telnet did not. http://osxfaq.com/man/5/resolv.conf.ws DS
From: Kenny McCormack on 9 Jul 2010 08:57 In article <433043da-255f-4890-9ecb-a5a6d4bcbb27(a)t13g2000prf.googlegroups.com>, David Schwartz <davids(a)webmaster.com> wrote: .... >http://osxfaq.com/man/5/resolv.conf.ws has nothing to do with my question. Thanks. -- > No, I haven't, that's why I'm asking questions. If you won't help me, > why don't you just go find your lost manhood elsewhere. CLC in a nutshell.
From: Rick Jones on 9 Jul 2010 17:29 David Schwartz <davids(a)webmaster.com> wrote: > On Jul 8, 5:58?am, gaze...(a)shell.xmission.com (Kenny McCormack) wrote: > > I put in my /etc/hosts file: > > > > 192.168.99.99 ? myhost Interesting that the '?' appeared when David was quoting Kenny's post. Makes me wonder if there are some "strange" characters in the /etc/hosts file. Carefully retyping the line might be a worthwhile experiment. > > Then I do: ping myhost > > and it works. ?But when I do: telnet myhost > > it says: myhost: No address associated with nodename Nodename? I would have expected to get "hostname" out of a telnet error message. Or perhaps "Unknown host" In HP-UX land at least a "nodename" is associated with UUCP not TCP/IP. To verify that telnet and ping are, or are not, following the same name resolution order you might try taking a system call trace of each. rick jones -- the road to hell is paved with business decisions... these opinions are mine, all mine; HP might not want them anyway... :) feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
From: Ian Collins on 9 Jul 2010 18:55
On 07/ 9/10 12:58 AM, Kenny McCormack wrote: > I put in my /etc/hosts file: > > 192.168.99.99 myhost > > Then I do: ping myhost > and it works. But when I do: telnet myhost > it says: myhost: No address associated with nodename Do other services work OK, for example nslookup? Are your name service files correct? -- Ian Collins |