RE: [squid-users] FW: Squid, NT Domains and non logged in systems
On Fri, 12 Dec 2003 [EMAIL PROTECTED] wrote: > I checked the systems that were affected and they were already up to date > with the lastest, according to windows update. Any other ideas? Not really, other than if there is no traffic to the proxy then the browser is almost certainly broken.. but it is a thin line as the ntlm authentication "scheme" is digging around in Windows internal NTLMSSP authenticaiton protocols completely without any official documentation.. Regards Henrik
RE: [squid-users] FW: Squid, NT Domains and non logged in systems
I checked the systems that were affected and they were already up to date with the lastest, according to windows update. Any other ideas? Austin Wolfe -Original Message- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Friday, December 12, 2003 1:34 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [squid-users] FW: Squid, NT Domains and non logged in systems On Fri, 12 Dec 2003 [EMAIL PROTECTED] wrote: > > access the proxy. If they shut down IE and try again, it will function > > until the next deny. I have had them try to access the proxy without using > > wpad.dat and they still get the same issue. I have another proxy that does > > not require authentication and the problem does not occur. I then had them > > log their system into a domain, they get prompted for the username > > password / domain, which they enter and the problem does not occur. How do > > I resolve this? First try applying the latest security update for MSIE if you have not already. This includes several bugfixes in how MSIE maintains authentication to proxies. Regards Henrik
Re: [squid-users] FW: Squid, NT Domains and non logged in systems
On Fri, 12 Dec 2003 [EMAIL PROTECTED] wrote: > > access the proxy. If they shut down IE and try again, it will function > > until the next deny. I have had them try to access the proxy without using > > wpad.dat and they still get the same issue. I have another proxy that does > > not require authentication and the problem does not occur. I then had them > > log their system into a domain, they get prompted for the username > > password / domain, which they enter and the problem does not occur. How do > > I resolve this? First try applying the latest security update for MSIE if you have not already. This includes several bugfixes in how MSIE maintains authentication to proxies. Regards Henrik
