Re: telnet2

[ABrady <kcsmart kc rr com>]

On Sat, 1 Sep 2001 11:15:30 -0300 Ted Gervais <ve1drg fox nstn ca>
imparted to us:

> 
> > >Thinking a bit more. And further to my last message.
> > >Not sure what is meant by 'bind to port 24' ??
> > >
> > >What I did was run chkconfig --level 2345 telnet2 on.
> > >That enabled it. That should have got it to go. I checked using 
> > > 'chkconfig --list telnet2'  and it was 'on'..
> > >Don't know what else to do..
> >
> > Sendmail listens on port 25, Apache listens on port 80, ftpd listens
> on
> > port 21, telnetd listens on port 23. You must take positive steps to
> make
> > these daemons listen on alternate ports. It may be a config file
> change or
> > it may involve editing a Makefile or the source code and
> recompiling. They
> > will each listen on their default port unless you somehow tell them
> > otherwise.
> 
> Well, I am already using ports 23 and 24 for telnet on several other 
> machines. That works fine.  But on this ONE machine I must have
> forgotten to 
> do something as port 24 is not recognized.
> 
> So - if I have /etc/services file with telnet2 port 24 installed, and
> a new 
> entry in etc/xinetd/telnet2 - and things have been started using
> chkconfig, 
> what else is there to do to have port 24 working?? Have I forgotten
> something.

That should work. I've bound telnet2 to port 109 and it works fine.

There are some strange goings on with some of this. I had the same
problem once before. It absolutely wasn't the firewall, all of the
settings were absolutely correct and it still wouldn't work. A reinstall
later & it all worked, exactly the same setup.

I have a slightly similar problem in my current situation, but not quite
the same. I can telnet to telnet2 just fine from almost anywhere. I can
even do it from work over the internet. I can telnet from one internal
machine to the telnet or telnet2 ports. Internally on the linux machine
it all works. But, I can't do it from ONE machine on the internal
network to the telnet2 port. From the same host I can come in on regular
telnet which only works internally.

To clarify I have machine A, B and C. A is linux, B is NT, C is 'Doze95,
D is a work NT machine that only has access via the internet. C can
telnet or telnet2 into A. D can telnet2 only because telnet is only
internal and telnet2 is both. B, which should be able to do both can
ONLY telnet and cannot telnet2. Both B and C are on the same network, so
subnetting isn't a problem. B can do everything I need it to do, but it
cannot telnet2 under any circumstances.

Can't be a firewall or configuration issue because C can do it. Can't be
connectivitiy becaue B can telnet, B can get mail, ping, provide
sharing, get to the internet, etc.

I haven't worried much about this because as long as it can telnet, and
I have that only internally, I can do what I need. But, it should still
work.

-- 
/etc/passwd is full -- go away!