unable to connect FTP site behind proxy

Starting with the question of "What changed?" look at what the clients are doing.

If nothing at all changed on the client machines, the problems are in the Proxy. Are all of the proxy choices on the server turned on and working? Are there any event log entries which suggest that something is broken? Did the IP number of the server change?

From what you describe, you have some stations with valid addresses on the same physical segment as other stations with internal addresses. Do you havea static route pair in RRAS between the two? You probably need one.

If you have an old route printout of RRAS, make sure that you restored all the static routes.

Good luck.

Make sure the client machines IP addresses are in the Proxy server's LAT (local address table), otherwise the proxy won't forward the ftp requests onto the Internet.

If this dosen't work, reload the proxy client on the workstation. I have found times when re-installation of the client was necessary when the Proxy server was reinstalled.

Good luck.

Two things I would check.

1. Like previous answers, make sure internal clients' ip range is in the LAT of proxy. Make sure you reconstruct the LAT. Remember it takes six hours (as I recall) for the servers' LAT to distribute down to the clients. You don't need to set gateway on clients, nor the internal interface of the proxy server.

2. On the client, go to WSP client in the control panel and hit update. If anything other than success message, reinstall the proxy client. Map to \\proxyserver\mspclnt from the client and install.

Two more suggestions.

A. I hope you mentioned IIS 2.0 with Proxy 2.0 by mistake. I don't even think you can install Proxy 2.0 on IIS 2.0. I think it needs at least IIS 3.0 or better yet IIS 4.0.

B. The whole point of having a proxy is to translate private addresses to public ip addresses. If you are using public ip on the clients, this defeat the purpose of having a proxy.

I've never used IIS 2.0, but in 4.0 and above, it is possible to have the web site listening to public addresses or private addresses or both.

Since proxy 2.0 intenerates so tightly with IIS, this may be worth considering...

Hi sudeep, thsi a clear case of rights not being allocated to your users who have I assume MSP client on the PCs. In your Proxy Server, check if all 6 Services are running, also in "Winsock" & "Socks" Properties for "Permissions" for users in FTP.
A better idea would be to grant unlimited acces to all protocols to the administrator of your NT Domain & Proxy. then from your PCs, loginas NT Admin to Domain & try checking FTP. Make sure you have SP6.
Akash

This question was auto closed due to inactivity