ftp/telnet
in [Solaris]
|
Prev: SQLite build process
Next: metareplace -e
From: patrick_nyr on 19 Mar 2010 08:29 "devN" <eishf2000(a)gmail.com> wrote in message news:cd69f04d-b2d4-46d4-a2ac-e725ea4752f2(a)19g2000yqu.googlegroups.com... On Mar 19, 12:52 am, "patrick_nyr" <mpprpp2...(a)yahoo.com> wrote: > <hume.spamfil...(a)bofh.ca> wrote in message > > news:hnts3a$gun$1(a)Kil-nws-1.UCIS.Dal.Ca... > > > > > > > patrick_nyr <mpprpp2...(a)yahoo.com> wrote: > >> Trying 127.0.0.1... > >> telnet: Unable to connect to remote host: Connection refused > > > There's something wrong with your inetd. I may be running, but it > > doesn't > > appear to have the proper ports open. > > > If /etc/inetd.conf contains the proper lines, then it's possible someone > > messed up that file, restarted or HUPped inetd, and then repaired the > > file. > > > The command: > > > pfiles `pgrep inetd` > > > ...will list what ports inetd has open. > > > Easiest thing to try is to try "pkill -1 inetd" to HUP inetd and see if > > it opens the proper ports. > > > How long has inetd been running? What's the date when you grep for its > > process? > > > -- > > Brandon Hume - hume -> BOFH.Ca,http://WWW.BOFH.Ca/ > > Hi, > > I check what you sent me, but I rebooted the machine this morning. > > Thanks > Is the problem resolved now after the reboot? Still not working after reboot. > With inetd.conf containing ftp lines, this is confusing. How long has > the inetd been running? Did you try running the FTPD manually? I haven't tried running it manually, I'll give it a try.
From: patrick_nyr on 19 Mar 2010 08:32 "Ceri Davies" <ceri_usenet(a)submonkey.net> wrote in message news:i_Jon.308300$X_6.284240(a)newsfe22.ams2... > On 2010-03-18, patrick_nyr <mpprpp2000(a)yahoo.com> wrote: >> >><hume.spamfilter(a)bofh.ca> wrote in message >> news:hnti5j$9fe$1(a)Kil-nws-1.UCIS.Dal.Ca... >>> patrick_nyr <mpprpp2000(a)yahoo.com> wrote: >>>> I ran the "netstat -af inet" and I don't see for ftp or telnet with >>>> LISTEN. >>> >>> Is inetd running? For example, >>> >>> # ps -ef | grep inetd >>> root 221 1 0 May 25 ? 8:37 /usr/sbin/inetd -s >>> >>> >> Hi, >> >> Yes, this is running. >> >>> ... and does /etc/inetd.conf exist and contain lines for 'ftp' and >>> 'telnet', >>> like: >>> >> >> Yes, it contains those lines for ftp and telnet' >> >>> # egrep 'ftp|telnet' /etc/inetd.conf >>> #telnet stream tcp6 nowait root /usr/sbin/in.telnetd >>> in.telnetd >>> ftp stream tcp6 nowait root /usr/sbin/in.ftpd >>> in.ftpd -a >>> >>> You can see there that ftp is enabled on this machine but telnet is not. >>> >> The telnet daemon and ftp daemon are enabled. > > Also check what port number the entry for ftp in /etc/services lists. > > Ceri > -- > That must be wonderful! I don't understand it at all. > -- Moliere > Just checked and for ftp it's 21 and telnet it's 23.
From: patrick_nyr on 19 Mar 2010 08:52 <hume.spamfilter(a)bofh.ca> wrote in message news:hnts3a$gun$1(a)Kil-nws-1.UCIS.Dal.Ca... > patrick_nyr <mpprpp2000(a)yahoo.com> wrote: >> Trying 127.0.0.1... >> telnet: Unable to connect to remote host: Connection refused > > There's something wrong with your inetd. I may be running, but it doesn't > appear to have the proper ports open. > > If /etc/inetd.conf contains the proper lines, then it's possible someone > messed up that file, restarted or HUPped inetd, and then repaired the > file. > > The command: > > pfiles `pgrep inetd` > > ... Hi, Here's the output from the pfiles `pgrep inetd` command 170: /usr/sbin/inetd -s Current rlimit: 1024 file descriptors 0: S_IFDIR mode:0755 dev:118,8 ino:2 uid:0 gid:0 size:1024 O_RDONLY 1: S_IFDIR mode:0755 dev:118,8 ino:2 uid:0 gid:0 size:1024 O_RDONLY 2: S_IFDIR mode:0755 dev:118,8 ino:2 uid:0 gid:0 size:1024 O_RDONLY 4: S_IFCHR mode:0000 dev:118,8 ino:13156 uid:0 gid:0 rdev:41,62 O_RDWR FD_CLOEXEC 5: S_IFCHR mode:0666 dev:118,8 ino:3314 uid:0 gid:3 rdev:21,0 O_WRONLY FD_CLOEXEC 6: S_IFCHR mode:0000 dev:118,8 ino:13160 uid:0 gid:0 rdev:41,51 O_RDWR 7: S_IFCHR mode:0000 dev:118,8 ino:13153 uid:0 gid:0 rdev:42,41 O_RDWR 8: S_IFCHR mode:0000 dev:118,8 ino:32781 uid:0 gid:0 rdev:42,37 O_RDWR 9: S_IFCHR mode:0000 dev:118,8 ino:32780 uid:0 gid:0 rdev:105,23 O_RDWR 10: S_IFCHR mode:0000 dev:118,8 ino:32779 uid:0 gid:0 rdev:105,24 O_RDWR 11: S_IFCHR mode:0000 dev:118,8 ino:32778 uid:0 gid:0 rdev:105,25 O_RDWR 12: S_IFCHR mode:0000 dev:118,8 ino:32777 uid:0 gid:0 rdev:42,36 O_RDWR 13: S_IFCHR mode:0000 dev:118,8 ino:32776 uid:0 gid:0 rdev:42,35 O_RDWR 14: S_IFCHR mode:0000 dev:118,8 ino:32775 uid:0 gid:0 rdev:42,34 O_RDWR 15: S_IFCHR mode:0000 dev:118,8 ino:32774 uid:0 gid:0 rdev:105,26 O_RDWR 16: S_IFSOCK mode:0666 dev:240,0 ino:8628 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 32795 17: S_IFCHR mode:0000 dev:118,8 ino:31919 uid:0 gid:0 rdev:41,58 O_RDWR 18: S_IFCHR mode:0000 dev:118,8 ino:13154 uid:0 gid:0 rdev:105,27 O_RDWR 19: S_IFSOCK mode:0666 dev:240,0 ino:8636 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 514 20: S_IFSOCK mode:0666 dev:240,0 ino:8627 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 512 21: S_IFSOCK mode:0666 dev:240,0 ino:8626 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 512 22: S_IFSOCK mode:0666 dev:240,0 ino:8625 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 517 23: S_IFCHR mode:0000 dev:118,8 ino:13155 uid:0 gid:0 rdev:41,29 O_RDWR 24: S_IFCHR mode:0000 dev:118,8 ino:32772 uid:0 gid:0 rdev:105,28 O_RDWR 25: S_IFCHR mode:0000 dev:118,8 ino:32771 uid:0 gid:0 rdev:41,28 O_RDWR 26: S_IFCHR mode:0000 dev:118,8 ino:32769 uid:0 gid:0 rdev:105,29 O_RDWR 27: S_IFCHR mode:0000 dev:118,8 ino:32768 uid:0 gid:0 rdev:42,27 O_RDWR 28: S_IFCHR mode:0000 dev:118,8 ino:7455 uid:0 gid:0 rdev:105,30 O_RDWR 29: S_IFCHR mode:0000 dev:118,8 ino:7453 uid:0 gid:0 rdev:105,31 O_RDWR 30: S_IFCHR mode:0000 dev:118,8 ino:7454 uid:0 gid:0 rdev:41,26 O_RDWR 31: S_IFCHR mode:0000 dev:118,8 ino:7452 uid:0 gid:0 rdev:105,32 O_RDWR 32: S_IFCHR mode:0000 dev:118,8 ino:7450 uid:0 gid:0 rdev:41,25 O_RDWR 33: S_IFCHR mode:0000 dev:118,8 ino:7450 uid:0 gid:0 rdev:105,33 O_RDWR 34: S_IFSOCK mode:0666 dev:240,0 ino:8624 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 42 35: S_IFCHR mode:0000 dev:118,8 ino:7448 uid:0 gid:0 rdev:105,34 O_RDWR 36: S_IFSOCK mode:0666 dev:240,0 ino:8624 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 540 37: S_IFSOCK mode:0666 dev:240,0 ino:7278 uid:0 gid:0 size:0 O_RDWR sockname: AF_INET 0.0.0.0 port: 32816
From: patrick_nyr on 19 Mar 2010 09:24 "devN" <eishf2000(a)gmail.com> wrote in message news:cd69f04d-b2d4-46d4-a2ac-e725ea4752f2(a)19g2000yqu.googlegroups.com... On Mar 19, 12:52 am, "patrick_nyr" <mpprpp2...(a)yahoo.com> wrote: > <hume.spamfil...(a)bofh.ca> wrote in message > > news:hnts3a$gun$1(a)Kil-nws-1.UCIS.Dal.Ca... > > > > > > > patrick_nyr <mpprpp2...(a)yahoo.com> wrote: > >> Trying 127.0.0.1... > >> telnet: Unable to connect to remote host: Connection refused > > > There's something wrong with your inetd. I may be running, but it > > doesn't > > appear to have the proper ports open. > > > If /etc/inetd.conf contains the proper lines, then it's possible someone > > messed up that file, restarted or HUPped inetd, and then repaired the > > file. > > > The command: > > > pfiles `pgrep inetd` > > > ...will list what ports inetd has open. > > > Easiest thing to try is to try "pkill -1 inetd" to HUP inetd and see if > > it opens the proper ports. > > > How long has inetd been running? What's the date when you grep for its > > process? > > > -- > > Brandon Hume - hume -> BOFH.Ca,http://WWW.BOFH.Ca/ > > Hi, > > I check what you sent me, but I rebooted the machine this morning. > > Thanks > >Did you try running the FTPD manually? > Ok, I ran it mannully and I get the following message: getpeername (/usr/sbin/in.ftpd) : Socket operation on non-socket.
From: hume.spamfilter on 19 Mar 2010 09:29
patrick_nyr <mpprpp2000(a)yahoo.com> wrote: > getpeername (/usr/sbin/in.ftpd) : Socket operation on non-socket. You can't run ftpd in standalone mode unless you remember to add the '-s' flag to the command line. This is documented in the in.ftpd manpage. Can you post your /etc/inetd.conf, please? The command: grep -v '^#' /etc/inetd.conf .... will produce the useful output. -- Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/ |