A client is running an ASP.NET web site on an IIS Server (on Windows Server 2008 R2). It's a dedicated physical server, at an external host, and, for the most part, the site runs fine.
The client has noticed, however, that the web site sometimes becomes unresponsive when we are transferring files to it via FTP. We are using the built-in Windows FTP server on this box. We generally copy files up using Beyond Compare, or a simple FTP client, like WinSCP. In these cases, we are copying up .aspx pages and .pdf files, not DLLs or config file changes, so IIS should not be restarting the asp.net worker process or anything like that.
Looking at Resource Monitor while the transfer is happening shows the network utilization getting up to about 25%. CPU, memory, and disk usage are all reasonable.
Could the FTP transfer be soaking up all the bandwidth available to the server? If so, is there a way for me to limit the bandwidth that the Microsoft FTP server uses? I've looked around for information on that, and it seems like that might not be possible. I know that it can be done with, for instance, Serv-U, so I've been thinking of switching to that.
I'm not sure yet how much bandwidth the host is providing, by the way, but I'm looking into that.