Outlook RPC over HTTp deosn't work

Not sure about 64bit versus 32bit. Sounds kinda like you might be missing
your client certificate.

Access your Exchange server via Outlook Web Access while using Internet
Explorer. Typically it's https://servername/exchange.

See if you receive a prompt with a certificate warning. You should have
three options: Yes, No, View Certificate. If you receive this, select View
Certificate. Then, select Install Certificate. Take the default options
all the way through saying YES at the last box.

Retry connecting to your server via RPC over HTTP using Outlook and see what
happens.

One other thing to try is when you launch Outlook and receive the username
and password box, enter your username as domain\username and then your
network password. Shouldn't make much difference...but doesn't hurt to try.

Stephen

"sdgirl143" <sdgirl.RemoveThis@discussions.microsoft.com> wrote in message
news:1E819216-9BFC-4BFE-ACC8-0CC005479676@microsoft.com...
>I am still having problems connecting to the Exchange server. I get as far
> as if I go to start/run and type in outlook /rpcdiag I get a box that
> shows
> connecting for the exchange server status. my connect to mail box comes
> up
> and I type in my entire email address and password. As soon as I do that
> my
> status disconnects and I get a box that says Your microsoft Exchange
> server
> is unavailable. Retry/work offline...
> My coworker is able to connect to the same exchange box from his computer
> and the only difference in our machines is that his is XP Pro and Mine is
> XP
> Media with a 64 bit. Please can you help???
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

Ok.. I installed the certificate but now when I try to log in Outlook acts
like I have the wrong password...
It shows connecting but then the password box comes up like it is the wrong
password.
--
Tracey Steinbach


"Stephen Harrington" wrote:

> Not sure about 64bit versus 32bit. Sounds kinda like you might be missing
> your client certificate.
>
> Access your Exchange server via Outlook Web Access while using Internet
> Explorer. Typically it's https://servername/exchange.
>
> See if you receive a prompt with a certificate warning. You should have
> three options: Yes, No, View Certificate. If you receive this, select View
> Certificate. Then, select Install Certificate. Take the default options
> all the way through saying YES at the last box.
>
> Retry connecting to your server via RPC over HTTP using Outlook and see what
> happens.
>
> One other thing to try is when you launch Outlook and receive the username
> and password box, enter your username as domain\username and then your
> network password. Shouldn't make much difference...but doesn't hurt to try.
>
> Stephen
>
> "sdgirl143" <sdgirl.DeleteThis@discussions.microsoft.com> wrote in message
> news:1E819216-9BFC-4BFE-ACC8-0CC005479676@microsoft.com...
> >I am still having problems connecting to the Exchange server. I get as far
> > as if I go to start/run and type in outlook /rpcdiag I get a box that
> > shows
> > connecting for the exchange server status. my connect to mail box comes
> > up
> > and I type in my entire email address and password. As soon as I do that
> > my
> > status disconnects and I get a box that says Your microsoft Exchange
> > server
> > is unavailable. Retry/work offline...
> > My coworker is able to connect to the same exchange box from his computer
> > and the only difference in our machines is that his is XP Pro and Mine is
> > XP
> > Media with a 64 bit. Please can you help???
>
>
>
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

I just restarted my computer and it still comes up retry/offline.....
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

"Nathan Liu [MSFT]" wrote:
> 2. To troubleshooting RPC over HTTP related issue:
>
> A. From the Internet client, browse to https://FQDN/rpc. In order for RPC
> over HTTP to work, you must be able to browse to this URL without getting a
> popup warning about the certificate. You will receive the following error
> on the page:
>
> The page cannot be displayed
> HTTP Error 403.2 - Forbidden: Read access is denied.
> Internet Information Services (IIS)
>
> This is normal. The idea is to be able to get to that page without getting
> the popup warning about the certificate.

And what if i have a different error ?
I have a polish SBS so i will try to translate this error to english:

Error HTTP 401.3 — No authorization: Access is denied. For the reqeusted
resource an access control list was configured.
Internet Information Services (IIS)

I have a seroius problem... I'm trying to configure Outlook and Exchange for
2 weeks now and i can't make it.
I have an SBS 2003 Standard with no ISA firewall, no firewall at all.

And Outlook 2003 with SP1.
It works fine thru LAN but i can't get it work thru the Internet or VPN...

I have my own SBS certificate and it seems to work cuz OWA works thru
Internet.
I've red many tutorials how the Exchange and Outlook should be configured to
work with RPC over HTTP and i think it's configured properly cuz it works on
LAN.

But i'm missing something and i don't know what it is;/

Thnx for any help.
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

Nathan:

I'm having the same initial problem, but I think with a twist. When I put
https://publishing.mydomain.local/remote - I don't get anything about the
certificate, it just says that internet explorer can't display the website.
My connection is fine, so I'm stuck! I use IE7.0 beta, might that impact it?

Thanks,

Cheryl
"Nathan Liu [MSFT]" wrote:

> Hello Lily,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that you received the error
> message "'The connection to the Microsoft Exchange Erver is unavailable¡­"
> when you try to use RPC over HTTP to connect the Exchange Server. If I have
> misunderstood your concern, please don't hesitate to let me know.
>
> 1. In SBS 2003, we don't have to manually configure RPC over HTTP. We can
> follow the steps below to enable RPC over HTTP:
>
> A. Make sure you have enabled "Outlook over the Internet" and "Remote Web
> Workplace" in the CEICW (Configure E-mail and Internet Connection wizard),
> then you will logon to the Remote Web Workplace (https://serverfqdn/remote)
> as a user from the remote client and look at the link for "Configure
> Outlook via the Internet". You can see it from the server by going into
> https://localhost/remote. If the option is not displayed, then the feature
> is not configured on the server.
>
> B. Click "Configure Outlook via the Internet" and then the Web page "Using
> Outlook via the Internet" will appear which has pretty much a step by step
> list of instructions. If it tells you to use "server.domain.local", use
> that. If it tells you to use "server.domain.com", use that. Follow the
> steps exactly.
>
> References:
>
> 825763 How to configure Internet access in Windows Small Business Server
> 2003
> http://support.microsoft.com/?id=825763
>
> Windows Small Business Server 2003 Getting Started Guide
> Appendix C - Network Configuration Settings
> http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx
>
> 2. To troubleshooting RPC over HTTP related issue:
>
> A. From the Internet client, browse to https://FQDN/rpc. In order for RPC
> over HTTP to work, you must be able to browse to this URL without getting a
> popup warning about the certificate. You will receive the following error
> on the page:
>
> The page cannot be displayed
> HTTP Error 403.2 - Forbidden: Read access is denied.
> Internet Information Services (IIS)
>
> This is normal. The idea is to be able to get to that page without getting
> the popup warning about the certificate.
>
> B. If URLScan is installed on the SBS server, in some configurations, it is
> necessary to make the following changes in urlscan.ini in order for RPC
> over HTTP to work:
>
> [RequestLimits]
> ; The entries in this section impose limits on the length
> ; of allowed parts of requests reaching the server.
> MaxAllowedContentLength=2000000000
> MaxUrl=16384
> MaxQueryString=4096
>
> In addition, you need to add the following verbs to the Allow Verbs:
>
> RPC_IN_DATA
> RPC_OUT_DATA
>
> After editing the ini file, restart IIS Admin Service and Microsoft ISA
> Server Control services.
>
> Reference:
>
> 823175 Fine-tuning and known issues when you use the Urlscan utility in an
> Exchange 2003 environment
> http://support.microsoft.com/?id=823175
>
> 3. Start outlook with the /rpcdiag switch, does that provide any direction?
>
> 4. On the SBS server, verify if it trusts the certificate:
>
> A. Open Internet Explorer, and then in the address bar type:
> https://publishing.yourdomain.local/remote
>
> B. If the certificate is not trusted, a warning popup appears. Click View
> Certificate, click Install Certificate, and then follow the instructions.
>
> 5. On the SBS server, open IIS Manager, expand your server\Web Service
> Extensions, is RPC Proxy Server Extension allowed? If so, double-click it,
> check if it is using "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll". If it is
> using "C:\WINDOWS\system32\rpcproxy.dll", remove it and add
> "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll" on the Required Files tab. Run
> "iisreset" and see how it goes.
>
> 6. How many NIC installed on your SBS server. Is ISA also installed? Is
> there any software firewall enabled on the SBS server? Generally, for RPC
> over HTTP, we just need to open the incoming TCP port 80 and 443 on the
> hardware firewall.
>
> 7. Please do a screen capture of this issue on the Outlook client, and then
> attach it in your reply.
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Outlook RPC over HTTp deosn't work
> >thread-index: AcWFxQ2Hc31WhoftSi61Vr9ffXKqNQ==
> >X-WBNR-Posting-Host: 203.25.66.146
> >From: "=?Utf-8?B?TGlseQ==?=" <Lily.RemoveThis@discussions.microsoft.com>
> >Subject: Outlook RPC over HTTp deosn't work
> >Date: Sun, 10 Jul 2005 20:03:03 -0700
> >Lines: 13
> >Message-ID: <2FD717CC-D301-49FD-90A2-79440BF9D862.RemoveThis@microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:134554
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi!
> >I enabled Outlook RPC over HTTP on SBS 03 server, and followed the
> >instructions to configure Outlook 03.
> >But now Outllok can't connect anymore, at all. When it starts - comes up
> >with a message:
> >'The connection to the Microsoft Exchange Erver is unavailable.Outlook
> must
> >be online or connected to complete this action.' and then:
> >'Unable to open your default email folders. The information store could be
> >opened.'
> >
> >Please help!
> >--
> >Thanks, Lily!
> >
>
>
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

"Nathan Liu [MSFT]" wrote:

> Hello Lily,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that you received the error
> message "'The connection to the Microsoft Exchange Erver is unavailable¡­"
> when you try to use RPC over HTTP to connect the Exchange Server. If I have
> misunderstood your concern, please don't hesitate to let me know.
>
> 1. In SBS 2003, we don't have to manually configure RPC over HTTP. We can
> follow the steps below to enable RPC over HTTP:
>
> A. Make sure you have enabled "Outlook over the Internet" and "Remote Web
> Workplace" in the CEICW (Configure E-mail and Internet Connection wizard),
> then you will logon to the Remote Web Workplace (https://serverfqdn/remote)
> as a user from the remote client and look at the link for "Configure
> Outlook via the Internet". You can see it from the server by going into
> https://localhost/remote. If the option is not displayed, then the feature
> is not configured on the server.
>
> B. Click "Configure Outlook via the Internet" and then the Web page "Using
> Outlook via the Internet" will appear which has pretty much a step by step
> list of instructions. If it tells you to use "server.domain.local", use
> that. If it tells you to use "server.domain.com", use that. Follow the
> steps exactly.
>
> References:
>
> 825763 How to configure Internet access in Windows Small Business Server
> 2003
> http://support.microsoft.com/?id=825763
>
> Windows Small Business Server 2003 Getting Started Guide
> Appendix C - Network Configuration Settings
> http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx
>
> 2. To troubleshooting RPC over HTTP related issue:
>
> A. From the Internet client, browse to https://FQDN/rpc. In order for RPC
> over HTTP to work, you must be able to browse to this URL without getting a
> popup warning about the certificate. You will receive the following error
> on the page:
>
> The page cannot be displayed
> HTTP Error 403.2 - Forbidden: Read access is denied.
> Internet Information Services (IIS)
>
> This is normal. The idea is to be able to get to that page without getting
> the popup warning about the certificate.
>
> B. If URLScan is installed on the SBS server, in some configurations, it is
> necessary to make the following changes in urlscan.ini in order for RPC
> over HTTP to work:
>
> [RequestLimits]
> ; The entries in this section impose limits on the length
> ; of allowed parts of requests reaching the server.
> MaxAllowedContentLength=2000000000
> MaxUrl=16384
> MaxQueryString=4096
>
> In addition, you need to add the following verbs to the Allow Verbs:
>
> RPC_IN_DATA
> RPC_OUT_DATA
>
> After editing the ini file, restart IIS Admin Service and Microsoft ISA
> Server Control services.
>
> Reference:
>
> 823175 Fine-tuning and known issues when you use the Urlscan utility in an
> Exchange 2003 environment
> http://support.microsoft.com/?id=823175
>
> 3. Start outlook with the /rpcdiag switch, does that provide any direction?
>
> 4. On the SBS server, verify if it trusts the certificate:
>
> A. Open Internet Explorer, and then in the address bar type:
> https://publishing.yourdomain.local/remote
>
> B. If the certificate is not trusted, a warning popup appears. Click View
> Certificate, click Install Certificate, and then follow the instructions.
>
> 5. On the SBS server, open IIS Manager, expand your server\Web Service
> Extensions, is RPC Proxy Server Extension allowed? If so, double-click it,
> check if it is using "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll". If it is
> using "C:\WINDOWS\system32\rpcproxy.dll", remove it and add
> "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll" on the Required Files tab. Run
> "iisreset" and see how it goes.
>
> 6. How many NIC installed on your SBS server. Is ISA also installed? Is
> there any software firewall enabled on the SBS server? Generally, for RPC
> over HTTP, we just need to open the incoming TCP port 80 and 443 on the
> hardware firewall.
>
> 7. Please do a screen capture of this issue on the Outlook client, and then
> attach it in your reply.
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Outlook RPC over HTTp deosn't work
> >thread-index: AcWFxQ2Hc31WhoftSi61Vr9ffXKqNQ==
> >X-WBNR-Posting-Host: 203.25.66.146
> >From: "=?Utf-8?B?TGlseQ==?=" <Lily RemoveThis @discussions.microsoft.com>
> >Subject: Outlook RPC over HTTp deosn't work
> >Date: Sun, 10 Jul 2005 20:03:03 -0700
> >Lines: 13
> >Message-ID: <2FD717CC-D301-49FD-90A2-79440BF9D862 RemoveThis @microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:134554
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi!
> >I enabled Outlook RPC over HTTP on SBS 03 server, and followed the
> >instructions to configure Outlook 03.
> >But now Outllok can't connect anymore, at all. When it starts - comes up
> >with a message:
> >'The connection to the Microsoft Exchange Erver is unavailable.Outlook
> must
> >be online or connected to complete this action.' and then:
> >'Unable to open your default email folders. The information store could be
> >opened.'
> >
> >Please help!
> >--
> >Thanks, Lily!
> >
>
>
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

HI Nathan
i have same problem .and try to export certificate to a pfx file .and
install it to my local computer but still can't check name
can you help

barry

"Nathan Liu [MSFT]" wrote:

> Hello Lily,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that you received the error
> message "'The connection to the Microsoft Exchange Erver is unavailable¡­"
> when you try to use RPC over HTTP to connect the Exchange Server. If I have
> misunderstood your concern, please don't hesitate to let me know.
>
> 1. In SBS 2003, we don't have to manually configure RPC over HTTP. We can
> follow the steps below to enable RPC over HTTP:
>
> A. Make sure you have enabled "Outlook over the Internet" and "Remote Web
> Workplace" in the CEICW (Configure E-mail and Internet Connection wizard),
> then you will logon to the Remote Web Workplace (https://serverfqdn/remote)
> as a user from the remote client and look at the link for "Configure
> Outlook via the Internet". You can see it from the server by going into
> https://localhost/remote. If the option is not displayed, then the feature
> is not configured on the server.
>
> B. Click "Configure Outlook via the Internet" and then the Web page "Using
> Outlook via the Internet" will appear which has pretty much a step by step
> list of instructions. If it tells you to use "server.domain.local", use
> that. If it tells you to use "server.domain.com", use that. Follow the
> steps exactly.
>
> References:
>
> 825763 How to configure Internet access in Windows Small Business Server
> 2003
> http://support.microsoft.com/?id=825763
>
> Windows Small Business Server 2003 Getting Started Guide
> Appendix C - Network Configuration Settings
> http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx
>
> 2. To troubleshooting RPC over HTTP related issue:
>
> A. From the Internet client, browse to https://FQDN/rpc. In order for RPC
> over HTTP to work, you must be able to browse to this URL without getting a
> popup warning about the certificate. You will receive the following error
> on the page:
>
> The page cannot be displayed
> HTTP Error 403.2 - Forbidden: Read access is denied.
> Internet Information Services (IIS)
>
> This is normal. The idea is to be able to get to that page without getting
> the popup warning about the certificate.
>
> B. If URLScan is installed on the SBS server, in some configurations, it is
> necessary to make the following changes in urlscan.ini in order for RPC
> over HTTP to work:
>
> [RequestLimits]
> ; The entries in this section impose limits on the length
> ; of allowed parts of requests reaching the server.
> MaxAllowedContentLength=2000000000
> MaxUrl=16384
> MaxQueryString=4096
>
> In addition, you need to add the following verbs to the Allow Verbs:
>
> RPC_IN_DATA
> RPC_OUT_DATA
>
> After editing the ini file, restart IIS Admin Service and Microsoft ISA
> Server Control services.
>
> Reference:
>
> 823175 Fine-tuning and known issues when you use the Urlscan utility in an
> Exchange 2003 environment
> http://support.microsoft.com/?id=823175
>
> 3. Start outlook with the /rpcdiag switch, does that provide any direction?
>
> 4. On the SBS server, verify if it trusts the certificate:
>
> A. Open Internet Explorer, and then in the address bar type:
> https://publishing.yourdomain.local/remote
>
> B. If the certificate is not trusted, a warning popup appears. Click View
> Certificate, click Install Certificate, and then follow the instructions.
>
> 5. On the SBS server, open IIS Manager, expand your server\Web Service
> Extensions, is RPC Proxy Server Extension allowed? If so, double-click it,
> check if it is using "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll". If it is
> using "C:\WINDOWS\system32\rpcproxy.dll", remove it and add
> "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll" on the Required Files tab. Run
> "iisreset" and see how it goes.
>
> 6. How many NIC installed on your SBS server. Is ISA also installed? Is
> there any software firewall enabled on the SBS server? Generally, for RPC
> over HTTP, we just need to open the incoming TCP port 80 and 443 on the
> hardware firewall.
>
> 7. Please do a screen capture of this issue on the Outlook client, and then
> attach it in your reply.
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Outlook RPC over HTTp deosn't work
> >thread-index: AcWFxQ2Hc31WhoftSi61Vr9ffXKqNQ==
> >X-WBNR-Posting-Host: 203.25.66.146
> >From: "=?Utf-8?B?TGlseQ==?=" <Lily.DeleteThis@discussions.microsoft.com>
> >Subject: Outlook RPC over HTTp deosn't work
> >Date: Sun, 10 Jul 2005 20:03:03 -0700
> >Lines: 13
> >Message-ID: <2FD717CC-D301-49FD-90A2-79440BF9D862.DeleteThis@microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:134554
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi!
> >I enabled Outlook RPC over HTTP on SBS 03 server, and followed the
> >instructions to configure Outlook 03.
> >But now Outllok can't connect anymore, at all. When it starts - comes up
> >with a message:
> >'The connection to the Microsoft Exchange Erver is unavailable.Outlook
> must
> >be online or connected to complete this action.' and then:
> >'Unable to open your default email folders. The information store could be
> >opened.'
> >
> >Please help!
> >--
> >Thanks, Lily!
> >
>
>
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

Hi Nathan
how to fix this step ??
B. If the certificate is not trusted, a warning popup appears. Click View
Certificate, click Install Certificate, and then follow the instructions.
when i open
http://mail.mydomain.com/exchange
there is a problem with this websites's security certificate.
the xecurity cerficate by this website was not issued by trusted certificate
authonity.
the xecurity cerficate by this website was not issued for a different
website's address.
we recommend that you cloas this webpage ans do not continue to this website .
1. click here to close this website .
2.continue to this website (not recommended).
more information
Thx
Barry





"Nathan Liu [MSFT]" wrote:

> Hello Lily,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that you received the error
> message "'The connection to the Microsoft Exchange Erver is unavailable¡­"
> when you try to use RPC over HTTP to connect the Exchange Server. If I have
> misunderstood your concern, please don't hesitate to let me know.
>
> 1. In SBS 2003, we don't have to manually configure RPC over HTTP. We can
> follow the steps below to enable RPC over HTTP:
>
> A. Make sure you have enabled "Outlook over the Internet" and "Remote Web
> Workplace" in the CEICW (Configure E-mail and Internet Connection wizard),
> then you will logon to the Remote Web Workplace (https://serverfqdn/remote)
> as a user from the remote client and look at the link for "Configure
> Outlook via the Internet". You can see it from the server by going into
> https://localhost/remote. If the option is not displayed, then the feature
> is not configured on the server.
>
> B. Click "Configure Outlook via the Internet" and then the Web page "Using
> Outlook via the Internet" will appear which has pretty much a step by step
> list of instructions. If it tells you to use "server.domain.local", use
> that. If it tells you to use "server.domain.com", use that. Follow the
> steps exactly.
>
> References:
>
> 825763 How to configure Internet access in Windows Small Business Server
> 2003
> http://support.microsoft.com/?id=825763
>
> Windows Small Business Server 2003 Getting Started Guide
> Appendix C - Network Configuration Settings
> http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx
>
> 2. To troubleshooting RPC over HTTP related issue:
>
> A. From the Internet client, browse to https://FQDN/rpc. In order for RPC
> over HTTP to work, you must be able to browse to this URL without getting a
> popup warning about the certificate. You will receive the following error
> on the page:
>
> The page cannot be displayed
> HTTP Error 403.2 - Forbidden: Read access is denied.
> Internet Information Services (IIS)
>
> This is normal. The idea is to be able to get to that page without getting
> the popup warning about the certificate.
>
> B. If URLScan is installed on the SBS server, in some configurations, it is
> necessary to make the following changes in urlscan.ini in order for RPC
> over HTTP to work:
>
> [RequestLimits]
> ; The entries in this section impose limits on the length
> ; of allowed parts of requests reaching the server.
> MaxAllowedContentLength=2000000000
> MaxUrl=16384
> MaxQueryString=4096
>
> In addition, you need to add the following verbs to the Allow Verbs:
>
> RPC_IN_DATA
> RPC_OUT_DATA
>
> After editing the ini file, restart IIS Admin Service and Microsoft ISA
> Server Control services.
>
> Reference:
>
> 823175 Fine-tuning and known issues when you use the Urlscan utility in an
> Exchange 2003 environment
> http://support.microsoft.com/?id=823175
>
> 3. Start outlook with the /rpcdiag switch, does that provide any direction?
>
> 4. On the SBS server, verify if it trusts the certificate:
>
> A. Open Internet Explorer, and then in the address bar type:
> https://publishing.yourdomain.local/remote
>
> B. If the certificate is not trusted, a warning popup appears. Click View
> Certificate, click Install Certificate, and then follow the instructions.
>
> 5. On the SBS server, open IIS Manager, expand your server\Web Service
> Extensions, is RPC Proxy Server Extension allowed? If so, double-click it,
> check if it is using "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll". If it is
> using "C:\WINDOWS\system32\rpcproxy.dll", remove it and add
> "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll" on the Required Files tab. Run
> "iisreset" and see how it goes.
>
> 6. How many NIC installed on your SBS server. Is ISA also installed? Is
> there any software firewall enabled on the SBS server? Generally, for RPC
> over HTTP, we just need to open the incoming TCP port 80 and 443 on the
> hardware firewall.
>
> 7. Please do a screen capture of this issue on the Outlook client, and then
> attach it in your reply.
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Outlook RPC over HTTp deosn't work
> >thread-index: AcWFxQ2Hc31WhoftSi61Vr9ffXKqNQ==
> >X-WBNR-Posting-Host: 203.25.66.146
> >From: "=?Utf-8?B?TGlseQ==?=" <Lily.TakeThisOut@discussions.microsoft.com>
> >Subject: Outlook RPC over HTTp deosn't work
> >Date: Sun, 10 Jul 2005 20:03:03 -0700
> >Lines: 13
> >Message-ID: <2FD717CC-D301-49FD-90A2-79440BF9D862.TakeThisOut@microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:134554
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hi!
> >I enabled Outlook RPC over HTTP on SBS 03 server, and followed the
> >instructions to configure Outlook 03.
> >But now Outllok can't connect anymore, at all. When it starts - comes up
> >with a message:
> >'The connection to the Microsoft Exchange Erver is unavailable.Outlook
> must
> >be online or connected to complete this action.' and then:
> >'Unable to open your default email folders. The information store could be
> >opened.'
> >
> >Please help!
> >--
> >Thanks, Lily!
> >
>
>
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

i have same problem .and try to export certificate to a pfx file .and
> install it to my local computer but still can't check name
> can you help
>

"Barry Lee" wrote:

> HI Nathan
> i have same problem .and try to export certificate to a pfx file .and
> install it to my local computer but still can't check name
> can you help
>
> barry
>
> "Nathan Liu [MSFT]" wrote:
>
> > Hello Lily,
> >
> > Thank you for posting in the SBS newsgroup.
> >
> > According to your description, I understand that you received the error
> > message "'The connection to the Microsoft Exchange Erver is unavailable¡­"
> > when you try to use RPC over HTTP to connect the Exchange Server. If I have
> > misunderstood your concern, please don't hesitate to let me know.
> >
> > 1. In SBS 2003, we don't have to manually configure RPC over HTTP. We can
> > follow the steps below to enable RPC over HTTP:
> >
> > A. Make sure you have enabled "Outlook over the Internet" and "Remote Web
> > Workplace" in the CEICW (Configure E-mail and Internet Connection wizard),
> > then you will logon to the Remote Web Workplace (https://serverfqdn/remote)
> > as a user from the remote client and look at the link for "Configure
> > Outlook via the Internet". You can see it from the server by going into
> > https://localhost/remote. If the option is not displayed, then the feature
> > is not configured on the server.
> >
> > B. Click "Configure Outlook via the Internet" and then the Web page "Using
> > Outlook via the Internet" will appear which has pretty much a step by step
> > list of instructions. If it tells you to use "server.domain.local", use
> > that. If it tells you to use "server.domain.com", use that. Follow the
> > steps exactly.
> >
> > References:
> >
> > 825763 How to configure Internet access in Windows Small Business Server
> > 2003
> > http://support.microsoft.com/?id=825763
> >
> > Windows Small Business Server 2003 Getting Started Guide
> > Appendix C - Network Configuration Settings
> > http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx
> >
> > 2. To troubleshooting RPC over HTTP related issue:
> >
> > A. From the Internet client, browse to https://FQDN/rpc. In order for RPC
> > over HTTP to work, you must be able to browse to this URL without getting a
> > popup warning about the certificate. You will receive the following error
> > on the page:
> >
> > The page cannot be displayed
> > HTTP Error 403.2 - Forbidden: Read access is denied.
> > Internet Information Services (IIS)
> >
> > This is normal. The idea is to be able to get to that page without getting
> > the popup warning about the certificate.
> >
> > B. If URLScan is installed on the SBS server, in some configurations, it is
> > necessary to make the following changes in urlscan.ini in order for RPC
> > over HTTP to work:
> >
> > [RequestLimits]
> > ; The entries in this section impose limits on the length
> > ; of allowed parts of requests reaching the server.
> > MaxAllowedContentLength=2000000000
> > MaxUrl=16384
> > MaxQueryString=4096
> >
> > In addition, you need to add the following verbs to the Allow Verbs:
> >
> > RPC_IN_DATA
> > RPC_OUT_DATA
> >
> > After editing the ini file, restart IIS Admin Service and Microsoft ISA
> > Server Control services.
> >
> > Reference:
> >
> > 823175 Fine-tuning and known issues when you use the Urlscan utility in an
> > Exchange 2003 environment
> > http://support.microsoft.com/?id=823175
> >
> > 3. Start outlook with the /rpcdiag switch, does that provide any direction?
> >
> > 4. On the SBS server, verify if it trusts the certificate:
> >
> > A. Open Internet Explorer, and then in the address bar type:
> > https://publishing.yourdomain.local/remote
> >
> > B. If the certificate is not trusted, a warning popup appears. Click View
> > Certificate, click Install Certificate, and then follow the instructions.
> >
> > 5. On the SBS server, open IIS Manager, expand your server\Web Service
> > Extensions, is RPC Proxy Server Extension allowed? If so, double-click it,
> > check if it is using "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll". If it is
> > using "C:\WINDOWS\system32\rpcproxy.dll", remove it and add
> > "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll" on the Required Files tab. Run
> > "iisreset" and see how it goes.
> >
> > 6. How many NIC installed on your SBS server. Is ISA also installed? Is
> > there any software firewall enabled on the SBS server? Generally, for RPC
> > over HTTP, we just need to open the incoming TCP port 80 and 443 on the
> > hardware firewall.
> >
> > 7. Please do a screen capture of this issue on the Outlook client, and then
> > attach it in your reply.
> >
> > I am appreciated your time and cooperation. If anything is unclear, please
> > feel free to let me know. I am looking forward to hearing from you.
> >
> > Best regards,
> >
> > Nathan Liu (MSFT)
> > Microsoft CSS Online Newsgroup Support
> > Get Secure! - www.microsoft.com/security
> > =====================================================
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > =====================================================
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> > --------------------
> > >Thread-Topic: Outlook RPC over HTTp deosn't work
> > >thread-index: AcWFxQ2Hc31WhoftSi61Vr9ffXKqNQ==
> > >X-WBNR-Posting-Host: 203.25.66.146
> > >From: "=?Utf-8?B?TGlseQ==?=" <Lily DeleteThis @discussions.microsoft.com>
> > >Subject: Outlook RPC over HTTp deosn't work
> > >Date: Sun, 10 Jul 2005 20:03:03 -0700
> > >Lines: 13
> > >Message-ID: <2FD717CC-D301-49FD-90A2-79440BF9D862 DeleteThis @microsoft.com>
> > >MIME-Version: 1.0
> > >Content-Type: text/plain;
> > > charset="Utf-8"
> > >Content-Transfer-Encoding: 7bit
> > >X-Newsreader: Microsoft CDO for Windows 2000
> > >Content-Class: urn:content-classes:message
> > >Importance: normal
> > >Priority: normal
> > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> > >Newsgroups: microsoft.public.windows.server.sbs
> > >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> > >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> > >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:134554
> > >X-Tomcat-NG: microsoft.public.windows.server.sbs
> > >
> > >Hi!
> > >I enabled Outlook RPC over HTTP on SBS 03 server, and followed the
> > >instructions to configure Outlook 03.
> > >But now Outllok can't connect anymore, at all. When it starts - comes up
> > >with a message:
> > >'The connection to the Microsoft Exchange Erver is unavailable.Outlook
> > must
> > >be online or connected to complete this action.' and then:
> > >'Unable to open your default email folders. The information store could be
> > >opened.'
> > >
> > >Please help!
> > >--
> > >Thanks, Lily!
> > >
> >
> >
 >> Stay informed about: Outlook RPC over HTTp deosn't work 

are you on Vista?

--
Kevin Weilbacher [SBS MVP]
"The days pass by so quickly now, the nights are seldom long"
*

"Barry Lee" <BarryLee.TakeThisOut@discussions.microsoft.com> wrote in message
news:DD239732-191D-4E25-8941-460A9C66D34E@microsoft.com...
> Hi Nathan
> how to fix this step ??
> B. If the certificate is not trusted, a warning popup appears. Click View
> Certificate, click Install Certificate, and then follow the instructions.
> when i open
> http://mail.mydomain.com/exchange
> there is a problem with this websites's security certificate.
> the xecurity cerficate by this website was not issued by trusted
> certificate
> authonity.
> the xecurity cerficate by this website was not issued for a different
> website's address.
> we recommend that you cloas this webpage ans do not continue to this
> website .
> 1. click here to close this website .
> 2.continue to this website (not recommended).
> more information
> Thx
> Barry
>
>
>
>
>
> "Nathan Liu [MSFT]" wrote:
>
>> Hello Lily,
>>
>> Thank you for posting in the SBS newsgroup.
>>
>> According to your description, I understand that you received the error
>> message "'The connection to the Microsoft Exchange Erver is
>> unavailable¡­"
>> when you try to use RPC over HTTP to connect the Exchange Server. If I
>> have
>> misunderstood your concern, please don't hesitate to let me know.
>>
>> 1. In SBS 2003, we don't have to manually configure RPC over HTTP. We
>> can
>> follow the steps below to enable RPC over HTTP:
>>
>> A. Make sure you have enabled "Outlook over the Internet" and "Remote Web
>> Workplace" in the CEICW (Configure E-mail and Internet Connection
>> wizard),
>> then you will logon to the Remote Web Workplace
>> (https://serverfqdn/remote)
>> as a user from the remote client and look at the link for "Configure
>> Outlook via the Internet". You can see it from the server by going into
>> https://localhost/remote. If the option is not displayed, then the
>> feature
>> is not configured on the server.
>>
>> B. Click "Configure Outlook via the Internet" and then the Web page
>> "Using
>> Outlook via the Internet" will appear which has pretty much a step by
>> step
>> list of instructions. If it tells you to use "server.domain.local", use
>> that. If it tells you to use "server.domain.com", use that. Follow the
>> steps exactly.
>>
>> References:
>>
>> 825763 How to configure Internet access in Windows Small Business Server
>> 2003
>> http://support.microsoft.com/?id=825763
>>
>> Windows Small Business Server 2003 Getting Started Guide
>> Appendix C - Network Configuration Settings
>> http://www.microsoft.com/technet/prodtechnol/sbs/2003/plan/gsg/appx_c.mspx
>>
>> 2. To troubleshooting RPC over HTTP related issue:
>>
>> A. From the Internet client, browse to https://FQDN/rpc. In order for RPC
>> over HTTP to work, you must be able to browse to this URL without getting
>> a
>> popup warning about the certificate. You will receive the following error
>> on the page:
>>
>> The page cannot be displayed
>> HTTP Error 403.2 - Forbidden: Read access is denied.
>> Internet Information Services (IIS)
>>
>> This is normal. The idea is to be able to get to that page without
>> getting
>> the popup warning about the certificate.
>>
>> B. If URLScan is installed on the SBS server, in some configurations, it
>> is
>> necessary to make the following changes in urlscan.ini in order for RPC
>> over HTTP to work:
>>
>> [RequestLimits]
>> ; The entries in this section impose limits on the length
>> ; of allowed parts of requests reaching the server.
>> MaxAllowedContentLength=2000000000
>> MaxUrl=16384
>> MaxQueryString=4096
>>
>> In addition, you need to add the following verbs to the Allow Verbs:
>>
>> RPC_IN_DATA
>> RPC_OUT_DATA
>>
>> After editing the ini file, restart IIS Admin Service and Microsoft ISA
>> Server Control services.
>>
>> Reference:
>>
>> 823175 Fine-tuning and known issues when you use the Urlscan utility in
>> an
>> Exchange 2003 environment
>> http://support.microsoft.com/?id=823175
>>
>> 3. Start outlook with the /rpcdiag switch, does that provide any
>> direction?
>>
>> 4. On the SBS server, verify if it trusts the certificate:
>>
>> A. Open Internet Explorer, and then in the address bar type:
>> https://publishing.yourdomain.local/remote
>>
>> B. If the certificate is not trusted, a warning popup appears. Click View
>> Certificate, click Install Certificate, and then follow the instructions.
>>
>> 5. On the SBS server, open IIS Manager, expand your server\Web Service
>> Extensions, is RPC Proxy Server Extension allowed? If so, double-click
>> it,
>> check if it is using "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll". If it
>> is
>> using "C:\WINDOWS\system32\rpcproxy.dll", remove it and add
>> "C:\WINDOWS\system32\rpcproxy\rpcproxy.dll" on the Required Files tab.
>> Run
>> "iisreset" and see how it goes.
>>
>> 6. How many NIC installed on your SBS server. Is ISA also installed? Is
>> there any software firewall enabled on the SBS server? Generally, for RPC
>> over HTTP, we just need to open the incoming TCP port 80 and 443 on the
>> hardware firewall.
>>
>> 7. Please do a screen capture of this issue on the Outlook client, and
>> then
>> attach it in your reply.
>>
>> I am appreciated your time and cooperation. If anything is unclear,
>> please
>> feel free to let me know. I am looking forward to hearing from you.
>>
>> Best regards,
>>
>> Nathan Liu (MSFT)
>> Microsoft CSS Online Newsgroup Support
>> Get Secure! - www.microsoft.com/security
>> =====================================================
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> --------------------
>> >Thread-Topic: Outlook RPC over HTTp deosn't work
>> >thread-index: AcWFxQ2Hc31WhoftSi61Vr9ffXKqNQ==
>> >X-WBNR-Posting-Host: 203.25.66.146
>> >From: "=?Utf-8?B?TGlseQ==?=" <Lily.TakeThisOut@discussions.microsoft.com>