Welcome to ISAserver.org

Weird Authentication Issue

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Web Proxy] >> General >> Weird Authentication Issue

Page: [1]

Message

<< Older Topic Newer Topic >>

Weird Authentication Issue - 25.May2007 11:18:07 AM

vickmark

Posts: 1
Joined: 25.May2007
Status: offline

Hello,
We have ISA Server 2004 and recently we have been seeing some bizarre authentication issues. We have several people that are accessing our network wirelessly that can't access external webpages through our proxy server. Other people on the wireless segment can, and if those machines are connected directly to our network everything is fine. Furthermore, if we mess with the proxy settings and uncheck 'Automatically Detect Settings', and force them to use the proxy server settings entered there, then it works as well.

When monitoring the connections in the ISA console, I see the initial connection attempt come in as anonymous, but I don't see the following two connections with any kind of authentication information. We turned on some packet capturing and noticed that on connections that work, a '407 Authentication Required' packet is sent to the client. On the machines that are not working, this packet is not seen.

Any ideas on what I need to look for next? Is this an issue where wpad.dat is not being downloaded? How do I check to see if it is? If it isn't why is it not on these machines, where others in the same segment work fine? Can this be related to wireless drivers?

This is a very mysterious issue that we'd like to get resolved. I'd really appreciate any help I can get from any of you.

Thanks,
--Ryan Vickmark

Post #: 1

Featured Links*

RE: Weird Authentication Issue - 26.May2007 6:35:01 AM

mylo

Posts: 138
Joined: 26.Mar.2002
Status: offline

Ryan,

On those clients that are not working.. are they domain members?

The clients that are working are authenticated (407) and the ones that aren't are coming in as anonymous. WPAD prepends the hostname wpad to the FQDN... what happens if you do an nslookup wpad on the non-working clients? I'm guessing you're also using PAC files?

Regards,
Mylo

(in reply to vickmark)

Post #: 2