At first, excuse my English, it's a Swiss interpretation of this language
I took this Tutorial to configure my installation, Exchange 2003 behind the new ISA 2006. I adapted that to my one Exchange Server Scenario without the Farm Configuration. OWA works, but I try now about 8 hours to figure out the problem with rpc over https. I can't connect with my Outlook Client. I tried everything 399 times, no chance. The resources about ISA 2006 are very sparely, about 3 articles to that.
So, when I try to test the rpc Configuration with https://localhost/rpc, the login box comes up, what is requested. But there, I can't login to receive the requested 403.2 Error, the box comes up again 3 times and then it breaks with a credential error. So, I think I have a problem there, but I compared everything with a standard rpc installation (without isa) that works, nothing. I tried also with e reinstallation of the rpc Service and the Service Pack 2 of Exchange... no chance.
So, now I'm searching for an answer and I don't know who can help me....
If you have an Idea... I'm very receptive to any tip!!!
Thanks for your reply. Yes, the Certificates are ok. I have an official certificate (trustcenter, like Verisign). OWA works without any error. Also the rpc tests are now successful, I made a mistake, I tested it with the guidelines of windows 2003 without SP1... so internal everything seems ok. Only when I try to connect from outside, trough the ISA Server nothing happens. When I try to test from outside with a connection to https://host.ch/rpc, the ISA Login Screen comes up (like OWA). But after sign in, nothing happens, ISA displays the login screen again!
I invested many hours now in this configuration and I can't find the failure!
Yes, everything set to Basic authentication. When I run /rpcdiag Switch, I can see, that nothing happens over HTTP. Outlook tries to connect and after a timeout of 20-30 seconds, the request fails with the standard answer that Exchange must be online! Internal everything works fine!
What is the common name on the Web site certificate bound to the Web listener? webmail.insidehost.ch
What is the common name on the Web site certificate bound to the RPC/HTTP proxy machine? webmail.insidehost.ch (exchange server/ i've exported the certificate to a file from this machine and imported it to the isa, which says me that the cert. is correctly installed)
What is the name on the TO tab? webmail.insidehost.ch and the internal name, if the external can't resolved
What is the name on the public name tab? webmail.insidehost.ch
I've read the article through and trough but I'm still confused on one point. ISA 2006 Web Farms are exactly what my client wants. He refuses to buy an hardware load-balancer and Windows integrated NLB doesn't work since ISA 2004 is unable to pool the destination IP's/Ports to see if they're alive. Now, reading the article (as I've understood it) we now can have different certificates on the listener and on the target web servers?... This is confusing, in ISA 2004 with SSL bridging I had to have the same certificate on the listener and on the target web server(s). Is this not the case in ISA 2006 with Web Farms?
What is the common name on the Web site certificate bound to the Web listener? webmail.insidehost.ch
What is the common name on the Web site certificate bound to the RPC/HTTP proxy machine? webmail.insidehost.ch (exchange server/ i've exported the certificate to a file from this machine and imported it to the isa, which says me that the cert. is correctly installed)
What is the name on the TO tab? webmail.insidehost.ch and the internal name, if the external can't resolved
What is the name on the public name tab? webmail.insidehost.ch
I have the same problem so far as Marco, and my Exchange Server is unfortunately also the DC. What were you going to suggest to Marco if that was his case please? My certificates and client are configured fine, and I thought I had done what was needed in the registry with Exchange SP2.
Marco, let us know if you fixed it also please - that would be great.
Its more simple when its on the DC. All you need to do is install the RPC/HTTP proxy service on the machine. You don't need to fiddle with the ports in the Registry.
Keep in mind that you can't use an FBA enabled listener for RPC/HTTP with the 2004 ISA Firewall.
hi guys, i dunno if this has been asked somewhere but do i really need to create a split DNS for me to access my OWA from external clients? are there any other alternatives?
"Hi Dan, Its more simple when its on the DC. All you need to do is install the RPC/HTTP proxy service on the machine. You don't need to fiddle with the ports in the Registry. Keep in mind that you can't use an FBA enabled listener for RPC/HTTP with the 2004 ISA Firewall. HTH, Tom
How is this supposed to help? It doesn't even make sense or pertain to the proceeding problem. Nobody suggested fiddling with registry ports. Everyone already knows you simply apply ServicePack 2 to each Exchange server before configuring them as front end and back end in your rpc/http topology. Nobody suggested using an FBA enabled listener or ISA 2004 for that matter. You are talking about installing the RPC/HTTP proxy service which he obviously already did and does not need help with. We need to know why the ISA FBA page appears but just reappers after we enter valid credentials instead of showing the OWA mailbox.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA Server 2004 General ] >> Exchange Publishing >> Discussion about Publishing Outlook Web Access and Outlook RPC/HTTP with ISA Server 2006 part 4 
Discussion about Publishing Outlook Web Access and Outl... - 
... help please...
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