RedHat won't listen to Debian

I have several Linux computers networked, and most run Debian.
One runs RedHat 9.

The Debian systems open INET sockets to one another for a special
application that I use. They cannot open a socket to the RedHat
system. The Python app says that there is no route to the RedHat host.

The only clue I've found is that traceroute from Debian to RedHat
fails with "!C" codes. I've never seen this code before. The
man page says it means that access to the remote host is prohibited.
(According to the Web, "!H" is more commonly used for this error.)

Can anybody suggest how to un-prohibit access to the RedHat system?

-:-
B Flitter flutter in the air,
How I wonder why you're there!
Chasing BATS is not much fun--
The worst is when you're killed by one.

--The Roguelet's ABC
--
Col. G. L. Sicherman
(E-Mail Removed)

On Sat, 17 Dec 2005 01:17:48 GMT, (E-Mail Removed) (A deaf heart, a loose liver) wrote:

>
>Can anybody suggest how to un-prohibit access to the RedHat system?

Yep, install Slackware ) RedHat 9 is dead.

Grant.

A deaf heart, a loose liver wrote:
> I have several Linux computers networked, and most run Debian.
> One runs RedHat 9.
>
> The Debian systems open INET sockets to one another for a special
> application that I use. They cannot open a socket to the RedHat
> system. The Python app says that there is no route to the RedHat host.
>
> The only clue I've found is that traceroute from Debian to RedHat
> fails with "!C" codes. I've never seen this code before. The
> man page says it means that access to the remote host is prohibited.
> (According to the Web, "!H" is more commonly used for this error.)
>
> Can anybody suggest how to un-prohibit access to the RedHat system?
>
> -:-
> B Flitter flutter in the air,
> How I wonder why you're there!
> Chasing BATS is not much fun--
> The worst is when you're killed by one.
>
> --The Roguelet's ABC

Go pick more clues:

- How is the network laid out?
- What do the following commands report on each host:
- ifconfig -a
- route -n
- iptables -nvL

A more detailed response can be obtained with tcpdump or
Ethereal on the packet exchange during the connection attempt.

--

Tauno Voipio
tauno voipio (at) iki fi

On Sat, 17 Dec 2005, in the Usenet newsgroup comp.os.linux.networking,
in article <0HJof.97$(E-Mail Removed)>, A deaf heart, a loose liver wrote:

>The Debian systems open INET sockets to one another for a special
>application that I use. They cannot open a socket to the RedHat
>system. The Python app says that there is no route to the RedHat host.

Run tcpdump and watch the packet exchange.

>The only clue I've found is that traceroute from Debian to RedHat
>fails with "!C" codes. I've never seen this code before. The
>man page says it means that access to the remote host is prohibited.
>(According to the Web, "!H" is more commonly used for this error.)

1812 Requirements for IP Version 4 Routers. F. Baker, Ed.. June 1995.
(Format: TXT=415740 bytes) (Obsoletes RFC1716, RFC1009) (Updated by
RFC2644) (Status: PROPOSED STANDARD)

See Section 5.2.7.1 - specifically about page 81.

>Can anybody suggest how to un-prohibit access to the RedHat system?

Fix the firewall configuration on the Red Hat box.

Old guy

In <IBPof.26$(E-Mail Removed)>, (E-Mail Removed) wrote:
>
> - How is the network laid out?
> - What do the following commands report on each host:
> - ifconfig -a
> - route -n
> - iptables -nvL

Iptables -L showed that some kind of RedHat firewall was up.
As soon as I figured out how to disable it, my problem vanished.
Thanks to all who replied.

-:-
The identical is equal to itself, since it is different.

--Franco Spisani, _Philosophical
Foundations of Autogenetic Logic_
--
Col. G. L. Sicherman
(E-Mail Removed)