A telnet daemon problem

A telnet daemon problem

Post by Kevin Li » Sat, 12 May 2001 23:51:03



I'm running a small linux in kernel 2.4.2 and /dev have pty0~3, ttyp0~3, when I
test the system with chroot in.telnetd can work, but the system boot alone the in.telnetd can not accept the telnet connect, the daemon response "all network ports in use", what's happend?

--
Best regards,
Kevin Liu

--
MIS Family, Inc.
No.10, Shuren Rd., Shanhua Jen,
Tainan, Taiwan 741.
Tel:+886-6-583-1381
Fax:+886-6-583-5209
http://mis-family.ath.cx

 
 
 

A telnet daemon problem

Post by Dean Thompso » Sun, 13 May 2001 12:47:30


Hi!,

Quote:> I'm running a small linux in kernel 2.4.2 and /dev have pty0~3, ttyp0~3,
> when I test the system with chroot in.telnetd can work, but the system boot
> alone the in.telnetd can not accept the telnet connect, the daemon response
> "all network ports in use", what's happend?

Check to see whether or not the terminal devices have been created in the /dev
directory.  This problem sometimes becomes apparent after a kernel has been
upgraded from the 2.2 kernel to the 2.4 kernel.  The only thing that I find
puzzling with your situation is that it works when you "chroot" the program
but not when you don't.  Eitherway, I would check to make sure that all the
terminal devices have been created.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

1. A telnet daemon problem

I'm running a small linux in kernel 2.4.2 and /dev have pty0~3, ttyp0~3, when I test the system with chroot in.telnetd can work, but the system boot alone the in.telnetd can not accept the telnet connect, the daemon response "all network ports in use", what's happend?

--
Best regards,
Kevin Liu

--
MIS Family, Inc.
No.10, Shuren Rd., Shanhua Jen,
Tainan, Taiwan 741.
Tel:+886-6-583-1381
Fax:+886-6-583-5209
http://mis-family.ath.cx

2. Major problems with upgrade to 5.0

3. Linux Telnet Daemon security setup problem with a Windows client

4. qdaemon

5. FTP and Telnet daemon problem. HELP...

6. 3d voodoo banshee-- gateway 450 video card

7. Telnet daemon problem fixed

8. Concepts of RAID on SPARC

9. Telnet, finger, ftp (daemon) problems.

10. A telnet daemon problem

11. set up daemons for telnet, etc

12. Can't telnet to Imap daemon ports

13. Source for telnet daemon/client w. RFC1408/1409 ?