I am having an odd problem where my FTP connection is aborted when core ftp issues the LIST command after a succesful login to my FTP server. The problem only occurs when I use the HOST NAME rather than the IP ADDRESS to connect. When I use the IP ADDRESS of the server the CWD / command is issued BEFORE the LIST command and everything is succesful. When I connect via HOST NAME the CWD / command is not issued and LIST subsequently fails. I've tried using CWD / in the pos-login command script but no success. Why is CORE-FTP LE issuing different sequence of commands? Due to permisioning reasons, my FTP client must issue the CWD / command before issuing the LIST command. Ive provided output of each attempt below.
When Connecting Via HOST NAME(Fail):
220 ***
USER ***
331 Password required for ***.
PASS ***
230-Downloading from this site indicates implicit
230-compliance to the terms set by ****
230 User *** logged in.
SYST
215 UNIX Type: L8
PASV
227 Entering Passive Mode (##,##,##,##,##,##)
LIST
ABOR
QUIT
Connecting Via IP ADDRESS(Succesful):
220 ***
USER ***
331 Password required for ***.
PASS ***
230-Downloading from this site indicates implicit
230-compliance to the terms set by ***.
230 User *** logged in.
SYST
215 UNIX Type: L8
CWD /
250 CWD command successful now (/)
PASV227 Entering Passive Mode (##,##,##,##,##,##)
LIST
150 Opening BINARY connection for /
226 Transfer complete.
QUIT
221 Closing connection - goodbye!
Thank You for your help!
Odd login sequence causing FTP connection to be aborted.
BTW, I installed Core FTP on another machine and it works fine. I'm guessing there is an option set somewhere thats screwing things up. The original machine was also upgraded from a previous version of CORE FTP maybe somthing carried over from the old version. I tried the trial version of CORE FTP pro on the original machine and the same problem is there. Both machines are running identical version OS's and patch levels (W2kprofessional)