As others have pointed out, look for an ACL on the inbound and outbound
interfaces.
As for the telnet access on your Unix box, see if you get a port connection
on the box using a port scanner. If so then it's likely TCP Wrappers that's
dumping your connection due to an incorrect configuration in
It depends
Check if there is access-list on router that
does not permit telnet to go through
or Check the Unix box , and make sure it has
telnetd
--- Moahzam Durrani <[EMAIL PROTECTED]> wrote:
> IF THERE ARE 2 DIFFERENT NETWORKS A AND B , AND WE
> COULD PING FROM NETWORK A
> TO B , BUT NOT TELNET
It could be either. Can you telnet to the box in network B from network B?
Denis
Denis A. Baldwin - Network Administrator
A+ / Network + / I-Net+ / MCP
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Moahzam Durrani
Sent: Thursday, February 15, 2001
Need a little more detail ... and yes it could be an access list
configuration issue.
Can you actually ping from a node in network a the Unix Box in network B
that you are attempting to telnet to ?
Can you actually ping from the Unix Box in B to the node in Network A ?
Can you telnet to the UNI
4 matches
Mail list logo
