Complete.Org: Mailing Lists: Archives: linux-help: January 2001:
[linux-help] Re: One-way-telnet
Home

[linux-help] Re: One-way-telnet

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: linux-help@xxxxxxxxx
Subject: [linux-help] Re: One-way-telnet
From: Jeff Vian <jvian@xxxxxxxxxx>
Date: Sun, 07 Jan 2001 02:08:59 -0600
Reply-to: linux-help@xxxxxxxxx

1.  Unless you have a telnet server running on the windows box you can't
telnet to it.

2.  On the RH box check hosts.allow (as was said), and check that telnet is
enabled. Look in /etc/inetd.conf
Also try telneting from the RH box to itself. That will let you know if the
RH box is setup to accept telnet.

3.  However, I suspect routing is the problem.
I do not see a default route on what you sent.
Actually I see two gateways listed. ( the lines with UG in the FLAGS
column ), and these point to BOTH NICs.
You should have one gateway listed as default, and the cable connection is
correctly trying to assign a default route on eth0.

The lines in /etc/sysconfig/network file for the default gateway on eth1 is
likely the problem.

All my internal PCs have the internal address of my Linux gateway as their
default gateway (192.168.2.10).  The gateway PC gets its default route from
the DSL connection via DHCP.

My network and ifcfg files follow, along with my routing table
I do not have either GATEWAYDEV or GATEWAY in the network file.  These are
automatically assigned by the DSL connection.

Note:   my eth1 is connected to the DSL modem and eth0 is my internal
network.

------network ------
NETWORKING=yes
HOSTNAME=my.host.name
DOMAINNAME=my.domain

------ifcfg-eth0------
DEVICE=eth0
IPADDR=192.168.2.10
NETMASK=255.255.255.0
NETWORK=192.168.2.0
BROADCAST=192.168.2.255
ONBOOT=yes

------ifcfg-eth1------
DEVICE=eth1
BOOTPROTO=dhcp
ONBOOT=yes


-----result of    netstat -r    --------
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
my.host.name *               255.255.255.255 UH        0 0          0 eth0
192.168.2.0     *               255.255.255.0   U         0 0          0
eth0
216.63.200.0    *               255.255.252.0   U         0 0          0
eth1
127.0.0.0       *               255.0.0.0       U         0 0          0 lo
default         adsl-216-63-203 0.0.0.0         UG        0 0          0
eth1



----- Original Message -----
From: Steven Saner <ssaner@xxxxxxxxxxxxxxx>
To: <linux-help@xxxxxxxxx>
Sent: Saturday, January 06, 2001 11:21 PM
Subject: [linux-help] Re: One-way-telnet


>
> TCP wrappers perhaps? Look in /etc/hosts.allow
>
>
> On Sat, Jan 06, 2001 at 11:21:33PM -0600, Bruce Bales wrote:
> >
> > I have a Linux (RH6) gateway with cable internet on eth0.  eth1 hooks to
a hub
> > and a network of a windows 98 box and another RH6 box.  I can ping both
ways
> > gateway to the windows box and both ways gateway to Linux2 box.  I can
telnet
> > from either box on the network to the gateway.   When I try to telnet
from the
> > gateway to either of the others, I get " trying 192.168.0.2" (or
192.168.0.3)
> > then "connection refused."
> >
> > ipchains is "ACCEPT", "ACCEPT", "ACCEPT".
> >
> > /etc/sysconfig/network,  ifconfig, and the routing table from the
gateway box
> > are below.  Why can I telnet only one way?
> >
> > bruce
> >
> > /sysconfig/network:
> > NETWORKING=yes
> > HOSTNAME=sam
> > NISDOMAIN="mynet.com"
> > GATEWAY='sam 192.168.0.1'
> > GATEWAYDEV=eth1
> > FORWARD_IPV4=no
> >
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
> > 192.168.0.1     0.0.0.0         255.255.255.255 UH       0 0          0
eth1
> > 192.168.0.0     192.168.0.1  255.255.255.0    UG       0 0          0
eth1
> > 192.168.0.0     0.0.0.0         255.255.255.0     U          0 0
0 eth1
> >
> > 65.27.96.0       0.0.0.0         255.255.248.0     U          0 0
0
> > eth0
> > 127.0.0.0         0.0.0.0         255.0.0.0             U          0 0
> > 0 lo
> > 0.0.0.0             65.27.96.1    0.0.0.0                UG        0 0
> > 0 eth0
> >
> > ifconfig:
> > eth0      Link encap:Ethernet  HWaddr 00:A0:CC:5C:AB:35
> > inet addr:65.27.101.55  Bcast:255.255.255.255  Mask:255.255.248.0
> > UP BROADCAST RUNNING  MTU:1500  Metric:1
> > RX packets:2575 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:11 Base address:0xfc00
> >
> > eth1      Link encap:Ethernet  HWaddr 00:00:E8:3E:F7:C8
> > inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > RX packets:2152 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:3 Base address:0x300
> >
> > lo        Link encap:Local Loopback
> > inet addr:127.0.0.1  Mask:255.0.0.0
> > UP LOOPBACK RUNNING  MTU:3924  Metric:1
> > RX packets:148 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:148 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> >
> >
> >
> >
> >
> > -- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
> > visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi
>
> -- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
> visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi
>


-- This is the linux-help@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi


[Prev in Thread] Current Thread [Next in Thread]