Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
RE: Outlook2003 via RPC over HTTP
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
 Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 5:17:00 AM
|
|
|
abraham
Posts: 72
Joined: 12.Aug.2003
From: Bogota
Status: offline
|
Look
This issue occurs if the server-based certificate is issued to a different server than the one that you are trying to connect to.
For example, if you have configured Outlook to use https://mail.secure.solutions.net as the default RPC over HTTP proxy server, but the certificate is issued to a front-end server such as frontend.example.com, the connection is not successful because the client does not recognize the front-end server as a valid server to authenticate with.
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 5:19:00 AM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
hey do you have MSN Messenger or AOL Messenger so we could chat for a few? gjackson78 is my msn messenger
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 5:24:00 AM
|
|
|
abraham
Posts: 72
Joined: 12.Aug.2003
From: Bogota
Status: offline
|
Hi. Im sorry, i can help you only in this site, if you have any question, im glad to help you.
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 5:27:00 AM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
My certificate is for "secure.gjsolutions.net" and is on my server "dcserver"...the exchange/dc is on the same box on my network so there are not a different name I use to access either. secure.gjsolutions.net is OWA as well as the certificate. Is this not done right?
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 5:36:00 AM
|
|
|
abraham
Posts: 72
Joined: 12.Aug.2003
From: Bogota
Status: offline
|
Hi. At this point i think that the issue is on the Certificate or the security configuration on the Client, but you say that the OWAs SSL is OK, wath happend if you try to Renew the Certificate (Export the existing Certificate, for Backup).
Tell about the Security configuration on the Client Profile.
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 5:46:00 AM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
ok I just went in and added "secure.gjsolutions.net" to the trust list. Now when I am outside my network and try to access my OWA the certificate Yes/No window says that I have chosen a 3rd party certificate company and have selected not to trust it...do I want to proceed yes or no? Of course I choose Yes. I haven't tried to renew yet.
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 5:56:00 AM
|
|
|
abraham
Posts: 72
Joined: 12.Aug.2003
From: Bogota
Status: offline
|
You must select YES, sorry but at this point im lost...you can connect or not. You are trying with OWA, but wath happend with your Outlook Client using RPC over HTTP. Still the error??
Ill be pending.
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 10.Oct.2003 3:03:00 PM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
Ok I'll lay it all out for you. I've followed the tutorial on this site on setting up SSL over OWA and it works without a hitch. I then followed the tutorial to set up Exchange over HTTP on this site as well. I have a certificate that I purchased from a third party and installed it on the server of course to make the SSL work. I can connect all day long via https://secure.solutions.net I also opened port 443 and port 80 on my firewall into my exchange server (which is also my domain controller). I installed Office 2003 and then had to apply the 31320 hotfix to it in order to se the Exchange over HTTP option in the client. I set up a brand new profile internal to my network by typing in the server name, username, checked the Exchange over HTTP option with the secure.solutions.net setting as well as selected basic authentication. I go back to the first tab and hit "Check Name". Immediately I get an OWA login screen in the Outlook client and type in my password. Outlook hangs for about 5 minutes and then says connection could not be established. I check the Connection status and it tries HTTP for a few minutes and then resorts to TCP/IP. I've also tried setting up a fresh profile remotely and get the same error. So yes I am able to connect via SSL OWA. I think something is happening in the client because I at least get an OWA like screen when I hit Check Name. That leads me to believe it is at least making a connection. I do not however have port 135 open on the firewall, but from what I read that should not be necessary. I receive domain name activity from Dyndns and thats where the secure.solutions.net is mapped to my public IP that is Dynamic if I might add. I'm not sure if this may be a problem. So thats basically everything I have done up to this point and I haven't been able to successfully connect to my Exchange server internally or externally via the Outlook 2003 client over HTTP. I really appreciate you taking the time to help. Thanks.
Gary
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 13.Oct.2003 4:22:00 PM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
Any ideas anyone? Thanks.
Gary
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 13.Oct.2003 4:29:00 PM
|
|
|
bist
Posts: 27
Joined: 11.Dec.2002
From: Belgium
Status: offline
|
Hi Gary,
I've been struggling with this topic too. First of all, NEVER click on check names. It simply does not work via RPC over http. There are a few things you must do before everything works. These things are not explained anywhere but on the article on win.net magazine. Follow that guide and everything will work. I believe there is a link to that guide somewhere in these forums. Try and let me know if it worked.
PS: Don't worry about ports not being open on your firewall. The only ports that need to be open are 80 and 443. So don't waste your time looking for an answers with the ports on you firewall. Did then, been there.....
Have fun
Bist
[ October 13, 2003, 04:31 PM: Message edited by: bist ]
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 14.Oct.2003 4:15:00 AM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
Hey where can i find the win.net article?
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 15.Oct.2003 1:40:00 PM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
Hey Henrik. No go. I had already read the article. My problem is I can't even create the profile internally once I enable HTTP. When I type in the name and hit finish and start outlook Connection status tries on HTTPS and then fails then resorts to TCP/IP. Something else is going on in my setup. I think its time someone just takes a look.
Gary
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 16.Oct.2003 12:57:00 PM
|
|
|
Henrik Walther
Posts: 6849
Joined: 21.Nov.2002
From: Copenhagen, Denmark
Status: offline
|
And you have applied the XP hotfix ?
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 16.Oct.2003 10:36:00 PM
|
|
|
gjackson78
Posts: 28
Joined: 21.May2003
From: Tampa, FL
Status: offline
|
Yes sure have. The hotfix just made the Exchange over HTTP option show up in Outlook 2003.
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 19.Oct.2003 5:59:00 PM
|
|
|
tshinder
Posts: 100
Joined: 9.Jul.2002
From: USA
Status: offline
|
quote:
Originally posted by Henrik Walther:
I heard MS would come up with some scripts for customizing the RPC over HTTP environment, but don't know when.
But you should be able to create the profile with profgen.exe utility from the Exchange Server Resource Kit.
Hi Henrik,
That's the nice thing about using ISA firewalls. You can create a secure RPC publishing rule and create the profile using that rule, via a remote connection. Then if you want, you can remove the rule, or leave it open, as its actually more secure than RPC over HTTPS.
Thanks!
Tom
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 19.Oct.2003 6:01:00 PM
|
|
|
tshinder
Posts: 100
Joined: 9.Jul.2002
From: USA
Status: offline
|
quote:
Originally posted by gjackson78:
Ok. I have done this. Under the Proxy settings in the client I've set up my FQDN along with Basic Auth and checked the two HTTP fast/slow network options then under the first box I've typed in my local exchange server name and typed in a username. When I hit "Check name", I get the OWA user prompt wanting username and password. I typed in the domain\user and password and hit ok. Outlook seemed to hang or freeze for about 5 minutes and then timed out saying it couldn't establish a connection to the exchange server. This is in fact remotely outside of my network. I have 443 open on the firewall as well as 135. What am I doing wrong as to why I can't get the names to resolve over the net?
Hi G,
Opening TCP 135 inbound isn't enough. You need a smart firewall like ISA 2000 that understands Exchange RPC and allows you secure inbound access to the RPC portmappering and secure dynamic port assignment. Only ISA firewalls have this layer 7 intelligence. It can't be done securely with any other type of firewall.
HTH,
Tom
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 19.Oct.2003 6:05:00 PM
|
|
|
tshinder
Posts: 100
Joined: 9.Jul.2002
From: USA
Status: offline
|
quote:
Originally posted by Abraham:
Look
This issue occurs if the server-based certificate is issued to a different server than the one that you are trying to connect to.
For example, if you have configured Outlook to use https://mail.secure.solutions.net as the default RPC over HTTP proxy server, but the certificate is issued to a front-end server such as frontend.example.com, the connection is not successful because the client does not recognize the front-end server as a valid server to authenticate with.
Hi Abraham,
Yes! Check out:
http://www.isaserver.org/tutorials/error505.html
HTH,
Tom
|
|
|
|
|
RE: Outlook2003 via RPC over HTTP - 19.Oct.2003 6:08:00 PM
|
|
|
tshinder
Posts: 100
Joined: 9.Jul.2002
From: USA
Status: offline
|
quote:
Originally posted by bist:
Hi Gary,
I've been struggling with this topic too. First of all, NEVER click on check names. It simply does not work via RPC over http. There are a few things you must do before everything works. These things are not explained anywhere but on the article on win.net magazine. Follow that guide and everything will work. I believe there is a link to that guide somewhere in these forums. Try and let me know if it worked.
PS: Don't worry about ports not being open on your firewall. The only ports that need to be open are 80 and 443. So don't waste your time looking for an answers with the ports on you firewall. Did then, been there.....
Have fun
Bist
Hi Bist,
Actually, if you check the Outlook 2003 client article, and the RPC over HTTP aritcle over at
www.tacteam.net/isaserverorg/exchangekit
All the answers are there!
HTH,
Tom
|
|
|
|
 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
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
RE: Outlook2003 via RPC over HTTP - ![[Big Grin]](/image/smiles/biggrin.gif)
