Wht can't I get a directory listing on my PC hosted FTP from my Amiga?

[DDNI]

Hi all,

I have my A1200 connected to my PC Ethernet port via a wired PCMCIA card.
My PC accesses the net via a wireless card.
I use ICS to share the wireless internet connection with the Ethernet port

I can browse the web from the Amiga.
I can nearly connect to my FTP server (Filezilla Server) which is hosted on 192.168.1.66 port 21.

But when AmiTradecenter is connecting to the FTP server it cannot complete a directory listing. It seems to be trying, but it does not complete the list.

Filezilla output is this.

000005)21/03/2011 12:03:26 - (not logged in) (192.168.1.66)> Connected, sending welcome message...
(000005)21/03/2011 12:03:26 - (not logged in) (192.168.1.66)> 220-FileZilla Server version 0.9.37 beta
(000005)21/03/2011 12:03:26 - (not logged in) (192.168.1.66)> 220-written by Tim Kosse (Tim.Kosse@gmx.de)
(000005)21/03/2011 12:03:26 - (not logged in) (192.168.1.66)> 220 Please visit http://sourceforge.net/projects/filezilla/
(000005)21/03/2011 12:03:26 - (not logged in) (192.168.1.66)> USER ddni
(000005)21/03/2011 12:03:26 - (not logged in) (192.168.1.66)> 331 Password required for ddni
(000005)21/03/2011 12:03:26 - (not logged in) (192.168.1.66)> PASS ****
(000005)21/03/2011 12:03:26 - ddni (192.168.1.66)> 230 Logged on
(000005)21/03/2011 12:03:26 - ddni (192.168.1.66)> CWD /
(000005)21/03/2011 12:03:26 - ddni (192.168.1.66)> 250 CWD successful. "/" is current directory.
(000005)21/03/2011 12:03:26 - ddni (192.168.1.66)> PWD
(000005)21/03/2011 12:03:26 - ddni (192.168.1.66)> 257 "/" is current directory.
(000005)21/03/2011 12:03:27 - ddni (192.168.1.66)> PORT 192,168,0,2,48,12
(000005)21/03/2011 12:03:27 - ddni (192.168.1.66)> 200 Port command successful
(000005)21/03/2011 12:03:27 - ddni (192.168.1.66)> LIST
(000005)21/03/2011 12:03:27 - ddni (192.168.1.66)> 150 Opening data channel for directory list.
(000005)21/03/2011 12:03:27 - ddni (192.168.1.66)> 226 Transfer OK


My sytem is setup like this.

Amiga (miamiDX)
IP 192.168.0.2
Netmask 255.255.255.0
Gateway 192.168.0.1
DNS 192.168.1.254

PC Ethernet
IP 192.168.0.1
Netmask 255.255.255.0
GAteway 192.168.1.254

PC
IP 192.168.1.66
Netmask 255.255.255.0
Gateway 192.168.1.254

I have no third party firewalls running. Windows XP firewall is up, stopping it makes no difference.

I am on BT infinity.

[rare_j]

Your setup sounds ok. Do you get no list at all, or a partial list? Does the ftp client hang, or just do nothing? Is filezilla set up to mimic unix paths? Can you try another ftp client? How about something like amiftp or ncftp?

[DDNI]

Hi, amiftp hangs when trying to create a listing.

[Doc Mindie]

Tried a browser? use FTP://192.168.0.2:21 in iBrowse or whatever you use... worth a try

Check both active and passive connections on the Amiga FTP-client

Not sure why you're gateways and your DNS are different?

[Mr B]

Tried switching active / passive mode on the client? It shouldn't be the cause since it claims

(000005)21/03/2011 12:03:27 - ddni (192.168.1.66)> PORT 192,168,0,2,48,12
(000005)21/03/2011 12:03:27 - ddni (192.168.1.66)> 200 Port command successful

But just to make sure.
The next option i would look at is that you simply haven't set up FileZilla right. Try 127.0.0.1 as "target" on the host system (PC) and see what you get there when you try to connect to the FTP. If there is a misconfiguration with the virtual filesystem you should get the same as you get on the Amiga, if not, then it's a connectivity issue.
B!

[vk3heg]

Originally Posted by DDNI

I have my A1200 connected to my PC Ethernet port via a wired PCMCIA card.

Amiga (miamiDX)
IP 192.168.0.2
Netmask 255.255.255.0
Gateway 192.168.0.1
DNS 192.168.1.254

PC Ethernet
IP 192.168.0.1
Netmask 255.255.255.0
GAteway 192.168.1.254

Your using a cross over cable between the pc and Amiga?

If so then don't have a gateway setup on either, plus you have two different gateway ip's set.

When using a cross over cable or even just a hub with two pc's you don't need to set a gateway, as the two are on the same network (subnet).

[Zetr0]

@DDNI

my friend, just try logging into the FTP host on the PC with another PC, say a laptop or something.

I had a similar issue with an XBox and the File server a few weeks back, to fix the problem I just updated the FTP host on the File server.

Since both the host and client are connecting, this is likely to be a software setup issue rather than a connection issue.


although saying that, is it possible that your router might be dropping some types of data packets?, I would be surprised as this is an internal network, but just double check =)

[DDNI]

Hi all, many thanks for the replies.

Using Aweb to browse to my ftp results in the same issue, the directory is not listed.

I am using a cross over cable.
Removing the gateway on the amiga side results in my Amiga web access being lost and no improvement with FTP

Filezilla displays my FTP as being on 127.0.0.1
I had been telling Amitradecenter to connect to 192.168.1.66. I decided to try 192.168.0.1. It sees the FTP on both of these ip addresses but still cannot creat the listing (this is with and without a gateway listed)

I tried a normal non cross over cable but that resulted in no connection at all.

I am stumped!

@zetr0 I just tried connecting to my FTP from my PC using firefox. It connected but did not give a directory listing. Using filezilla client to connect results in the same issue. There must be a problem with filezilla server settings..


@TCD post thief

Tried a different FTP server (xlight) I still get an empty listing.

[cosmicfrog]

Amiga (miamiDX)
IP 192.168.0.2
Netmask 255.255.255.0
Gateway 192.168.0.1
DNS 192.168.1.254

these are on 2 diffrent networks
try setting DNS to 192.168.0.1

hope it works for you

[thomas]

Originally Posted by cosmicfrog

Amiga (miamiDX)
IP 192.168.0.2
Netmask 255.255.255.0
Gateway 192.168.0.1
DNS 192.168.1.254

these are on 2 diffrent networks
try setting DNS to 192.168.0.1

hope it works for you

The DNS is not involved in retrieving a directory listing from an already connected FTP server. DNS query is only done once during connect to get the IP address for a name. Once the IP address is known, the DNS is no longer used. So this cannot be the solution.

More than that, your tip is not right, because the PC is not running a name server, so using 192.168.0.1 as a DNS cannot work. Using the real DNS as DNS address is right, even if it's on a seperate network. Your ISP's DNS is not on your private network, either, but it works nevertheless.

As another PC cannot retrieve a directory listing from the FTP server, too, it clearly points towards a mistake in the FTP server configuration.

[DDNI]

I "think" that I have fixed it....

I changed the DNS server in MiamiDX database to 192.168.0.1
So far so good, I can get a directory listing

[Mr B]

Originally Posted by DDNI

@zetr0 I just tried connecting to my FTP from my PC using firefox. It connected but did not give a directory listing. Using filezilla client to connect results in the same issue. There must be a problem with filezilla server settings..

This would point in the direction of a configuration issue, usually with the virtual filesystem Filezilla uses. But it doesn't fit with:

Originally Posted by DDNI

I "think" that I have fixed it....

I changed the DNS server in MiamiDX database to 192.168.0.1
So far so good, I can get a directory listing

Best of luck, keep us updated ;- )
B!

[cosmicfrog]

I see where you are comeing from thomas I think, blood net works heheheh
but 192.168.xxx.xxx are all local nets I know that at least