'Access denied' on FTP command in Windows 2012

Attempting a Put command between servers and get 'Access denied'. Yet when "/" in the path are swapped for "\" it succeeds. This used to work before 2012.

The simple fix would be to just start using back-slashes, but we'd have a lot of scripts to change. And, these scripts are still used for Win 2008 servers ...

Is there a Windows/FTP setting we can change to accommodate this?
brownkm82Asked:
Who is Participating?
 
AlexPaceCommented:
Also, if you find yourself having to change a lot of script anyway you might reconsider the wisdom of using ftp.exe for important business processes since seems like basically abandonware at this point.  Consider instead using WinSCP or Robo-FTP.  Both support scripting.  WinSCP is free. Robo-FTP is not but it has actual support where you can open a ticket and get help for your specific issue rather than just posting to a forum... it also has a more powerful script language that, to my mind, is closer in syntax to windows batch files.  The best for you will depend on your needs and perhaps how hard it is to requisition new software... if you have to deal with accounting trolls .... well yuck.
0
 
AlexPaceCommented:
The scripts have forward slashes in the names of local files on a windows box?

Please give an example of a failing command.
0
 
brownkm82Author Commented:
Sorry, meant to get back to earlier.

Here's what the User wrote:

The following command fails with message 'access is denied'
put 268CHRT /output/test2

The following command is successful:
put 268CHRT \output\test2

Hope that helps,
Ken
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
AlexPaceCommented:
Run it in verbose mode and the output will indicate if the error is due to a server response or a client-side error.

put is not an FTP protocol-level verb, it is a command in the ftp.exe client that will send a PORT verb, wait for the server's response, then send a STOR verb on the control channel, wait for the server's inbound connection on the data channel, then write the file contents to the connection until EOF and wait for the server's response on the control channel.

So obviously a lot of things have to happen under the hood involving both the client and the server and just knowing access is denied doesn't tell you if the client can't access the source file or the server won't allow the file to be saved or maybe something else.... in verbose mode you can often infer what happened by looking at the last thing that actually happened in the FTP protocol-level conversation.
0
 
AlexPaceCommented:
I don't think there have been any substantial changes to ftp.exe command line client in a decade so I suspect something else like local permissions, local firewall, network firewall/proxy or somesuch issue external to ftp.exe
0
 
brownkm82Author Commented:
They ended up changed their scripts in the end. But I did pass this on to them especially the part about using something like Robo-FTP.

Thanks for all your help,
Ken
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.