Article View: cu.decstation.managers
Article #108Summary: decstation can't ping itself
From: Martin Meadows
Date: Thu, 25 Feb 1999 00:00
Date: Thu, 25 Feb 1999 00:00
62 lines
3206 bytes
3206 bytes
First of all, thanks to the following folks for working with me
to resolve my problem (my apologies to anyone I may have overlooked):
Georg Schwarz <schwarz@physik.tu-berlin.de>
Jacob Rose <jrose@flyingmouse.com>
Philip Tait <pjt@phxase.allied.com>
Mike Thompson <Mzthompson@aol.com>
Pirie Hart <pirie@u.washington.edu>
Jeff Hewitt <jhewitt@lsf.jaycor.com>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I received many helpful suggestions. Here's a summary:
OK, be sure that name's in /etc/hosts with the correct IP.
What is the first few lines in your /etc/rc.local, especially the ifconfig
commands there? What is your IP, netmask and default gateway?
Check you netstat -nr output. Did you change the line in /etc/rc.local that
has the hostname command? Make sure named & routed are turned off.
What do /etc/networks and /etc/resolv.conf contain?
Perhaps you have a "route add ..." command in /etc/rc.local, which is no
longer valid. A comparison of the output of "ifconfig ln0" and "netstat
-nr" might help you trace the problem. ("ln0" may not be correct for
the 2100 - check the "netstat -nr" output to get the correct device
name).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I checked out all the suggestions. I worked with /etc/hosts & the
rc.local file to get things like I thought they should be. In the end,
however, I was best able to resolve my problem by running BINDSETUP.
This system had once been a primary nameserver. It was now a client
of bind only. In BINDSETUP I removed the BIND/Hesiod service from the
system. I then added it back as a client only. I then double-checked
/etc/hosts & rc.local, saw that some slight changes had been made
by BINDSETUP. I made sure I wasn't starting named & routed in rc.local
and I rebooted. This took care of the problem.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For reference, here's the original question:
Hello again,
I've got a decstation 2100 that we just changed the hostname on.
We also changed the ip address on it. It's running ultrix 4.3.
I modified /etc/hosts to make the changes. Now when we boot
the system I can't even ping it. I get
ping: sendto: network is unreachable
Any suggestions?
Thanks,
Martin Meadows
Indianapolis, IN.
Thanks again to everyone who pitched in on this!!!
Technical Details
Message-ID:
<919950141.4676@news.Colorado.EDU>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1065d6,4bd757a07d96f6d4,start X-Google-Attributes: gid1065d6,public From: Martin Meadows <PZXKYS@atdva3.atd.gmeds.com> Subject: Summary: decstation can't ping itself Date: 1999/02/25 Message-ID: <919950141.4676@news.Colorado.EDU> X-Deja-AN: 448303128 Distribution: cu Sender: daemon@lace.colorado.edu Delivered-To: decstation-managers@sws1.ctd.ornl.gov X-Authentication-warning: ns1.eds.com: Host nnsa2.eds.com [192.85.154.30] claimed to be nnsa.eds.com Followup-To: poster X-Note1: message-id generated by recnews X-Note2: mail msgid was <990225084133.37e5e@atdva3.atd.gmeds.com> Organization: University of Colorado at Boulder Newsgroups: cu.decstation.managers