--
__/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/
Jeffrey G. Micono 505.844.6767
Ktech Corporation 505.268.3379
__/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/ __/
_______________________________________________________________________
from Tom Webster
Kathy,
Try doing a "netstat -r" to verify what your routing table looks like.
The output should, hopefully, look something like:
----- snip ----- snip ----- snip ----- snip ----- snip -----
Routing tables
Destination Gateway Flags Refs Use Interface
Netmasks:
Inet 255.255.0.0
Route Tree for Protocol Family 2:
default WAN.DOM.COM UG 4 40194 tu0
localhost localhost UH 7 366158 lo0
168.100 host U 48 1476870 tu0
----- snip ----- snip ----- snip ----- snip ----- snip -----
Where: I am on a class 'b' network (168.100, subnet has been changed to
protect the guilty), my hostname is "host" (we'll pretend my address is
168.100.100.1) and my default router is "WAN.DOM.COM".
Some things to check:
1. Make sure your netmask is set correctly. The mask tells the system
how big of a network to consider 'local'. I'm on a class 'b' (large)
subnet, so mine is 255.255.0.0. This would mean that 'host' would
consider everything in 168.100.* as local. If you are on a class 'c'
network, yours netmask should be 255.255.255.0, meaning that
everything
in 168.100.100.* would be local. If you have set you subnet mask too
restrictively, i.e. you are on a class 'b' net, but have it set for
a class 'c' -- your system may think it can't reach the router.
2. Make sure that you have a default route defined and it is marked with
a gateway ('G') flag. If not, you can add one using the 'route'
command manually. In the example above "WAN.DOM.COM" is my default
router.
3. If your network is not really complex, or that complexity is handled
by the routers, you may save yourself a lot of headaches by just
leaving routed turned off and setting a static route or two. Your
system won't do auto-discovery of new or failed net paths, but it
is simple and should only need to be changed once in a blue moon.
4. Invest some time in the route manual page, it is one of those things
that is good to know about.
Hope this helps,
Tom
--
+--------------------------------+------------------------------+
| Tom Webster | "Funny, I've never seen it |
| SysAdmin MDA-SSD ISS-IS-HB-S&O | do THAT before...." |
| webster_at_ssdpdc.mdc.com | - Any user support person |
+--------------------------------+------------------------------+
| Unless clearly stated otherwise, all opinions are my own. |
+---------------------------------------------------------------+
_______________________________________________________________________
from Alex_Nord_at_jabil.com:
In addition to having routed running, you must make sure that you
still have the correct value set for your default gateway. I know
this is an obvious pointer, but sometimes they are the easiest to
overlook.
_______________________________________________________________________
from George Gallen:
this happened to us once, the problem it turned out was the
ethernet connection to our LAN fell out a little bit, not enough to
look like it was out, yet not enough to transmit.
George Gallen
ggallen_at_slackinc.com
_______________________________________________________________________
from Bill Bathurst :
Is the computer you are trying to reach outside your network or inside
your network?
If it is outside your network you need to add a static route:
(1) Edit the /etc/route file.
(2) Enter in the IP address of your router. If it is already there
then it is another problem.
or
(1) Run netsetup and add the router IP via the add static route option.
Make sure to read the man page first.
Restart networking:
/usr/sbin/rcinet restart
Don't forget "traceroute" is a valuable tool to see where route is
getting
cut off.
Bill Bathurst http://freerange.com
Systems Engineer/Oracle DBA Freerange Media
_______________________________________________________________________
from Dick Abraham:
Try: /usr/sbin/route add default <router address>
_______________________________________________________________________
from Cliff Krieger:
Kathy,
You left out some important information such as your address in
relation to the address you are trying to ping. If they are on the same
network, then you don't need a route. In this case, with the network
unreachable I would guess that they are not. Every time I have seen
this it is either because the default route went away, or because a
static route went away. Routed will usually pick a good default route,
but it might not pick up on a static route that isn't advertised. That
last idea is my best guess for what is wrong.
-cliff
_______________________________________________________________________
from Patricia Campbell :
This may seem obvious but did you check the network card and cable ??
and can other machines on the same subnet ping you ??
Also
1 try setting static routing temporarily to ensure connectivitiy.
2 gated works better than routed, it sometimes looses connections.
Patricia Campbell campbe13_at_cn.ca
Telecomm _at_ CNR voice 514-399-7187
Montreal, Quebec fax 514-399-8105
Canada
_______________________________________________________________________
from Brian Sheehan
I have had the same error, always because my default route file was
gone:
/etc/routes
It should contain just one line:
default xxx.xxx.xxx.xxx
where it has your default route IP address. See if that helps...
- Brian
+---------------------------------------+------------------------------+
| Brian Sheehan | Standard Disclaimer: |
| Research Programmer | "My opinions are not those |
| The Scripps Research Institute | of my employers or their |
| La Jolla, CA | employers or their....." |
| | |
| (619)784-2206 (voice) | Is the internet slowing |
| (619)784-2943 (fax) | down, or does it just SEEM |
| sheehan_at_scripps.edu | that way because our |
| http://dilbert.scripps.edu/~sheehan | computers are faster ? ;) |
+---------------------------------------+------------------------------+
end of responses
_______________________________________________________________________
Received on Tue Mar 25 1997 - 18:38:47 NZST
This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:36 NZDT