ftp/telnet
in [Solaris]
|
Prev: SQLite build process
Next: metareplace -e
From: patrick_nyr on 18 Mar 2010 12:35 "Oscar del Rio" <delrio(a)mie.utoronto.ca> wrote in message news:hntjqi$3go$1(a)news.mie... > On 03/18/10 11:58 AM, patrick_nyr wrote: > >> The telnet daemon and ftp daemon are enabled. > > what does "telnet hostname 21" say? > Hi, I get the following message: "Connecting To <hostname> ...Could not open connection to host, on port 21: Connect failed" Thanks
From: hume.spamfilter on 18 Mar 2010 13:18 patrick_nyr <mpprpp2000(a)yahoo.com> wrote: > "Connecting To <hostname> ...Could not open connection to host, on port 21: > Connect failed" And if you log into the server itself, and use the command: telnet localhost 21 .... what do you see? -- Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: Chris Ridd on 18 Mar 2010 13:25 On 2010-03-18 17:18:51 +0000, hume.spamfilter(a)bofh.ca said: > patrick_nyr <mpprpp2000(a)yahoo.com> wrote: >> "Connecting To <hostname> ...Could not open connection to host, on port 21: >> Connect failed" > > And if you log into the server itself, and use the command: > > telnet localhost 21 > > ... what do you see? Also are any other inetd services working? -- Chris
From: patrick_nyr on 18 Mar 2010 13:26 <hume.spamfilter(a)bofh.ca> wrote in message news:hntn9r$dea$1(a)Kil-nws-1.UCIS.Dal.Ca... > patrick_nyr <mpprpp2000(a)yahoo.com> wrote: >> "Connecting To <hostname> ...Could not open connection to host, on port >> 21: >> Connect failed" > > And if you log into the server itself, and use the command: > > telnet localhost 21 > > ... what do you see? > > -- > Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/ > Ok, I see. Sorry about that. On the local machine I get: Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused Thanks
From: hume.spamfilter on 18 Mar 2010 14:40
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` ....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/ |