The task is to move several files to a remote machine. Currently this is a Windows XP to Windows XP scenario. The production process is to move files from Windows XP to a Unix box. I have set up a ftp server on one XP box. I am making the correction. However, I am not able to create a directory. I have ensure the user on the ftp server has upload and down load privileges.
Did you try ftp'ing manually and doing the mkdir command?
Did you try it out XP to UNIX? You may be troubleshooting things that will be irrelevant to your final solution and then have other issues in production.
Is remotedir really something like "directory_name" or is it a series of directories like "some/remote/dir"?
I'm doing XP to UNIX and it worked fine, see output below (don't be so frugal posting one snippet from your error output, context might help). Tried with remotedir "directory_name" and "some/remote/dir". I'm not sure how the separator works it doesn't seem to affect my mkdir. I did try "some\remote\dir" and it created one directory in UNIX named "some\remote\dir", that's why I ask what your remotedir is really like.
Thank you for answering my question and offering me some good advice.
I got off the Windows XP to Windows XP scenario and got on to the Windows XP to UNIX scenario. It save me the time and effort of figuring our why I was not able to manually send files using a ftp command from the command window to another Windows XP box.
The remotedir is the directory on the remote box. In Windows XP to UNIX scenario, it was the UNIX box.
The good news is I was able to make the connection and create the directory!
The bad news is now I am tackling the error
I think what this is telling me is the UNIX box does not have the right configuration involving ANT, i.e. jakarta-oro-2.0.8.jar
AGAIN, I am indebted to you for your assistance! One simple question had me digging to be sure I had my configuration correct. I discovered the jar file was not in the correct directory. Once I moved it, I re-ran the ant script and it all worked.......