Upgraded to 6.1 - FTP connectivity gone?

[chakotha]

Hi

We upgraded our Wingate Server and Clients to version 6.1 yesterday.

Now it seems we cannot connect with any outside server using FTP. We have been trying to get access with WS_FTP and via Internet Explorer to anonymous public FTP sites.

Any ideas at all?

TIA

[adrien]

hi

How are your FTP clients connecting?

they aren't using SOCKS are they?

We tested extensively with

NAT (intercepted or not)
SOCKS (not intercepted - doesn't work for SOCKS if you intercept)
WinGate Client
FTP proxy directly.

Which method are you using for your FTP clients to connect to the servers?

Regards

Adrien

[chakotha]

Thanks for the reply.

By trial and error we determined that the FTP Proxy settings Sessions Configuration has to have the transparent proxy check box intercepting connections made via ENS the WinGate Client or SOCKS unticked.

If this is ticked then our FTP client does not connect.

Is there a downside to this?

[adrien]

THe only downside is that it then doesn't go through the FTP proxy.

If you aren't scanning on this proxy, or enforcing policies, then there is no downside.

However we tested extensively with interceptions.

there is an issue with SOCKS which I don't think can be got around (due to the way SOCKS works), but it should work fine if your clients were just using normal NAT, and it was being intercepted.

Or were you using the WinGate client?

[cristdom]

I'm having the same issue.

When trying to connect in IE for example to ftp://ftp.software.ibm.com/common/ssi/r ... 74USEN.PDF I get the following message "220 WinGate Engine FTP Gateway ready"

The FTP Proxy Service has an everyone policy accepting all assumed users.

Thanks.

[genie]

IE, AFAIR, expects normal HTTP proxy to be used for FTP proxying - not the standard FTP one.

[cristdom]

What do you mean exactly? How can I resolve it?

[genie]

What proxy settings do you have in IE? Does it use Wingate HTTP proxy all over, for all the protocols?

[cristdom]

My IE proxy setting are:

HTTP: 192.168.168.200.1 Port 3128
HTTPS: 192.168.200.1 Port 3128
FTP: 192.168.200.1 Port 21

As you can see I'm using FTP Proxy Server to FTP connections.

Thanks.

[adrien]

Hi

Web browsers speak the wrong language when it comes to FTP proxying.

the port number needs to be the same as the HTTP one - it actually makes an HTTP request for an FTP resource.

Normally it's even easier to just remove proxy settings in the client and have the FTP connection intercepted by WinGate.

Adrien