Your best friend for file transfer.Fetch
Fetch 4.01 dont work with Guildftpd (4 posts)
- Started 13 years ago by mhe
- Latest reply 13 years ago from mhe
I have a Win2000 server running Guildftpd (www.guildftpd.com), no other client is having troubles connecting. The server is setup to work both passive and active.
Still people using fetch 4.01 is having problem loging in, it actually works with fetch 3.0.
This is what is happening.
[This message has been edited by mhe (edited 04-16-2002).]
I think i might know why this is happening now.
Connecting to alloffset.mine.nu port 21 (02-04-15 21.14.44)
220-GuildFTPd FTP Server (c) 1997-2002
220 Please enter your name:
Right now everthing is stalled and i get the error msg www.mhe.mine.nu/pictures/fetch.jpg
Isnt the ftp client supposed to send out a USER command? I think it might be that the ftp server dont understand the ADAT command and ignores it (dont respond at all) so fetch is still waiting for the server to respond something?
Couldnt fetch be made so if you choose to not use any encryption (Kerberos or
GSS). Fetch should start with USER and if you choose to use one of the above encryptions it starts with ADAT..
Jim Matthews Administrator
You are right that the ADAT command is the problem. FTP servers are supposed to ignore commands that they do not support, but GuildFTPD appears to be broken in this regard.
You can tell Fetch to not send the ADAT command by running this AppleScript (you only need to run the script once):
tell application "Fetch 4.0.1"
set dont send ADAT" to true
Im not very familiar with Mac or MacOS.. How do i go about executing this script?
I couldnt find anything in fetch itself so i assume i should do this in the OS somewhere.
Just out of curiosity, why should fetch send the "ADAT" command even though im telling it to not use any security/crypt?
- Page 1
This topic has been closed.