Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows Server General Forum. Sign in to vote. I have a user who is having trouble copying information from one folder on an FTP site to another folder.
She is accessing the FTP site from a browser. She has Full Control over the parent folder, and I double checked She can, however, download the files she is trying to copy to her own hard drive. Then upload them back to the other folder.
Any ideas? Friday, August 22, PM. Friday, August 29, PM. Note: It actually lets you right click and copy. Lastly, I discuss the advantages and disadvantages of each different account type in the following blog that I wrote some time ago.
I would suggest reading that blog if you ever have any question as to which type of accounts you should use.
I would suggest trying out some of the walkthroughs that I have listed, and you will quickly discover that it's really very easy to create user accounts for FTP. I've been running computers for 35 years now and have set up countless desktop systems and about half a dozen Windows servers.
IIS 7. I've spent over 15 hours now trying to get this FTP server set up and it still doesn't work. There's a permissions problem somewhere as I can log in but I can't get a directory listing. But even getting to this point has required reading dozens of pages and watching many help videos all of which stop short of telling all the steps and several of which required copying and pasting command prompts over to try to configure the Windows firewall.
Telling Windows to set up and FTP is simple. Making it actually work is not. Microsoft has failed when it comes to FTP. Even the IIS. As you mentioned in your post, if you can log in but you can't get a directory listing, then more than likely you have an issue with a firewall - even if you're on the same machine.
Yes - there are additional steps beyond installing the FTP that are required to enable FTP to work through a firewall, and those security settings are there by design; the alternative is leaving your server open to attack, which is even less desirable. The reason why I chose to use the command-line in articles such as that is because of its simplified ease-of-use for end users; you could configure all of the same firewall settings through the Windows Firewall user interface, but in this particular scenario it was much, much easier to condense what might be thirty or forty user interface steps into a single command-line.
There is also one additional item to consider - which FTP client are you using? If you are using the built-in Windows command-line FTP client, then you are likely to have issues when a firewall is involved, and here's why - the built-in Windows FTP client only uses Active FTP, which is very firewall-unfriendly.
So chances are, if you're using the FTP client that ships with Windows, you may already have your server correctly configured, and it's the client that's having issues. That being said, I wrote a blog series on FTP clients where I reviewed several clients and listed what worked well and what didn't, and here are the clients that I would currently recommend using instead of Windows' built-in command-line FTP client:.
Thank you for the reply. It was not the firewall after all, it was Windows permissions on the folder where the FTP files were located. I had to manually add permissions for my Windows FTP user. Manually adding the user now allows the folders and files to display properly. I think it just reinforces the point that Windows isn't as easy as it probably should be. I still have one task to try to complete but I should probably start another thread.
It's related to this topic however because Windows doesn't easily allow me to let a user SEE the contents of the folder but NOT be able to copy them. This is very valuable in an FTP environment where you want them to be able to verify the file copied, but not allow someone else to download that file. Customer uploads private data to us for our use. They don't want others to use it, just us. Need to be able to upload and verify.
Trouble is, in Windows IIS 7. Poor decision by Microsoft. After doing a LOT of research and spending a couple of days trying different things I finally concluded that it could no longer be done. It worked great in earlier verisons of Windows Server but I was unable to get it to work with Windows Server I then installed Filezilla Server because in researching above so many people seemed happy with it. It installed quickly, easily, and it's worked perfectly.
It has worked so well in fact that I felt a bit stupid for having wasted so much time and effort trying to get Windows Server to do this. I should also mention that setting up a user in Filezilla is independent of setting up a Windows user so you have less risk because permissions of everything else is not touched. All those FTP customers don't have Windows user names at all. This program works better than FTP ever has on any version of Windows. Being an IIS forum this comment may get deleted.
I don't know. I do know that I tried my best to solve this solution with Windows and after investing much time and effort I learned there was a better way. I've been using it since and am very happy with it. Each time I use it I think about my efforts to get IIS to do the same thing and remember the frustration.
I do not own it, have no involvement with it other than mentioned above. I'm just a very happy user. Thanks, cdsJerry - rest assured, your comments won't be deleted; hearing problems from customers is part of the reason for why these forums exist. In any case, that is why I posted the instructions for setting up authentication for IIS Managers earlier in this thread - I prefer not to hand out Windows user accounts if I don't need to.
You are correct, however, that the FTP service does not set physical ACLs when you add users to the authorization settings; IIS has never set physical ACLs on the file system when you make changes to authorization settings, and there is a long list of reasons why this is the case. Open the properties for the root directory that holds your Web content. This can cause unnecessary data to be uploaded to your Web server.
Right-click the remaining folders, click Properties , and then click the Security tab. Click to clear the Allow inheritable permissions check box, click Copy , and then click OK. The following table lists the permissions that will be applied when you follow the steps in the "Disable inheritance in system directories" section.
This table is for reference only. To apply the permissions in the following table, follow these steps:. Click the Security tab, and then click Advanced.
Double-click Permission , and then select the appropriate setting from the Apply Onto list. Click Start , click Run , type regedt32, and then click OK. Do not use Registry Editor because it does not let you change permissions in Windows Click to clear the Allow inheritable permissions from parent to propagate to this object check box, click Copy , and then remove all users except:.
Click to clear the Allow inheritable permissions from parent to propagate to this object check box, and then remove all entries except:. The following table lists the permissions that will be applied when you follow the steps in the "Grant permissions in the registry" section.
Click Start , click Settings , and then click Control Panel. Select and then click Remove for any user who is not listed in the table. Add any user who is not listed. To do this, click Add , and then select the user in the Select Users or Groups dialog box. Note that because a domain controller policy overrides the local policy, you must make sure that Effective Policy Setting matches Local Policy Setting. The following table lists the permissions that will be applied when you follow the steps in the "Grant rights in the Local Security Policy" section.
0コメント