Help: "network is unreachable"
Matthew J Zukowski
as the ability to telnet to my sun IPX from my pc under linux and
windows98. This is happy. But for some reason, it's not happening any
more. It's fetching the DNS entry, so when I do the following...
telnet coho.halcyon.com
Trying 198.137.131.12
Unable to connect to remove host, network is unreachable.
This is most odd because the network is here, and I can reach 2 other
nodes by reaching out my arm. I can reach it, and I can telnet to the
sun, just not from it.
I consider this most odd. My hub light has a signal, and everything
sugests good communication, and the fact that the DNS look up is fuctional
means there is some communication going on. Name lookup is accutate,
tested some sights that are not in my little 4 machine network, and I used
some sights that were not stored on my nt's name cache, so the sun box is
reaching outside my network to get these numbers, yet it considers the
"network unreachable".
I do have an entry for the sun box, "bob", on my hosts file, and during
hte most recent install., I didn't get an error as I did before that
lookup failed, so bob knows who is is. Name lookup works great even for
my internal machines, but "network in unreachable", very frustrating when
you can just reach out and touch the nodes.
What could be the problem here :)
thanks...
matt
John Doherty
Zukowski) wrote:
| telnet coho.halcyon.com
| Trying 198.137.131.12
| Unable to connect to remove host, network is unreachable.
|
| This is most odd because the network is here, and I can reach 2 other
| nodes by reaching out my arm.
Obviously, physical proximity isn't what counts here. Usually, "network
is unreachable" means that the destination IP address is not on the
local network and there is no known route to the remote network.
| Name lookup is accurate
Are you sure? Here's what I find:
$ whois halcyon.com
Domain Name: HALCYON.COM
Domain servers in listed order:
NWNEXUS.WA.COM 192.135.191.1
NWFOCUS.WA.COM 192.135.191.3
BOLERO.RAHUL.NET 192.160.13.1
HUSTLE.RAHUL.NET 192.160.13.2
$ nslookup
Default Server: localhost
Address: 127.0.0.1
> server NWNEXUS.WA.COM
Default Server: NWNEXUS.WA.COM
Address: 192.135.191.1
> coho.halcyon.com
Server: NWNEXUS.WA.COM
Address: 192.135.191.1
Name: coho.halcyon.com
Address: 198.137.231.21
It looks like your machine resolves coho.halcyon.com to 198.137.131.12,
when an authoritative name server for halcyon.com resolves it to
198.137.231.21, so I'm not sure that your name service really is working
properly.
FWIW, I can ping coho.halcyon.com (198.137.231.21) just fine.
--
Matthew J Zukowski
: In article <81ac5c$446$1...@brokaw.wa.com>, zake...@halcyon.com (Matthew J
: Zukowski) wrote:
:
: | telnet coho.halcyon.com
: | Trying 198.137.131.12
: | Unable to connect to remove host, network is unreachable.
: |
: | This is most odd because the network is here, and I can reach 2 other
: | nodes by reaching out my arm.
:
: Obviously, physical proximity isn't what counts here. Usually, "network
: is unreachable" means that the destination IP address is not on the
: local network and there is no known route to the remote network.
That was meant more for humor, symantics, the developers attempt to
frustrate the user by choosing words that the user can inturperate.
As far as no known route, I'd assume that I would use
route add 192.168.0.3 default
(my nt router/dns)
But this too results in "unable to reach the network".
:
: | Name lookup is accurate
Yes actually, while line 1 was a typo, microsoft natural keyboard
adjustments :), my test is the telnet server of my providership,
198.137.231.21. It actually is getting the right numbers from the name
lookup, but alas isn't going there because it thinks the network in
unreachable.
So it's reading the numbers though my NT box, network blinks and modem
blinks from my requests. I am able to telnet/ftp to my sun box. I am
also able to ftp a file that I grabbed from king.halcyon.com and put it
onto the sun box, and run it on the sun. Pico was the test file, somthing
not in the core install. This sugests the network is ok, perhaps a sun
side configeration issue?
: Are you sure? Here's what I find:
:
: $ whois halcyon.com
:
: Domain Name: HALCYON.COM
:
: Domain servers in listed order:
:
: NWNEXUS.WA.COM 192.135.191.1
: NWFOCUS.WA.COM 192.135.191.3
: BOLERO.RAHUL.NET 192.160.13.1
: HUSTLE.RAHUL.NET 192.160.13.2
:
: $ nslookup
: Default Server: localhost
: Address: 127.0.0.1
:
: > server NWNEXUS.WA.COM
: Default Server: NWNEXUS.WA.COM
: Address: 192.135.191.1
:
: > coho.halcyon.com
: Server: NWNEXUS.WA.COM
: Address: 192.135.191.1
:
: Name: coho.halcyon.com
: Address: 198.137.231.21
:
: It looks like your machine resolves coho.halcyon.com to 198.137.131.12,
: when an authoritative name server for halcyon.com resolves it to
: 198.137.231.21, so I'm not sure that your name service really is working
: properly.
:
: FWIW, I can ping coho.halcyon.com (198.137.231.21) just fine.
Assume my origional type was a typo, or I was looking at the wrong
numbers, I just retested and I'm reading the correct numbers,
198.137.231.21. Also it's getting the internal numbers correctly...
helios 192.168.0.3 (correct) nt server
gandhi 192.168.0.2 (correct) Sometimes linux, sometimes win98
suezuke 192,168.0.1 (correct) win98 box, with ftpd
bob 192.168.0.128 (correct) it self.
coho 198.137.231.21 (correct) my providers telnet server
.halcyon.com :)
This is what's baffeling to me, how is it that it understands how to
resolve names, yet seem to think the network is unreachable.
John Doherty
Zukowski) wrote:
> This is what's baffeling to me, how is it that it understands how to
> resolve names, yet seem to think the network is unreachable.
They're two separate issues. What does netstat -r on your sun show?
--
John Doherty
> As far as no known route, I'd assume that I would use
> route add 192.168.0.3 default
> (my nt router/dns)
What is the IP address of the sun? If it's 192.168.0.x, then it
shouldn't need a route to its own network. How is your network
connected to the internet? Is the NT box the router to the rest
of the world? If so, then the route command you need is
route add default 192.168.0.3 1
--
Matthew J Zukowski
: In article <81bem2$s2p$1...@brokaw.wa.com>, zake...@halcyon.com (Matthew J
Ahhhh, syntax error, thank you thank you thank you!
My bad.
Fully fuctional, makes me happy :)
Jerry Aguirre
Matthew J Zukowski <zake...@halcyon.com> wrote:
> telnet coho.halcyon.com
> Trying 198.137.131.12
> Unable to connect to remove host, network is unreachable.
This is a network routing problem, not a DNS or hosts file problem.
As you say the hostname is being resolved to an IP address. At that
point DNS/NIS/Hosts has done its job.
Posible problems are:
1 - Your interface is not configured correctly. This could be
because it has an incorrect IP or an incorrect netmask.
Run "ifconfig -a" and verify that the IP and netmask are
correct.
2 - Your missing or have an incorrect default gateway. Run
"netstat -rn" and verify that the default route is correct.
3 - Your network is weird :-). People come up with some fairly
complex networks. It is difficult to advise without knowing
more detail of your topology. By example running multiple
networks on the same ethernet requires special routing
entries.