Skip to contentSkip to conversation

site not seen through squid

DISCUSSION Payal Rathod 2 participants 5 messages Feb 16, 2005 – Feb 17, 2005

lore
Share & tools
lore
#0 lore raw

Hi,
My friend has a sharepoint (don't know what it is) server in her DMZ at 10.10.10.3. She can access that server from outside world by giving its public IP in browser. She cannot access it via her squid proxy inside the LAN. But when she removes proxy settings and gives, iptables -I FORWARD -s 192.168.10.7 -j ACCEPT
she can access it. When I say access here it means that in all cases she can see IIS page but it is giving authorization failed from inside LAN. When she removes proxy settings and gives iptables rule above she is presented with a username-password box which is not seen via squid internally.
Strangely if I am on the squid/gateway/firewall machine and still using proxy I can see the authorization box. Can someone give us both some hints to proceed?

With warm regards,
-Payal

#1 lore raw
Quoted 6 lines · Payal Rathod

Hi,
My friend has a sharepoint (don't know what it is) server in her DMZ at 10.10.10.3. She can access that server from outside world by giving its public IP in browser. She cannot access it via her squid proxy inside the LAN. But when she removes proxy settings and gives, iptables -I FORWARD -s 192.168.10.7 -j ACCEPT

Quoted 8 lines

she can access it. When I say access here it means that in all cases she can see IIS page but it is giving authorization failed from inside LAN. When she removes proxy settings and gives iptables rule above she is presented with a username-password box which is not seen via squid internally.
Strangely if I am on the squid/gateway/firewall machine and still using proxy I can see the authorization box. Can someone give us both some hints to proceed?

my guess is that your friend is using transparent redirection to the squid proxy and not explicit proxying (i.e. configuring the proxy in the web browser). HTTP AUTH does not work through a transparent proxy. easiest solution would be to bypass the transparent redirect for requests to the sharepoint server by adding an ACCEPT rule prior to the REDIRECT:

  iptables -t nat -A PREROUTING -i $INT_IF -d 10.10.10.3 --dport 80 \
    -j ACCEPT

  iptables -t nat -A PREROUTING -i $INT_IF --dport 80 \
    -j REDIRECT --to-port 3128

-j

--
"Operator! Give me the number for 911!"
--The Simpsons

#2 lore raw
Quoted 3 lines · Jason Opperisano

my guess is that your friend is using transparent redirection to the
squid proxy and not explicit proxying (i.e. configuring the proxy in the

No it is not transparent proxy. She has it configured in all browsers in her office.
Any clues?

With warm regards,
-Payal

#3 lore raw
Quoted 8 lines · Payal Rathod
Quoted 3 lines · Jason Opperisano

my guess is that your friend is using transparent redirection to the
squid proxy and not explicit proxying (i.e. configuring the proxy in the

No it is not transparent proxy. She has it configured in all browsers in her office.
Any clues?

then my next guess is that the sharepoint server uses NTLM authentication, and the problem is:

http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.14

which links to:

http://support.microsoft.com/kb/q198116/

punch line: you can't put a proxy between a client and a server that does NTLM authentication

again--you'll have to bypass the proxy for this destination server (or configure the web server to use another authentication method).

-j

ps - this is starting to sound more like a squid question than a netfilter question.

--
"Kids, you tried your best and you failed miserably. The lesson is,
never try."
--The Simpsons