220 WinGate Engine FTP Gateway ready

[mv1234]

We use Wingate 5.2.2.
Although Wingate FTP service is up and running, when we try to connect to any FTP server, the only message displayed in Internet Explorer (6.1) is :
"220 WinGate Engine FTP Gateway ready" .

Could you please help us ?
Thanks in advance.

[Pascal]

Although Wingate FTP service is up and running, when we try to connect to any FTP server, the only message displayed in Internet Explorer (6.1) is : "220 WinGate Engine FTP Gateway ready" .

How are your proxies configured in IE ? Or do you use NAT that is TRd (Transparent Redirection) to the proxy ?

[mv1234]

I use the proxy settings.
For "FTP Type", I use the IP address of Wingate server and port 21.

WWW service is working fine. Its IP address is the same with FTP, while the port is 80 instead of 21.

[nicolatn1]

Hi, I have exactly the same problem with a similar cient server configuration. (on clients IE 5.5 or 6.1)
Looking for a solution, thanks in advance.

[kgoodknecht]

Although Wingate FTP service is up and running, when we try to connect to any FTP server, the only message displayed in Internet Explorer (6.1) is : "220 WinGate Engine FTP Gateway ready" .

How are your proxies configured in IE ? Or do you use NAT that is TRd (Transparent Redirection) to the proxy ?

Pascal,
I would like to find what causes this, too.
Actually, I know what causes the symptoms, and I have found a work around. It may be a bug caused by a combination of things. This happens when you click on a link to a file in an FTP site, the way I have found to stop the behavior is to:
1. Make sure IE is set to Enable folder view of FTP sites (Internet Options, Advaced tab). If you do not use Folder view IE converts FTP folders to HTML and caches the page then you cannot download the files through this page.

2. Connect to the FTP site in IE by "ftp://ftp.example.com/" then right click on the file then click choose "Copy to folder" DO NOT use "ftp://ftp.example.com/filename" If you have already done this and recieved the message, the message is in HTML and is cached as the filename, then see step 3

3. If you have already used "ftp://ftp.example.com/filename" you must close all browser windows AND clear the browser cache before you can use "ftp://ftp.example.com".

This does not seem to happen if you use NAT and do not define the Wingate FTP proxy in internet properties on the Connections Tab.

Kevin D. Goodknecht [MVP]

[mv1234]

Unfortunately the problem remais.
When I write "ftp://ftp.example.com/" immediately appears '220 WinGate Engine FTP Gateway ready'.

[kgoodknecht]

Unfortunately the problem remais.
When I write "ftp://ftp.example.com/" immediately appears '220 WinGate Engine FTP Gateway ready'.

Did you follow my instructions exactly?

You must use folder view of FTP sites.

Close ALL browser windows, go to the internet properties by right clicking on IE on the desktop and choose properties, then Empty the cache. If you try to empty the cache without closing all browser windows the page is held in memory. While in internet properties check on the Advanced tab that you have folder view enabled.

This does work it, cured my problem of getting the same message.

Best regards,
Kevin D. Goodknecht [MVP]

[Warren]

Hi To ALL of You,

This "220 Message" has shown at various times when I have been trying to link to sites to download files and I have never been able to sort it out. Some sites cause problems and others don't.

However, following on from Kevin's fix, I have now tried this with an HP site, where I needed to get an XP driver for my CD Writer. I didn't activate the FTP Folder as Kevin has suggested. My fix went like this:
Let the 220 message appear and then copy the ftp:// address from the address bar at the top of the screen. F11 to get the full Web Page Format showing.

Next go to Internet Options in Tools, then go to /Connexions/Configure LAN/Advanced Options - Tick "Use Same Proxy Server". Mine ends up as my Proxy Wingate Server on Port 86. Accept your way out and then close IE. Restart IE and paste the ftp address to the address bar. Then GO. With luck and if my instructions are understandable, you should get to the Windows File Download Menu. From there, Open or Save the file as you wish. Note that as distinct from Kevin's work around, this way, you do need the file name at the end of the ftp address. It should end up looking similar to this:

ftp://ftp.hp.com/pub/information_storag ... rw_usb.exe

That's the good news. The bad news is that you need to go back into the LAN settings and redo all of you Port Numbers because when you select the Same Server window, it removes all of the individual Ports Numbers.

This worked for me. Hope it helps the rest of you.

Good Luck, Warren

P.S. Thanks Kevin, your suggestions came just at the right time for me to solve my file download problem.

[belem]

I have had the same problem until I learned that ftp Proxy requests from the browser are treated as https. That means: Tell your browser to use the http proxy port not the ftp port (all the same) of your wingateproxy computer.
Would like to know if this helped. On my computer it works now perfect. ftp proxy is only used with ftp client programms.

Best wishes
Bernhard

[nonoghost]

Hi to All,

as Bernhard says:
For IE and FireFox, use Port 80 (or the port for the WWW) instead of 21.
For IE You can omit the number of the port in "proxy settings", not in Firefox.

Why do you use WWW Port for FTP ? I Don't Know, ask The Qbik team. ;-)

I use FTP proxy only for the Filezilla server.

Tchuss, :-)