I'm trying to find step by step documentation on setting up RPC over http from exchange all the way to setting up outlook 2003. I seem to find bits and pieces but nothing that takes you all the way through. If you know of a link I would be most appreciative. Also I'm having a problem getting my FBA to work after I upgrade the os on my exchange 2003 servers from Windows 2000 to Windows 2003 even though they were working before. Here is my setup: Internet Firewall to DMZ 1 FE server running exchange 2003 standard on windows 2003 standard (upgraded from win2k standard) Firewall to internal 1 BE server running exchange 2003 Enterprise on windows 2003 enterprise (upgraded from win2k Advanced server) both of these exchange servers were running on a version of win2k server 2 weeks ago. I have been using OWA for a few years and have not really had any problems since I originally set them up. At that time I had FBA working fine. 2 weeks ago I upgraded the FE server to windows 2003 standard so that I could setup rpc over http. At that time webmail stopped working. After a few tweeks I got it back up and running again, though without a current SSL certificate for FBA Last weekend I upgraded the BE server to finalize setting up RPC over http. Installed a current SSL certificate for FBA and now FBA doesn't work at all. At first, whenever I tried using HTTPS:// i wouldn't even get my form login. Instead I got the 440 login timeout error. Searched a bunch of forums and tried a bunch of things....the only one that worked was to rename the owalogon.asp file to an old extention and copy the logon.asp file to the auth directory and rename it to owalogon.asp. Now i get the form but it still doesn't work. Whenever I type in a username/password it just resets the form (I'm wondering if the problem is still the 440 login timeout error even though i circumvented it). I would appreciate any ideas on these matters. Thank you
On Thu, 13 Oct 2005 11:13:05 -0700, "Ian Davies" wrote: >I'm trying to find step by step documentation on setting up RPC over http >from exchange all the way to setting up outlook 2003. I seem to find bits >and pieces but nothing that takes you all the way through. If you know of a >link I would be most appreciative. > >Also I'm having a problem getting my FBA to work after I upgrade the os on >my exchange 2003 servers from Windows 2000 to Windows 2003 even though they >were working before. > >Here is my setup: > >Internet >Firewall to DMZ >1 FE server running exchange 2003 standard on windows 2003 standard >(upgraded from win2k standard) >Firewall to internal >1 BE server running exchange 2003 Enterprise on windows 2003 enterprise >(upgraded from win2k Advanced server) > >both of these exchange servers were running on a version of win2k server 2 >weeks ago. I have been using OWA for a few years and have not really had any >problems since I originally set them up. At that time I had FBA working >fine. 2 weeks ago I upgraded the FE server to windows 2003 standard so that >I could setup rpc over http. At that time webmail stopped working. After a >few tweeks I got it back up and running again, though without a current SSL >certificate for FBA > >Last weekend I upgraded the BE server to finalize setting up RPC over http. >Installed a current SSL certificate for FBA and now FBA doesn't work at all. >At first, whenever I tried using HTTPS:// i wouldn't even get my form login. >Instead I got the 440 login timeout error. Searched a bunch of forums and >tried a bunch of things....the only one that worked was to rename the >owalogon.asp file to an old extention and copy the logon.asp file to the auth >directory and rename it to owalogon.asp. Now i get the form but it still >doesn't work. Whenever I type in a username/password it just resets the form >(I'm wondering if the problem is still the 440 login timeout error even >though i circumvented it). > >I would appreciate any ideas on these matters. > >Thank you What concerns me first is the presence of the FE in a DMZ. That's not a recommended configuration and is about half an inch away from not supported. I certainly wouldn't support that configuration from nothing more fancy than a corporate security point of view. To get this working without tricky diagnostics you need to get the FE into the LAN and then start again.
