J
Jon Doe
I'm trying to set up rpc over https and I just can't seem to be able to get
it to work even after following all the technet docs for configuration and
troubleshooting. Here's what I've done so far:
I'm trying to use the same front-end server that I'm using for OWA which has
a certificate and owa is working fine. On that server, I went ahead and
checked off the rpc front-end selection in the HTTP-RPC tab. I then went to
the backend server (which is really an A/P cluster) and checked off the rpc
backend selection.
I later learned that I was supposed to do the backend first, before doing
the frontend, so I unchecked the boxes and did it in order and then rebooted
the frontend (owa) server. Then on the owa server, I went through making
sure basic authentication was selected on both my owa server and also on the
rpc subfolder... as well as making sure is requires SSL (128bit encryption).
I then went ahead and configured the client (using basic auth), and I'm
using the dns name for my owa server which is owa.domain.com as the
"exchange server". When I try to connect, I just get the prompt for login
credentials, but never connects.
To troubleshoot, I went to owa.domain.com/rpc, and it prompts me for the
login credentials, and it doesn't accept the credentials... but after the
3rd time, it would go to the "You are not authorized" page. I load up
outlook /rpc and it never gets past the login screen. On the troubleshooting
steps on technet, all software versions match/exceeds what's required.
Am I right to put in my owa server's dns name as the exchange server? Or can
someone please help me discover what I'm doing wrong? rpc doesn't work when
I'm on the network, nor does it work when I'm connection from the internet.
Thanks a lot in advance!
it to work even after following all the technet docs for configuration and
troubleshooting. Here's what I've done so far:
I'm trying to use the same front-end server that I'm using for OWA which has
a certificate and owa is working fine. On that server, I went ahead and
checked off the rpc front-end selection in the HTTP-RPC tab. I then went to
the backend server (which is really an A/P cluster) and checked off the rpc
backend selection.
I later learned that I was supposed to do the backend first, before doing
the frontend, so I unchecked the boxes and did it in order and then rebooted
the frontend (owa) server. Then on the owa server, I went through making
sure basic authentication was selected on both my owa server and also on the
rpc subfolder... as well as making sure is requires SSL (128bit encryption).
I then went ahead and configured the client (using basic auth), and I'm
using the dns name for my owa server which is owa.domain.com as the
"exchange server". When I try to connect, I just get the prompt for login
credentials, but never connects.
To troubleshoot, I went to owa.domain.com/rpc, and it prompts me for the
login credentials, and it doesn't accept the credentials... but after the
3rd time, it would go to the "You are not authorized" page. I load up
outlook /rpc and it never gets past the login screen. On the troubleshooting
steps on technet, all software versions match/exceeds what's required.
Am I right to put in my owa server's dns name as the exchange server? Or can
someone please help me discover what I'm doing wrong? rpc doesn't work when
I'm on the network, nor does it work when I'm connection from the internet.
Thanks a lot in advance!