Is samba setup on this machine?
And is the FTP Daemon running?
Not exactly sure how to present this. However,
ops: In the local LAN consisting of several O/S's (SCO Linux, Windows, Trustix), the SuSE machine name is not shown in the WinTel Network window for selection.
ops: I can ftp out but the inbound connections are refused.
ops: Must all printer names begin with an alpha character for yast?, because I have several beginning with numerics.
Should any additional info be required, just give me a buzz.
TIA
Everything I learn gives me another way to say \"OOPS!\" :oops:
Is samba setup on this machine?
And is the FTP Daemon running?
ops: Samba probably is NOT set up. Here's the reading from netstat:
elbert:/etc # netstat -at
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:login *:* LISTEN
tcp 0 0 *rinter *:* LISTEN
tcp 0 0 *:microtalon-dis *:* LISTEN
tcp 0 0 *:netbios-ns *:* LISTEN
tcp 0 0 *:netbios-ssn *:* LISTEN
tcp 0 0 *op3 *:* LISTEN
tcp 0 0 *:netstat *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:x11 *:* LISTEN
tcp 0 0 elbert.creico:commd_tcp *:* LISTEN
tcp 0 0 *:ftp *:* LISTEN
tcp 0 0 *:telnet *:* LISTEN
tcp 0 0 localhost:smtp *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 192.168.1.16:ssh 192.168.1.127:4485 ESTABLISHED
elbert:/etc #
Is Samba difficult to set up and run? :?:
Everything I learn gives me another way to say \"OOPS!\" :oops:
i would actually think samba is set up, because your listening on netbios-* portsOriginally Posted by jeager";p="3256
That being the case, then what might the reason be that ftp out works and ftp in does not?
Everything I learn gives me another way to say \"OOPS!\" :oops:
1) ftp has nothing to do with samba
2) what's interesting is according to netstat you are listening on the ftp port
do you have a firewall running? If you don't know just post the output of
Code:# iptables -L
Here tiz:
elbert:/etc # iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
elbert:/etc #
Everything I learn gives me another way to say \"OOPS!\" :oops:
hmmm... so no firewall, i wonder what really is listening on port 21
could you post the output of
Code:# netstat -lap | grep -i ftp
Let me begin by saying thanks for taking the trouble to look at all this stuff. Here tiz:
elbert:/etc # netstat -lap | grep ftp
tcp 0 0 *:ftp *:* LISTEN 9368/inetd
elbert:/etc #
Everything I learn gives me another way to say \"OOPS!\" :oops:
ok, i'm guessing Suse sets up ftpd to be called by inetd, you can verify this with
i don't understand why you can't access it though if that is the caseCode:# cat /etc/inetd.conf | grep -i ftp
actually, can you post the output of the above command? Also are you _sure_ there isn't another firewall somewhere in the way of accessing ftp on this box?
Is it on the lan, or through the net? some isp block port 21.
Bookmarks