General discussion

Locked

Proxy Server

By Chris Joseph ·
I am trying to get my Web Proxy and Winsock proxy to work together. Currently Winsock is handling everything and I would like Web Proxy to handle http and ftp requests, so we can build a cache and improve performance. Anyway I have had absolutely noluck with this.

The lat is correct, only contains internal addresses. Everything seems fine but if I try to set IE to use Proxy port 80 it does not work.

I printed out a netstat on the proxy server. Out of the two NICS on the machine only the external is listening to port 80. Shouldn't the internal NIC be doing the same.

Any help on this topic would be greatly appreciated. Please give me anything

Thanks.

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Proxy Server

by it In reply to Proxy Server

Your proxy server should have a port of its own listening for requests. You need to configure your ftp client to use the proxy server. In Internet Explorer, this would be as simple as confirming in Tools>Internet Options>Connections>LAN Settings>Advanced that the FTP line contains the IP Address and port number of your proxy server. This presumes that you have not adjusted the proxy server to only address web caching and you have not changed the server to listen to port 80.

Programs such as CuteFTP and WS_FTP should also permit configuring usage of a proxy server.

My proxy server is Squid running under RedHat 7.0. I currently cache web and ftp requests through Squid.

Collapse -

Proxy Server

by Chris Joseph In reply to Proxy Server
Collapse -

Proxy Server

by McKayTech In reply to Proxy Server

The first answer is pretty good and I only wanted to add that the conventional port for the internal side of a proxy server is 8080 (although it could be anything you want).

paul

Collapse -

Proxy Server

by Chris Joseph In reply to Proxy Server
Collapse -

Proxy Server

by jvohs In reply to Proxy Server

If you have the Proxy client installed on the clients, access control will be applied using the Winsock proxy access control. Caching for web requests and port 80 ftp will be handled by the Web proxy service. Make sure that the default website is running on the proxy server. Verify that it is running on port 80, if not change the client to match the default web site's port. Make sure the default website is set to anonomous access for testing purposes at least. Disable access control on both the Web proxy and the Winsock proxy. Disable packet filtering. Can you get out now? If so start by using default packet filters. I would also recommend custom filters. Sometimes the predefined filters break packet filtering. If non of the above does any good, remove sp1 for proxy (reboot), remove proxy (reboot), reinstall the current NT service pack (reboot). Make sure the event viewer comes up clean. IIS must be healthy for Proxy. Then reinstall proxy, sp1 for proxy, and finally the NT service pack again. Good luck.

Collapse -

Proxy Server

by Chris Joseph In reply to Proxy Server

Unclear. Forget about ftp. See message.

Collapse -

Proxy Server

by Chris Joseph In reply to Proxy Server

Forget I mentioned FTP, Really it is just HTTP traffic I want to have routed and cached through Web Proxy, currently it goes through winsock proxy. That is where the problem is, I can not make it go through Web Proxy.

Collapse -

Proxy Server

by jvohs In reply to Proxy Server

If the browser isn't configured it WON'T go through web proxy. Try using automatic browser configuration for the proxy client. Configure this on the server. Did you double check the Default Web site? Has it been changed? Proxy will not run correctly if the default web site is changed too much. The port on the default web site must match the port on the client. If you are web publishing, on port 80, the default web site was probably changed. Yes, some of the packet filters DO break the ipfilter driver. Can you get out without filtering? About cahcing, it must be NTFS, 100mb base + .5mb per user to start with recommended. Check permissions on the cache directory and drive if necessary. Do you get any error messages? Event ID's??? This all helps.

Collapse -

Proxy Server

by Chris Joseph In reply to Proxy Server

I know about the browser. The only reason it is not configured to use the proxy is because it doesn't work that way right now.
As for the default web site, there is not a web site that is called "default" there are two web sites on the server, ourbackup company site and the admin site, the admin site is stopped. So I would guess that the other site is the default.

What do the settings have to be on the default web site to make web proxy work?

Collapse -

Proxy Server

by tech84 In reply to Proxy Server

The results you get from netstat will vary depending upon how you have Proxy Server set up. It appears that your backup company site is indeed your "default" web site. If you go to the properties for that site, and look at the "Web Site" tab, whatever the ip address is set to will be the NIC that is listening on port 80. If you have it set to "All Unassigned", then you'll get both, or one or the other NICs listening on port 80. I think it should be set for the internal NIC, or "All Unassigned." At least that's the only way I can get mine to work properly. Now, of course the TCP Port should be set to 80 here also.

Now, you've probably already got this part set right, but when you go into the Web Proxy properties and click on the Client Configuration button, do you have the "Automatically configure Web browser during client setup" box checked? If so, you'll need to have port 80 selected there too.

That's about all I can think of. Hope this at least sheds some light on something.

Mike

Back to Windows Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums