Internet Explorer doesn't show any login box.


Feb 17, 2004
What we need to provide our clients.

FTP access for our clients who (unfortunately) use Internet Explorer as their only FTP client:​

Behavior we want:

When is typed into a URL in explorer it should bring up a login window.​

Behavior we are experiencing:


New to cPanel and I am struggeling with this. :eek: There are scripts in multiple places and I don't understand which one is actually controling pure ftpd.


found this note on the subject but have been unsuccessfull implimenting it.

-> Internet Explorer doesn't show any login box.

IE does a very strange trick to detect whether an FTP server does accept anonymous connections or not. Basically, it connects to the server and logs in as 'anonymous'. But if you say 'no' at this point, it drops the connections with an error. You have to say 'ok, anonymous users are allowed' and then, when a dummy password ('[email protected]') is sent, you say 'ah ehm... finally... no... anonymous users aren't allowed' . Silly. To play that game, you must run pure-ftpd with the -E (non-anonymous server) and -b (compatibility with broken clients) flags. Then, the magic popup will show up. But please note that IE (and browsers at large) are usually bad FTP clients.

-> Internet Explorer doesn't want to log in. (Matthew Enger)

Check that the max number of connections (either per user or per IP) is at least 2. IE needs two connections to connect to an FTP server.​

Any thoughts and guidance greatly appreciated.


Peter :)


Mar 24, 2005
UK, England
cPanel Full URL - Is this right?

I do not remember the full login URL for cPanel, I did have it and I cannot remember it as I made a Login script, but now I need it to design something.


(I Thought it was:[email protected]+pass)
Last edited:


Well-Known Member
Jan 22, 2005
And if these clients will only or can only use IE as their FTP client there is the chance that they are not the sharpest tools in the box, in which case specifying the FTP address for use in IE as ftp://yourdomain instead of ftp://ftp.yourdomain might make things a slight bit easier for them.