FTP with proxy server

I really need some help. I am trying to access an FTP site outside of my firewall. I can use the OpenURL to make a connection but this offers limited functionality. I would prefer to use the Execute. The proxy server has an address of: web."myproxyserver".com. I have been using the internet transfer controls to try to specify the proxy server (i.e. Inet1.Proxy = "ftp=web.myproxyserver.com:21" followed by the .AccessType = icNamedProxy. Still no luck, I get stopped at connecting everytime with a Run-Time error of 35754 (Unable to connect to remote host). Can someone please help me!!!!!

Do you have to supply a username and password to get outside the firewall? We do at my company and we send the username and password for both the proxy and ftp server in one line like this:
ProxyUID@FTPServerUID
ProxyPWD@FTPServerPWD

I admit, we aren't using the inet control, but we do build a bat file to go out and download a file from a proxy server, using this format, and then execute the bat file. It works fine for us.

Give it a try at the DOS prompt to test it.

Hope this applies/helps,
John

John Pirkey
MCSD
www.ShallowWaterSystems.com

I don't have to supply a username and password and I can do everything I need to at a DOS prompt. That is the odd thing. At the DOS prompt, I type:

ftp> open web."myproxyserver".com 21

This connects me to the proxy and then I am prompted for a User which I then would enter something like [email protected] which establishes a connection. From there, I am home free as far as being able to access needed files, get a directory listing, etc. But I really need to be able to do this through VB6 because it is a key part of my program. Without it, I am sunk. Any ideas???

hi!,

i am facing the same problem.if you have found the solution i would be grateful if could help me on it.

thanks.

I've actually moved onto something better than Inet since I encounterd a "round robin" problem in which the proxy server was doing load balancing between two servers. I modified the FTP code from VBNet(http://www.mvps.org/vbnet/) which uses API calls. It has been more reliable and easier to implement than the INET control.