by Wickes » Sun Jul 03, 2011 11:49 am
This may be a bug or just that I don't know what I am doing. I can make a successful FTP connection to a default directory on my institutional server, but there are additional directories that I also access. These directories are not included in the path to the default directory, but require connection to the same server. I added a path to the "Initial Directory" for one of the other directories, but I get a an error after logon. If I leave the path blank I end up at the default directory. I have not found a way to see a transcript of the connection, so it is difficult to determine where the failure occurs. My guess is that UltraEdit is connecting to the default directory before calling the alternate path from the "Initial Directory". If true, then it is failing because you can't get to the other directory from the EH06 directory. Is there a way to see a transcript of the connection process? Is there a way to get the alternate path executed before it goes to the base directory?
When I use Cyberduck I can get into both directories with separate connection configurations. The connection transcript produced looks something like this this for the base directory:
230 User WESTC Logged in Successfully
NOOP
200 NOOP Command Successful
CWD /EH06/users/westc
250 Directory successfully changed to "/EH06/users/westc"
SYST
215 NETWARE Type: L8
It looks like this for the other directory:
230 User WESTC Logged in Successfully
NOOP
200 NOOP Command Successful
CWD //GS16/GS16/workgroups
250 Directory successfully changed to "/GS16/workgroups"
SYST
215 NETWARE Type: L8
To me this seems to indicate that CyberDuck has been successful because it does not allow the default directory to be entered before running the CWD command. I have no idea how that works or whether there is a way to get UltraEdit to work in a similar manner.
Any advice would be appreciated.