SEO

Simple scenario ... two OpenServers, one Enterprise the other Desktop
(both 5.04). Host files are identical. One is 192.168.0.1 the other is
192.168.0.2, netmask 255.255.255.0, broadcast 192.168.0.255.

Both see everything else on the network, Enterprise sees the Desktop,
can ping, telnet, ftp into it. Desktop has no idea the Enterprise is
there. This is too simple for words, but I've missed something,
somewhere...

Anyone got a clue (yeah, I know this is probably something REAL
stupid).

Jim Hickinbotham

Jim Hickinbotham wrote:

> Simple scenario ... two OpenServers, one Enterprise the other Desktop
> (both 5.04). Host files are identical. One is 192.168.0.1 the other is
> 192.168.0.2, netmask 255.255.255.0, broadcast 192.168.0.255.
>
> Both see everything else on the network, Enterprise sees the Desktop,
> can ping, telnet, ftp into it. Desktop has no idea the Enterprise is
> there. This is too simple for words, but I've missed something,
> somewhere...
>
> Anyone got a clue (yeah, I know this is probably something REAL
> stupid).

When you try to "see" one from the other, are you using IP addresses or
host names? If host names, there must be something wrong with host name
resolution. One machine is getting a good answer from DNS (or
/etc/hosts), the other one isn't.

Try `ping -n 192.168.0.1` from 2, and vice versa.

>Bela<

Bela Lubkin <belal@sco.com> wrote in message news:<20031112090850.GL14056@sco.com>...
> When you try to "see" one from the other, are you using IP addresses or
> host names? If host names, there must be something wrong with host name
> resolution. One machine is getting a good answer from DNS (or
> /etc/hosts), the other one isn't.
>
> Try `ping -n 192.168.0.1` from 2, and vice versa.
>
> >Bela<


Tried pinging both directions with hostnames and ip's. The Enterprise
server has repsonses from the Desktop, but not vice versa. Arp does
occaisionally show the ip of the Ent. on the Desktop, on the Ent. it's
solid. Makes no sense since I can even telnet and ftp into the Desktop
from the Enterprise.

Desktop responds with 'host down' when trying to ping the Ent, from
either hostname or ip. Stopped and started tcp on both, tried
rebooting to no avail. Flushed the arp cache, no joy.

Jim Hickinbotham

Jim Hickinbotham typed (on Wed, Nov 12, 2003 at 09:06:22AM -0800):
| Bela Lubkin <belal@sco.com> wrote in message news:<20031112090850.GL14056@sco.com>...
| > When you try to "see" one from the other, are you using IP addresses or
| > host names? If host names, there must be something wrong with host name
| > resolution. One machine is getting a good answer from DNS (or
| > /etc/hosts), the other one isn't.
| >
| > Try `ping -n 192.168.0.1` from 2, and vice versa.
| >
| > >Bela<
|
|
| Tried pinging both directions with hostnames and ip's. The Enterprise
| server has repsonses from the Desktop, but not vice versa. Arp does
| occaisionally show the ip of the Ent. on the Desktop, on the Ent. it's
| solid. Makes no sense since I can even telnet and ftp into the Desktop
| from the Enterprise.
|
| Desktop responds with 'host down' when trying to ping the Ent, from
| either hostname or ip. Stopped and started tcp on both, tried
| rebooting to no avail. Flushed the arp cache, no joy.

Check the routing (netstat -nr).

--
JP

In article <8056da43.0311120906.3ce8f0c3@posting.google.com >,
Jim Hickinbotham <aardvark@peaknet.net> wrote:
>Bela Lubkin <belal@sco.com> wrote in message news:<20031112090850.GL14056@sco.com>...
>> When you try to "see" one from the other, are you using IP addresses or
>> host names? If host names, there must be something wrong with host name
>> resolution. One machine is getting a good answer from DNS (or
>> /etc/hosts), the other one isn't.

>> Try `ping -n 192.168.0.1` from 2, and vice versa.

>> >Bela<

>Tried pinging both directions with hostnames and ip's. The Enterprise
>server has repsonses from the Desktop, but not vice versa. Arp does
>occaisionally show the ip of the Ent. on the Desktop, on the Ent. it's
>solid. Makes no sense since I can even telnet and ftp into the Desktop
>from the Enterprise.

>Desktop responds with 'host down' when trying to ping the Ent, from
>either hostname or ip. Stopped and started tcp on both, tried
>rebooting to no avail. Flushed the arp cache, no joy.

I saw something remotely similar when trying to trouble shoot
a T1. We were providing IP and the CLEC was providing transport and
telephones. We looped to my 7513 just fine, the smart jack at my
site, his mid-point, a transition at anohter point, to their
smart-jack and it failed.

All three were on the phone and Max [the telco person] had them
wire a jack as a loopback, and then I could loopback to their hand
but not the Cisco. We said then perhaps you jack is mis-wired.

"We don't have a jack. We just have a 75 foot cable with a plug on
this end and we must moved the connectors over on the 66 block".

The studid fools has cross wired on pair - so things worked in one
direction but not the other.

Check all your cables, connections, etc. The company I was working
with also did convention installs and as a promotional item we
gave out ethernet loopback devices to all customers - complete with
a little light. They loved it, and it saved us more than the cost
of the device.

Since you've checked all the SW I'm thinking it is a wiring issue.

But I could be wrong.

Bill

--
Bill Vermillion - bv @ wjv . com

I am going to be on-site tomorrow. The only cable involved is a patch
cable. The two servers sit next to each other, connected to a switch.

Jim Hickinbotham

>
> I saw something remotely similar when trying to trouble shoot
> a T1. We were providing IP and the CLEC was providing transport and
> telephones. We looped to my 7513 just fine, the smart jack at my
> site, his mid-point, a transition at anohter point, to their
> smart-jack and it failed.
>
> All three were on the phone and Max [the telco person] had them
> wire a jack as a loopback, and then I could loopback to their hand
> but not the Cisco. We said then perhaps you jack is mis-wired.
>
> "We don't have a jack. We just have a 75 foot cable with a plug on
> this end and we must moved the connectors over on the 66 block".
>
> The studid fools has cross wired on pair - so things worked in one
> direction but not the other.
>
> Check all your cables, connections, etc. The company I was working
> with also did convention installs and as a promotional item we
> gave out ethernet loopback devices to all customers - complete with
> a little light. They loved it, and it saved us more than the cost
> of the device.
>
> Since you've checked all the SW I'm thinking it is a wiring issue.
>
> But I could be wrong.
>
> Bill