Topic: Authentication issue connecting to MS Outlook Web Access

[dmajwool]

Hi.
Using 6.0.1 as gateway, and attempting to connect to a Microsoft Outlook Web Access server on the internet gives an authentication error.

Using Firefox, the user's credentials are accepted during logon to the MS server and the user's mail box tree is displayed as expected, but then when the user tries to open a mail, the logon credentials dialog is displayed a second time, and the credentials are never accepted.

Using IE, the credentials are not accepted in the first place.

Using a different, unrelated DSL connection gives no problems, so I think the MS server is working OK.

Any thoughts?

Many thanks, David

[cc_skavenger]

Do a search for owa, this was covered and there is a fix.  It involves squid.

HTH

[raem]

dmajwool

Just a thought/possibility.
Are your browsers properly configured to use the sme server proxy port eg set to auto detect or specify the actual port number, rather than say, directly connect to internet ?

I have seen some authentication problems when users change this or if set wrongly.

[dmajwool]

Thanks guys.  
I tried the squid.conf fix in http://forums.contribs.org/index.php?topic=25663.msg104032#msg104032 and this hasn't yet made a difference for me.

the reason owa doesn't work is webdav by the way, but if they are using https it shouldn't matter.

but getting my customers to connect to their MS exchange server over https has avoided the issue.
Thanks again.  David.

[funkusmunkus]

The only way I got it working was port forwarding port 443 to the exchange server.
Proxy pass never worked for me.

Another way I was told would work is to create a virtual domain, and forward www.virtualdomianname in hostnames and addresses to the exchange server, and restart the server, which should forward all http and https requests that are made to that virtual domain, but that didn’t work either.

If you do get it going and have a nice and simple how to, let me know, and if your after all the info I came across in my attempts, pm me, and I’ll get back to you    

Hope that helps
Cheers

[dmajwool]

FunkusMunkus.

Thanks for the reply.  I suppose _my_ Howto is very simple,

Code: [Select]


"Tell any MS  Exchange customers to connect to their offsite OWA servers via https".

I know that merely avoids the problem and doesn't solve it, but maybe its good enough for now.

David

[funkusmunkus]

Yeah but, I wanted to know how you did it from the start, I would only allow https to OWA anyway.
I wanted to know the steps you took to get the SME server to forward web requests to your exchange server.
Was it the same as the second step option I mentioned ??

[dmajwool]

Yeah but, I wanted to know how you did it from the start

I don't think I did anything !

1. deal with irate customers who claim that "it works from company X's site, so it must be this site that's bust"
2. enquire here and read  http://forums.contribs.org/index.php?topic=25663.msg104032#msg104032
3. Do the squid.conf hack described in 2.
4. No change observed, customers still can't authenticate on http://theirdomain.com/exchange.
5. try connecting like https://theirdomain.com/exchange
6. success
HTH

David

edit.  Re-reading your post, I don't have an exchange server. I have the SME, I have customers visiting my office wanting to connect to their own server back at their base.

[funkusmunkus]

Hi David,

Yeah I think I got it around the other way, I thought you meant you had your clients-internet-SME-exchange in that order  

coz that's what I'm trying to sort out.

Oh well back to the drawring board

cheers