Username in the address for an FTP site

Working with IIS 7.5 is a bit daunting when it comes to the new virtual hostnames for FTP servers. However, even though it seems you have configured yoru IIS 7.5 server correctly, IE, Chrome, and other browsers to not know how to handle those type of virtual host requests in the same manner that your IIS 7.5 can handle it.

The only work around currently available is to do the following, quoted:

Internet Explorer, Windows Explorer and Virtual FTP Sites issue

Both the Internet Explorer and Windows Explorer first try to connect to FTP server anonymously. If they fail, then they prompt for credentials.When FTP 7 is only configured with virtual host name based sites, these clients fail. Anonymous logon will be be rejected by server the way, that is valid as far as FTP specification (RFC 959) goes, nonetheless, it confuses the authentication sequence of those clients. Robert McMurray, noticed the problem long time ago and proposed a simple workaround in the following blog http://blogs.msdn.com/robert_mcmurray/archive/2008/12/17/ftp-clients-part-3-creating-a-global-listener-ftp-site.aspx.

To address the problem, you would need to create a GlobalListenerFtpSite, that is not configured with a host name. It has to deny anonymous access. As a matter of fact you should not allow any access to the site (leave the authorization section empty). This site will reject the anonymous logon the way that is friendly to IE and Windows Explore. Everything will then work as expected. Robert's blog entry will provide more information on the topic.

You can find out much more in-depth information from the following article and write up: Addressing the “|” separator problem for virtual FTP Sites (FTP 7.5).


I don't really understand what the real error is.

You should connect using ftp://username:[email protected]. The fact that you think that you need to pass the domain in your username doesn't make any sense to me.

But in your example you use the | in your username and your browser will try and change that to something with %. I think you should check the error logs and get back on that.