Re: [squid-users] Certain header not authenticating
Hey, I am running squid/squidGuard with NTLM authentication. Everything works perfectly, except there is a site that some employees use for interactive training. It seems when these employees go to this site they are continually prompted for username/password with wpad.domainname.com as the realm. After investigating, the useragent log is showing this: 192.168.12.102 - - [15/Feb/2006:15:30:49 -0500] GET /wpad.dat HTTP/1.1 200 251 - NSPlayer/9.00.00.2980 It seems that the NSPlayer header is somehow not retrieving the wpad file correctly? If the users click cancel nothing happens - they can continue, but it pops up when they click to go to the next page. This is a major annoyance for some users, and has become a headache for me. I haven't explicitly set anything in squid.conf to only allow certain headers, im not even sure if you can. I have searched hell and high-water, but to no avail. Does anyone have any ideas? - WPAD is normally used for automatic proxy detection in IE. - I don't understand why the remote webserver , would offer a WPAD.dat files for 'internet users', that doesn't make sense. - The remote webserver may be broken. M.
[squid-users] Re: [Bulk] Re: [squid-users] Certain header not authenticating
My squid server has apache on it as well. The wpad.dat (and proxy.pac) is on the squid/apache server. The only time this prompt appears is when users are using sites with the NSPlayer/9.00.00.2980. I'm getting the header from the squid useragent.log file. The prompt is attached. The squid prompt box asks for the domain name right? Guess I may be barking up the wrong tree here. - Original Message - From: Mark Elsen [EMAIL PROTECTED] To: Terry Dobbs [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Sent: Monday, February 20, 2006 6:27 AM Subject: [Bulk] Re: [squid-users] Certain header not authenticating Hey, I am running squid/squidGuard with NTLM authentication. Everything works perfectly, except there is a site that some employees use for interactive training. It seems when these employees go to this site they are continually prompted for username/password with wpad.domainname.com as the realm. After investigating, the useragent log is showing this: 192.168.12.102 - - [15/Feb/2006:15:30:49 -0500] GET /wpad.dat HTTP/1.1 200 251 - NSPlayer/9.00.00.2980 It seems that the NSPlayer header is somehow not retrieving the wpad file correctly? If the users click cancel nothing happens - they can continue, but it pops up when they click to go to the next page. This is a major annoyance for some users, and has become a headache for me. I haven't explicitly set anything in squid.conf to only allow certain headers, im not even sure if you can. I have searched hell and high-water, but to no avail. Does anyone have any ideas? - WPAD is normally used for automatic proxy detection in IE. - I don't understand why the remote webserver , would offer a WPAD.dat files for 'internet users', that doesn't make sense. - The remote webserver may be broken. M. -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date: 2/17/2006 attachment: prompt.JPG No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date: 2/17/2006
Re: [squid-users] Re: [Bulk] Re: [squid-users] Certain header not authenticating
On 2/20/06, Terry Dobbs [EMAIL PROTECTED] wrote: My squid server has apache on it as well. The wpad.dat (and proxy.pac) is on the squid/apache server. The only time this prompt appears is when users are using sites with the NSPlayer/9.00.00.2980. I'm getting the header from the squid useragent.log file. The prompt is attached. The squid prompt box asks for the domain name right? Guess I may be barking up the wrong tree here. - Note also; that if the remote webserver uses NTLM, things won´t work either , as this protocol is not proxyable. M.
[squid-users] Re: [Bulk] Re: [squid-users] Re: [Bulk] Re: [squid-users] Certain header not authenticating
Well, NTLM authentication is working perfectly for users accessing every site except for a claritynet training site. I am able to report via SARG using userid's, and restrict sites using squid-guard. There isn't any authentication setup on the webserver, its only use is to view SARG reports, SARG Realtime, and serve the wpad.dat file. Anyone (internally) can access these pages. The part I don't understand is why when a user uses a page with the NSPlayer header it gives me the prompt. I'm not sure if it is squid giving me the problem, or Apache. I suspect it may be Apache, so I will look into that if nobody has encountered similar issues. - Original Message - From: Mark Elsen [EMAIL PROTECTED] To: Terry Dobbs [EMAIL PROTECTED] Cc: squid-users@squid-cache.org Sent: Monday, February 20, 2006 9:35 AM Subject: [Bulk] Re: [squid-users] Re: [Bulk] Re: [squid-users] Certain header not authenticating On 2/20/06, Terry Dobbs [EMAIL PROTECTED] wrote: My squid server has apache on it as well. The wpad.dat (and proxy.pac) is on the squid/apache server. The only time this prompt appears is when users are using sites with the NSPlayer/9.00.00.2980. I'm getting the header from the squid useragent.log file. The prompt is attached. The squid prompt box asks for the domain name right? Guess I may be barking up the wrong tree here. - Note also; that if the remote webserver uses NTLM, things won´t work either , as this protocol is not proxyable. M. -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date: 2/17/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date: 2/17/2006
Re: [squid-users] Re: [Bulk] Re: [squid-users] Re: [Bulk] Re: [squid-users] Certain header not authenticating
Well, NTLM authentication is working perfectly for users accessing every site except for a claritynet training site. I am able to report via SARG using userid's, and restrict sites using squid-guard. There isn't any authentication setup on the webserver, its only use is to view SARG reports, SARG Realtime, and serve the wpad.dat file. Anyone (internally) can access these pages. The part I don't understand is why when a user uses a page with the NSPlayer header it gives me the prompt. I'm not sure if it is squid giving me the problem, or Apache. I suspect it may be Apache, so I will look into that if nobody has encountered similar issues. - Couldn't is just be that NSPlayer , does not support ntlm-auth to your local SQUID , hence the errors you are seeing ? M.
[squid-users] Certain header not authenticating
Hey, I am running squid/squidGuard with NTLM authentication. Everything works perfectly, except there is a site that some employees use for interactive training. It seems when these employees go to this site they are continually prompted for username/password with wpad.domainname.com as the realm. After investigating, the useragent log is showing this: 192.168.12.102 - - [15/Feb/2006:15:30:49 -0500] GET /wpad.dat HTTP/1.1 200 251 - NSPlayer/9.00.00.2980 It seems that the NSPlayer header is somehow not retrieving the wpad file correctly? If the users click cancel nothing happens - they can continue, but it pops up when they click to go to the next page. This is a major annoyance for some users, and has become a headache for me. I haven't explicitly set anything in squid.conf to only allow certain headers, im not even sure if you can. I have searched hell and high-water, but to no avail. Does anyone have any ideas? I really appreciate it. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date: 2/17/2006
