Here is the situation.....
I have two domains
Bank.domain.com
and
sterling.domain.com
BOTH domains share one exchange 2003 server (all malboxes reside in one exchange server) The exchange server lives in the BANK.domain.com.
Users in the STERLING.domain.com want to login to OWA.... they come to the login page.... when they login I normally tell users to login as follows:
username: STERLING\USERNAME_HERE
pw: that persona's password.....
When they hit return, it does not allow authetication to go forward..... Note: This was working for like the past 6 months and now NO AUTHENTICATION is allowed. I will say this... an ISA server was put in about 2-3 months ago.... I'm using the box as a caching server only (which filters ONLY HTTP and HTTPS traffic)
Id there something I need to modify in IIS on the exchange server? Should I try adding a permit rule to allow anyone on b0oth domains to access the OWA box?
(note: authentication will not work internally via OWN or externally)
Brett
I have two domains
Bank.domain.com
and
sterling.domain.com
BOTH domains share one exchange 2003 server (all malboxes reside in one exchange server) The exchange server lives in the BANK.domain.com.
Users in the STERLING.domain.com want to login to OWA.... they come to the login page.... when they login I normally tell users to login as follows:
username: STERLING\USERNAME_HERE
pw: that persona's password.....
When they hit return, it does not allow authetication to go forward..... Note: This was working for like the past 6 months and now NO AUTHENTICATION is allowed. I will say this... an ISA server was put in about 2-3 months ago.... I'm using the box as a caching server only (which filters ONLY HTTP and HTTPS traffic)
Id there something I need to modify in IIS on the exchange server? Should I try adding a permit rule to allow anyone on b0oth domains to access the OWA box?
(note: authentication will not work internally via OWN or externally)
Brett