RPC over HTTP for outlook 2003
Hi.
I am a little confused and would like a little clarification.
Does RPC over HTTP for outlook 2003 mean that people who work from home or remote locations (With a broadband connection) can connect to their SBS2003 server (Exchange) and download their email to outlook 2003?
Can they also compose emails and and send them through their broadband connection to their SBS2003 server (exchange)
Thank you.
I am a little confused and would like a little clarification.
Does RPC over HTTP for outlook 2003 mean that people who work from home or remote locations (With a broadband connection) can connect to their SBS2003 server (Exchange) and download their email to outlook 2003?
Can they also compose emails and and send them through their broadband connection to their SBS2003 server (exchange)
Thank you.
ASKER
Hi Peralesa.
That is what I though and I have been trying to configure the server and client laptop for quite a while now without sucess. I have tried a number of articles with instructions on how to do this but I am a little confused.
Could I please ask a couple of questions:
Firstly.
When configuring the SBS with the CEICW and I get to the web server certificate section, I create a new web server certificate - at this point do I enter the full computer name of the server, the domain name of the computer or the www.xxx.co.uk DNS name that points to the server via the MX record?
Secondly.
When I configure the outlook client where do you specify the www address for the server - I am assuming you need to point outlook 2003 to the server which I assume is done by specifying a www address, but under exchange server settings for the account / connection / exchange proxy settings - all I can find is: use this url to connect to my proxy server... is it here i put the www address because all the abc guides seem to tell me to put something like : exchangemail.wpi.edu - but i do not recognise this as a valid www address???
I am really confused - any help would be great.
Thank you.
That is what I though and I have been trying to configure the server and client laptop for quite a while now without sucess. I have tried a number of articles with instructions on how to do this but I am a little confused.
Could I please ask a couple of questions:
Firstly.
When configuring the SBS with the CEICW and I get to the web server certificate section, I create a new web server certificate - at this point do I enter the full computer name of the server, the domain name of the computer or the www.xxx.co.uk DNS name that points to the server via the MX record?
Secondly.
When I configure the outlook client where do you specify the www address for the server - I am assuming you need to point outlook 2003 to the server which I assume is done by specifying a www address, but under exchange server settings for the account / connection / exchange proxy settings - all I can find is: use this url to connect to my proxy server... is it here i put the www address because all the abc guides seem to tell me to put something like : exchangemail.wpi.edu - but i do not recognise this as a valid www address???
I am really confused - any help would be great.
Thank you.
When you create your certificate request you will want to enter the DNS name or Fully qualified domain name, the way you want it to be addressed from the web. so www.xxx.co.uk
in your outlook under your connections setting; account / connection / exchange proxy settings / use this url/ you would enter www.xxx.co.uk the same url that is pointing to your exchange server address that you did above.
maybe this guide will help some.
http://www.msexchange.org/
in your outlook under your connections setting; account / connection / exchange proxy settings / use this url/ you would enter www.xxx.co.uk the same url that is pointing to your exchange server address that you did above.
maybe this guide will help some.
http://www.msexchange.org/
ASKER
Hi.
This is driving me nut now.
Perhaps I could please run past you the actual settings I have and would you be kind enough to advise if anything stands out as completely wrong?
Firstly - On the SBS CEICW I seleted the relevant options and created a new certificate as MERSEY.COM (without the www) and finished the wizard.
I have tested the RPC connection according to Microsofts document - http://technet.microsoft.com/en-gb/library/bb124175(EXCHG.65).aspx
On the client machine - A laptop working remotely (i.e. from a remote office with a broadband connection) I have the following:
Selecting the account in outlook - which has been configured to an exchange server and works fine withing the network conecting directly to his mailbox - the Exchange Server settings are:
Microsoft Exchange Server is: main-server.KeenProducts.l
User Name: a J Peters
Both items have an underscore which I assume means they are valid
More Settings - Security - the option for Encrypt Data has been ticked
Connections Tab - Exchange Proxy Settings -
Use this URL to connect to my proxy server is set to: MERSEY.COM (No www)
Connect using SSL is ticked - as is the Mutually Authenticate the session and in here we have:
main-server.KeenProducts.l
(I have also tried just main-server with no joy)
On fast and slow networks are both ticked (As I believe this is an acceptable setting)
and proxy authentication settings are set to:
Bacis Authentication
(I have also NTLM Authentication)
When i restart outlook and click send recieve after a short delay (Where data is being sent over the internet) i get the error -
Task - microsoft exchange server reported error (0x8004011D) the server is not available.
which seems to be quite a generic error and i cannot find any definitive resolve for.
I hope yourself or someone can help as this simple task seems to be an endless problem.
Thank you and Regards
This is driving me nut now.
Perhaps I could please run past you the actual settings I have and would you be kind enough to advise if anything stands out as completely wrong?
Firstly - On the SBS CEICW I seleted the relevant options and created a new certificate as MERSEY.COM (without the www) and finished the wizard.
I have tested the RPC connection according to Microsofts document - http://technet.microsoft.com/en-gb/library/bb124175(EXCHG.65).aspx
On the client machine - A laptop working remotely (i.e. from a remote office with a broadband connection) I have the following:
Selecting the account in outlook - which has been configured to an exchange server and works fine withing the network conecting directly to his mailbox - the Exchange Server settings are:
Microsoft Exchange Server is: main-server.KeenProducts.l
User Name: a J Peters
Both items have an underscore which I assume means they are valid
More Settings - Security - the option for Encrypt Data has been ticked
Connections Tab - Exchange Proxy Settings -
Use this URL to connect to my proxy server is set to: MERSEY.COM (No www)
Connect using SSL is ticked - as is the Mutually Authenticate the session and in here we have:
main-server.KeenProducts.l
(I have also tried just main-server with no joy)
On fast and slow networks are both ticked (As I believe this is an acceptable setting)
and proxy authentication settings are set to:
Bacis Authentication
(I have also NTLM Authentication)
When i restart outlook and click send recieve after a short delay (Where data is being sent over the internet) i get the error -
Task - microsoft exchange server reported error (0x8004011D) the server is not available.
which seems to be quite a generic error and i cannot find any definitive resolve for.
I hope yourself or someone can help as this simple task seems to be an endless problem.
Thank you and Regards
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As long as they have an internet connection and their computer set up this way they can just click on outlook and get their email, send receive pretty much everything that you can do with outlook on the lan you can do remotely.
this does require some configuration on the server side of things. And a couple of settings changed on your user clients.