"acastleberry" <acastleberry@gmail.com> wrote in message
news:1173364253.926321.20930@q40g2000cwq.googlegroups.com...
> On Mar 7, 8:58 pm, "Ken Schaefer" <kenREM...@THISadOpenStatic.com>
> wrote: 
>
> Thanks for the response, Ken.  I am not saying that IE reporting that
> it doesn't have a connection is a IWA or IIS issue, I'm saying that
> the only way that I can get IWA to work is to place my domain in the
> intranet security zone and THAT is what creates the problem.  By
> placing https://mydomain.com in the intranet security zone, my users
> can sucessfully connect to https://mydomain.com and
> https://mydomain.com/exchange
> on our LAN.  BUT, when they go OFF LAN, they can connect to
> https://mydomain.com
> without problem, but https://mydomain.com/exchange will not connect.
> I beleive that the underlying problem is the way that IWA works and I
> am not sure if my setup is correct to make this happen like I want it
> to happen.

Hi,

Can you get a network packet capture (using Ethereal/Wireshark) to verify
that IE is indeed attempting a connection to the website?

If IE is attempting NTLM auth, and this is failing then you typically get a
401 error. If IE is attempting Kerberos Auth and failing, then I'm not sure
what error you would get, but I don't think you should get a "not connected
to the internet" type error.

That is why I'm wondering what proxy, or PAD, or other proxy auto-discovery
stuff your browser may have configured.

But again, the best way to find out exactly what is happening is to see if
IE is even attempting to go out from your client. And the best way to do
this is with Fiddler or a packet capture tool.

Cheers
Ken


--
My IIS Blog: www.adOpenStatic.com/cs/blogs/ken

[ Post a follow-up to this message ]