Hi Amos, Thanks for your response. Unfortunately, the problem persists. I could forward the problem to a VMware forum. Cheers, Farkas On 24 August 2012 09:46, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On 22/08/2012 11:21 p.m., Farkas H wrote: >> >> Hi all, >> >> I have installed a Squid proxy (2.7 windows) in a VMware (8.0.4) with >> NAT networking [1]. >> The proxy is working inside VMware correct but cannot be accessed from >> the host network. >> I think I've to use port forwarding in VMware and tried these settings, >> - port forwarding in VMware [2], >> - host-browser [3], >> - squid.conf [4]. >> >> I hope someone can help me and I appreciate any advice. > > > Port forwarding NAT is only required when the networks have overlapping IP > ranges and require NAT to fix that problem. Regular routing should work > fine. > > >> >> Cheers, >> Farkas >> >> [1] >> network: vmnet8 >> subnet: 192.168.88.0 >> mask: 255.255.255.0 >> gateway: 192.168.88.2 >> ip: 192.168.88.128 >> >> [2] >> Port forwarding in VMware (version 8.0.4): >> -- >> host port: 3128 >> type: tcp >> vm: 192.168.88.128:3128 >> allow active FTP >> allow any org. unique identifier >> config port 0 (?) >> >> [3] >> Host-Browser settings: >> -- >> http-proxy: localhost >> port: 3128 > > > Browser is connecting to localhost (127.0.0.1 or ::1) not one of the 192.* > ranges. This might be the probem. It should be pointing at an IP:port of the > proxy. > > >> [4] >> squid.conf (version 2.7) >> -- >> acl all src 0.0.0.0/0.0.0.0 >> acl manager proto cache_object >> acl localhost src 127.0.0.1/32 >> >> # host >> acl MyNetwork src 192.168.2.120-192.168.2.199/255.255.255.255 >> # vm >> acl MyNetwork src 192.168.88.128-192.168.88.254/255.255.255.255 > > > You don't need the 255.255.255.255 bits here. > > >> >> http_access allow MyNetwork >> http_access allow localhost >> http_access deny all >> >> icp_access deny all >> ... > >
