Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outlook 2003 cant connect using RPC over HTTP/S

Status
Not open for further replies.

reynolwi

IS-IT--Management
Sep 7, 2006
452
US
I have checked settings tried some tweaks, but for some reason outlook 2003 will not connect using rpc over http/s. I have verified the server settings and the client settings but everytime I try to connect outlook tells me the exchange server is unavailable.

Could BES be causing a problem? I have BES installed on he exchange 2003 server because there is only 8 blackberry users on the network.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
Did you install the certificate on the client machine?

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
Zelandakh said:
check to see if the certificate is valid.

Correction, should be check http[red]s[/red]://server.domain.local/remote to see if the certificate is valid.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
the certificate is good because its the same one used by OWA, but I still can not get outlook client to connect using RPC over HTTP/S

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
I didn't see a reply to my question. Did you install the cert on the client side?

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
Yes, it is a single server setup and yes I did follow those directions. RPC used to be setup on the old exchange server but when it died I had to move everything to a new box with a new servername. I set everything back up the way it used to be but nothing works still.

Mark, I tried the directions you gave me but it does not work. Our setup is servername.domain.net and i did and all it told me was the page didnt exsist. I even tried the way I have the ssl cert setup doing and still nothing.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
I think we assumed above that you have SBS. Is that the case? If not then you won't have a /remote virtual directory.

You can still grab the cert to install on the workstation though using OWA.

Go to Right click on the padlock
Click View Certificate
Then choose to install the certificate.

Make sure that your firewall is set to direct 443 to the Exchange machine too.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
443 is redirected to exchange because we use owa. no, i do not run sbs in the enterprise network.

i will try that and see what happens.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
it still does not allow it to connnect.

I have these settings on the client:

Microsoft Exchange Server: server-name.domain.net (actual exchange server name not fqdn on certificate)
Mailbox: Username

Under more settings... connections... exchange proxy settings...

URL to connect to my proxy server for exchange: (this is the fqdn i have on the ssl certificate not the server name)
Connect to proxy servers that have principal name in cert: NOT USED
Connect using SSL: YES
On Slow Networks: YES
Authentication: BASIC

Does this not look right? The only thing different from when I previously had it setup is my SSL certificate actually matched the exchange server name. This certificate I have it as owa.domain.net instead of using the true servername. I have the name owa setup in dns to forward over and for outlook web access everyone goes to and the login

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
I've been recommending the cert be installed on the client for a few posts now.

In addition I would check the box to use the proxy. You have to then fill int he box below that like this:

msstd:eek:wa.domain.com

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
Its telling me...

"The connection to Microsoft Exchange in unavailable. Outlook must be online or connected to complete this action."

Even with the msstd:eek:wa.domain.com added it tells me the same thing. What does this leave?

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
Ok... going to gives me the login popup box. I try and login and it pops up a total of 3 times. Then instead of the Error 403.2 (Forbidden: Read access is denied) I get Error 401.1 (Unauthorized: Access is denied due to invalid credentials). Looking at this I'm going to say I have a permission issue which is why its not letting it connect.


Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
Verify IIS permissions via my FAQ faq955-7121

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
I have still not been able to figure this out. I can not find the problem. Im beginning to think its an IIS problem somewhere because of the permission issue but I can't find it. RPC over HTTP/s used to work on the old exchange server so I don't know what I did differently.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions


- - - - - - - - - - - - -

Network Error:
Hit any user to continue
 
You could try rebuilding the Exchange virtual directories.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at
Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top