Make sure the client is seutp correctly too. The CA certificate on the client is often forgotten.
HTH, Tom
Certificate on client is ok. I imported the ROOT CA. When I open OWA I don't get any warnings. From internal networks RPC/HTTPS works ok, but not from External. I use the same address to connect to RPC/HTTPS from internal and external (I use split DNS). It seems that when I pass through ISA 2004 there is a problem (https://ADDRESS/rpc/rpcproxy.dll), and I get the: Technical Information (for support personnel)
Error Code 64: Host not available Background: The connection to the Web server was lost.
Make sure the client is seutp correctly too. The CA certificate on the client is often forgotten.
HTH, Tom
Certificate on client is ok. I imported the ROOT CA. When I open OWA I don't get any warnings. From internal networks RPC/HTTPS works ok, but not from External. I use the same address to connect to RPC/HTTPS from internal and external (I use split DNS). It seems that when I pass through ISA 2004 there is a problem (https://ADDRESS/rpc/rpcproxy.dll), and I get the: Technical Information (for support personnel)
Error Code 64: Host not available Background: The connection to the Web server was lost.
Hi Marius,
What is the EXACT information contained on the Public Name and TO tabs?
What will the implications if the Exchange Server runs on the DC be?
Why are you using LDAP when you could use Windows auth?
1. None that I know of, but I'm not an Exchange Server MVP, so there may be Exchange issues, but the ISA Firewall itself doesn't care
2. LDAP authentication is a new feature in ISA 2006, so I thought I'd let people know about it. Windows integrated auth with the ISA Firewall being a domain member is always the superior security and functionality decision
What is the EXACT information contained on the Public Name and TO tabs?
Thanks! Tom
Hi,
let's say that the public name is mail.domain.com.
so, at the TO tab I have mail.domain.com (configured to point to the internal exchange server, tested from the ISA browser works ok, https://mail.domain.com/rpc/rpcproxy.dll opens a blank page, witch is ok)
traffic tab: HTTPS
listener: only HTTPS, Basic Auth, certificate name is : mail domain.com, Domain for Authentication: internaldomain.LOCAL
users tab: All, FW basic Auth
Bridging: HTTPS only
Paths; /rpc/* plus all othe exchange ones
Public Name: mail.domain.com
On the IIS server I put the certificate mail.domain.com, the same certificate as on the ISA Listener (I exported it from IIS and Imported on the ISA computer personal cerificate store)
Did you configure the permissions on the /rpc directory as outlined in the article?
Tom
I only modified at the Directory Security\ Authentication and Access control: There is only Basic Authentication and the Default domain configured to internaldomain.LOCAL
Don't mind my last question, because finally I got it working. I was looking over my settings from the beginning and found out I made a mistake in the registry setting for the RPCProxy...
In some cases I've found that the /rpc directory permissions aren't set correctly. You need to remove the anonymous permission and configure for Basic authentication.
Doc, thanks for your help above. OWA is working like a charm! Your tutorial was excellent. When I get the phones in I will try the Activesync component.
Followed the 5 part guide after upgrading to ISA 2006. Only difference with our configuaration is that we have exchange on the DC, and the ISA server is on the domain and is using windows authentication instead of LDAP. We're also using a commercial web certificate.
OWA is still working great (as it was with ISA 2004) but I've still had no sucess get RPC/HTTP to work.
When trying to connect in Outlook 2003, I get the basic authentication window but a long timeout and then an error. Looking at the ISA server monitor I see at the same time a whole load of requests on port 135 are denied.
Do I also need to add an access rule to allow inbound/outbound access on port 135 for all users?
< Message edited by dila125 -- 14.Dec.2006 5:33:52 AM >
Posts: 433
Joined: 18.Jul.2005
From: USA
Status: offline
Hi Tom,
Redirection of http to https not working and I am not able to use OWA, for some reason my access is getting denied. How should I trouble shoot? I am using LDAP for authentication. I think there is something wrong with the communication between ISA (not a domain member) and DC.
< Message edited by bhavin78 -- 12.May2008 9:49:50 PM >
Redirection of http to https not working and I am not able to use OWA, for some reason my access is getting denied. How should I trouble shoot? I am using LDAP for authentication. I think there is something wrong with the communication between ISA (not a domain member) and DC.
Check the Event Viewer for LDAP communication errors.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA 2006 Publishing] >> Exchange Publishing >> RE: Discussion about article on publishing OWA and RPC/HTTP 
RE: Discussion about article on publishing OWA and RPC/... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread