ftp to linux server fails

Hi,

I've recently setup a SuSE server on my network
and today I tried getting FTP to work, but I didn't
succeed.
Because it's just for testing I'm using ftpd (on SuSE 9.0).
I've added it to xinetd (in /etc/xinetd.d/ftpd.conf).
I can connect locally via "ftp localhost", but when I try
to connect via the command prompt in Windows XP "ftp 192.168.1.12",
the IP address of the server, that fails.
I am able to ping 192.168.1.12.
I was guessing iptables blocked access to it so I did
iptables --flush (probably not a good thing), but it didn't
help either.
And hosts.allow doesn't contain anything, while hosts.deny only
contains "http-rman: ALL EXCEPT LOCAL".
One last thing: my client (win xp) and server (SuSE) are connected
via a router (192.168.1.1).

Anyone who can tell me what I'm doing wrong?

Thanks in advance!

Kind Regards,
Sam

In article <Bhbfc.71095$(E-Mail Removed)>, SH wrote:
> Hi,
>
> I've recently setup a SuSE server on my network
> and today I tried getting FTP to work, but I didn't
> succeed.
> Because it's just for testing I'm using ftpd (on SuSE 9.0).
> I've added it to xinetd (in /etc/xinetd.d/ftpd.conf).
> I can connect locally via "ftp localhost", but when I try
> to connect via the command prompt in Windows XP "ftp 192.168.1.12",
> the IP address of the server, that fails.
> I am able to ping 192.168.1.12.
> I was guessing iptables blocked access to it so I did
> iptables --flush (probably not a good thing), but it didn't
> help either.
> And hosts.allow doesn't contain anything, while hosts.deny only
> contains "http-rman: ALL EXCEPT LOCAL".
> One last thing: my client (win xp) and server (SuSE) are connected
> via a router (192.168.1.1).
>
> Anyone who can tell me what I'm doing wrong?

Do a "netstat -ltnpa" (I don't use Suse so you may have to take some of
those arguments out if it complains, RH/FC's netstat takes all those args).
This should show you the ports in a listen state, for tcp, and the
associated processes. From this you should be able to see what address(es)
ftp is listening on (port 21). Your system may only be listening on
localhost for security reasons.

--
"SH1-0151. This is the serial number, of our orbital gun."

vom wrote:

> In article <Bhbfc.71095$(E-Mail Removed)>, SH wrote:
>> Hi,
>>
>> I've recently setup a SuSE server on my network
>> and today I tried getting FTP to work, but I didn't
>> succeed.
>> Because it's just for testing I'm using ftpd (on SuSE 9.0).
>> I've added it to xinetd (in /etc/xinetd.d/ftpd.conf).
>> I can connect locally via "ftp localhost", but when I try
>> to connect via the command prompt in Windows XP "ftp 192.168.1.12",
>> the IP address of the server, that fails.
>> I am able to ping 192.168.1.12.
>> I was guessing iptables blocked access to it so I did
>> iptables --flush (probably not a good thing), but it didn't
>> help either.
>> And hosts.allow doesn't contain anything, while hosts.deny only
>> contains "http-rman: ALL EXCEPT LOCAL".
>> One last thing: my client (win xp) and server (SuSE) are connected
>> via a router (192.168.1.1).
>>
>> Anyone who can tell me what I'm doing wrong?
>
> Do a "netstat -ltnpa" (I don't use Suse so you may have to take some of
> those arguments out if it complains, RH/FC's netstat takes all those
> args). This should show you the ports in a listen state, for tcp, and the
> associated processes. From this you should be able to see what
> address(es)
> ftp is listening on (port 21). Your system may only be listening on
> localhost for security reasons.
>
netstat -ltnpa gives me this:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
2302/xinetd

I guess that's ok?

SH wrote:

> Hi,
>
> I've recently setup a SuSE server on my network
> and today I tried getting FTP to work, but I didn't
> succeed.
> Because it's just for testing I'm using ftpd (on SuSE 9.0).
> I've added it to xinetd (in /etc/xinetd.d/ftpd.conf).
> I can connect locally via "ftp localhost", but when I try
> to connect via the command prompt in Windows XP "ftp 192.168.1.12",
> the IP address of the server, that fails.
> I am able to ping 192.168.1.12.
> I was guessing iptables blocked access to it so I did
> iptables --flush (probably not a good thing), but it didn't
> help either.
> And hosts.allow doesn't contain anything, while hosts.deny only
> contains "http-rman: ALL EXCEPT LOCAL".
> One last thing: my client (win xp) and server (SuSE) are connected
> via a router (192.168.1.1).
>
> Anyone who can tell me what I'm doing wrong?
>
> Thanks in advance!
>
> Kind Regards,
> Sam

I just installed MySQL on the Linux box, which went fine and I can
connect to localhost like it should. But connecting from the Win XP
client through port 3306 doesn't work either... it looks like it's
the router?
Although pinging works fine. Any more ideas?

On Wed, 14 Apr 2004 15:11:29 GMT, SH wrote:
>
> I just installed MySQL on the Linux box, which went fine and I can
> connect to localhost like it should. But connecting from the Win XP
> client through port 3306 doesn't work either... it looks like it's
> the router?
> Although pinging works fine. Any more ideas?

MySQL on linux doesn't allow remote connections by default.

Cheers,
Ingo

--
Ingo Strauch ---- Registered Linux User #227900 (http://counter.li.org/)
http://www.the-one-brack.org/

Yeah, it's listening on all interfaces. So this router you're talking
about, are you saying that your linux and xp boxes are on different subnets
? I.e. you are positive that your packets go through a router ? If so I'd
say that's where the problem looks to be. Another thing you can try is to
run (on the linux machine):

tcpdump -nn -vvv -i eth0 port 21

Then with this running try your ftp from the xp machine. See if you are
even seeing the first packet.

> netstat -ltnpa gives me this:
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> PID/Program name
> tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
> 2302/xinetd
>
> I guess that's ok?


--
"SH1-0151. This is the serial number, of our orbital gun."

Ok, I did that:
PDC:/etc # tcpdump -nn -vvv -i eth0 port 21
tcpdump: listening on eth0
18:51:08.068910 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl 128,
id 11367, len 48)
18:51:11.055858 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl 128,
id 11368, len 48)
18:51:16.992089 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl 128,
id 11369, len 48)

it takes a few seconds before this turns up, but that looks like they are
corresponding?
Both are on the same subnet:
Win XP: 192.168.1.10
SuSE: 192.168.1.12

Depending on the outcome of tcpdump I guess we can determine if it's the
router or the configuration of the server?

Thanks again!!


vom wrote:

> Yeah, it's listening on all interfaces. So this router you're talking
> about, are you saying that your linux and xp boxes are on different
> subnets
> ? I.e. you are positive that your packets go through a router ? If so
> I'd
> say that's where the problem looks to be. Another thing you can try is to
> run (on the linux machine):
>
> tcpdump -nn -vvv -i eth0 port 21
>
> Then with this running try your ftp from the xp machine. See if you are
> even seeing the first packet.
>
>> netstat -ltnpa gives me this:
>> Active Internet connections (servers and established)
>> Proto Recv-Q Send-Q Local Address Foreign Address State
>> PID/Program name
>> tcp 0 0 0.0.0.0:21 0.0.0.0:*
>> LISTEN 2302/xinetd
>>
>> I guess that's ok?
>
>

Ingo Strauch wrote:

> On Wed, 14 Apr 2004 15:11:29 GMT, SH wrote:
>>
>> I just installed MySQL on the Linux box, which went fine and I can
>> connect to localhost like it should. But connecting from the Win XP
>> client through port 3306 doesn't work either... it looks like it's
>> the router?
>> Although pinging works fine. Any more ideas?
>
> MySQL on linux doesn't allow remote connections by default.
>
> Cheers,
> Ingo
>
Hi, you mean I have to add root@% as a user or I have to change the
config file to allow remote connections?

Thanks!!
Sam

Doesn't look like you are on a router. You are on a switch (that probably
also is an 'internet' router and had the word router on it's box).
Nevertheless, your IPs are on the same subnet and this traffic is not going
through a 'router'. This may be a DNS issue, try adding a line in
/etc/hosts like:

192.168.1.10 windows

In article <62efc.71251$(E-Mail Removed)>, SH wrote:
> Ok, I did that:
> PDC:/etc # tcpdump -nn -vvv -i eth0 port 21
> tcpdump: listening on eth0
> 18:51:08.068910 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
> 3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl 128,
> id 11367, len 48)
> 18:51:11.055858 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
> 3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl 128,
> id 11368, len 48)
> 18:51:16.992089 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
> 3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl 128,
> id 11369, len 48)
>
> it takes a few seconds before this turns up, but that looks like they are
> corresponding?
> Both are on the same subnet:
> Win XP: 192.168.1.10
> SuSE: 192.168.1.12
>
> Depending on the outcome of tcpdump I guess we can determine if it's the
> router or the configuration of the server?
>
> Thanks again!!
>

--
"SH1-0151. This is the serial number, of our orbital gun."

Yes, true: it's a router with built in switch.
I've added a line to /etc/hosts, but it makes no difference.
In my FTP client, I don't even get a first FTP response: just
a connection timeout after a few seconds.

My actual setup is this:
router/switch
-> XP home client
-> hub
-> XP pro client
-> SuSe "server"
I know it's not a great setup, but the distance between de router/switch
is 25 meters and 2 cables was not an option. I wasn't using the hub, so
it was the easiest sollution.

But since pinging works fine, the network should be ok I guess.
All clients are DHCP clients, that isn't a problem?

I can't send files via MSN/kopete either, while this works between the
XP home and XP pro clients.
To me, this looks like a firewall issue on the SuSE box?



vom wrote:

> Doesn't look like you are on a router. You are on a switch (that probably
> also is an 'internet' router and had the word router on it's box).
> Nevertheless, your IPs are on the same subnet and this traffic is not
> going
> through a 'router'. This may be a DNS issue, try adding a line in
> /etc/hosts like:
>
> 192.168.1.10 windows
>
> In article <62efc.71251$(E-Mail Removed)>, SH wrote:
>> Ok, I did that:
>> PDC:/etc # tcpdump -nn -vvv -i eth0 port 21
>> tcpdump: listening on eth0
>> 18:51:08.068910 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
>> 3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl
>> 128, id 11367, len 48)
>> 18:51:11.055858 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
>> 3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl
>> 128, id 11368, len 48)
>> 18:51:16.992089 192.168.1.10.1665 > 192.168.1.12.21: S [tcp sum ok]
>> 3240863348:3240863348(0) win 16384 <mss 1460,nop,nop,sackOK> (DF) (ttl
>> 128, id 11369, len 48)
>>
>> it takes a few seconds before this turns up, but that looks like they are
>> corresponding?
>> Both are on the same subnet:
>> Win XP: 192.168.1.10
>> SuSE: 192.168.1.12
>>
>> Depending on the outcome of tcpdump I guess we can determine if it's the
>> router or the configuration of the server?
>>
>> Thanks again!!
>>
>