home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!cs.columbia.edu!ji
- From: ji@cs.columbia.edu (John Ioannidis)
- Subject: Re: ping works, but ftp/telnet get "no route to host"
- Message-ID: <BrsM1C.36v@cs.columbia.edu>
- Sender: news@cs.columbia.edu (The Daily News)
- Organization: Columbia University Department of Computer Science
- References: <BrruC8.FEo@spock.dis.cccd.edu>
- Date: Wed, 22 Jul 1992 13:41:35 GMT
- Lines: 27
-
- In article <BrruC8.FEo@spock.dis.cccd.edu> markb@spock.dis.cccd.edu (Mark Bixby) writes:
- >Why would I be able to ping a site OK, but when I try to ftp or telnet to it
- >I receive a "no route to host" error? Traceroute can find the host, and it
- >is apparently on Alternet, if that makes a difference.
- >
- >Any info would be most helpful to this tcp/ip novice. Thanks.
- >
-
- The site you are trying to ping is running a firewall gateway, because
- they're too lazy to beef up their host security and are relying on the
- firewall to protect themselves against external attacks. The site
- router(s) look inside your packets, and if they are not to/from
- specific hosts or ports, they don't forward them, but rather send you
- an ICMP host unreachable message back.
-
- I wish I had a transcript of Dave Clark's talk at the IETF last week.
- He said some great things about firewall gateways and mailbridges, and
- how they've essentially destroyed the whole purpose of having an IP
- internet, and have forced a lot of us to use mail as a transport-level
- protocol.
-
- /ji
-
- In-Real-Life: John "Heldenprogrammer" Ioannidis
- E-Mail-To: ji@cs.columbia.edu
- V-Mail-To: +1 212 854 8120
- P-Mail-To: 450 Computer Science \n Columbia University \n New York, NY 10027
-