RE: RPC over HTTP
- From: v-terliu@xxxxxxxxxxxxxxxxxxxx (Terence Liu [MSFT])
- Date: Mon, 09 Jul 2007 06:37:41 GMT
Hello Bob,
Thank you for posting here.
According to your description, I understand that you want to ask 4
questions about RPC over http. If I have misunderstood the problem, please
don't hesitate to let me know.
Please understand that our newsgroup is an issue based service, meaning we
usually respond to one question/issue per post. This will lessen the
confusion for both of us, as well as ensure that our results are accurate
and not a result of a test for a different question. Therefore, I will work
with you on the first question in this post. Regarding the additional
questions, I will give you some general info, for detail steps, I suggest
you create a new post for getting more quick assistance.
1. NTLM and Basic Authentication for RPC over HTTP:
Since the remote users cannot join domain, we do not need to use NTLM, this
authentication is just for domain users. The remote user can not connect DC
directly, so the NTLM will fail. Therefore, please use the recommended
Basic Authentication for RPC over HTTP.
2. We cannot use username rather than Domain\Username when logon.
3. RPC over http is use for remote users, for the client can only use one
TCP port to connect Exchange server by Outlook, it is easy to go through
firewall between SBS and remote Outlook client. Otherwise, the RPC over
http is safer than RPC, and the RPC over https will be safest.
4. This is a Exchange mailbox permission issue, you have to give permission
of the mailbox to the domain user account who need to access the mailbox.
Additional, I like to show you the detail steps to configure RPC over HTTP:
Using Outlook via the Internet
If you are using Microsoft? Office Outlook? 2003, you can connect to the
computer running Windows? Small Business Server through the Internet using
the feature called RPC over HTTP. This means you can remotely access your
server e-mail account from the Internet when you are working outside your
organization's firewall. You do not need security-related hardware or
software (such as smart cards or security tokens), and you do not have to
establish a virtual private network (VPN) connection to the server.
Comparing RPC over HTTP and Outlook Web Access
When using RPC over HTTP to access your mailbox, you get the full
functionality of Outlook 2003. For example, you can work offline, use
Microsoft Office Word 2003 as your e-mail editor, and easily organize your
mailbox.
To use Outlook via the Internet
Ensure that the following requirements have been met on the client computer:
Verify that the computer is running Microsoft Windows XP Service Pack 1 or
later
Click Start, right-click My Computer, and then click Properties.
The version of the operating system and service pack is displayed under
System. If you do not see a service pack version, there is no service pack
installed.
Verify that Windows update Q331320 is installed on the computer (not
required if you are running Windows XP Service Pack 2 or later)
1. Click Start, click Control Panel, and then open Add or Remove Programs.
2. Under Currently installed programs, search for the item Windows XP
Hotfix (SP2) Q331320.
3. If the item is not present, go to the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=18651) and follow the instructions
to download and install it.
Verify that the computer is running Outlook 2003 or later
1. Open Outlook.
2. Click the Help menu, and then click About Microsoft Office Outlook. The
version number appears at the top of the box.
Verify that the computer trusts the certificate used by the server
1. Open Internet Explorer, and then in the address bar type:
https://www.sbsc.com/remote
a. If the certificate is trusted, a certificate warning does not appear. In
this case, continue with step 1 under Ensure that you have an Outlook
profile configured for the server.
b. If the certificate is not trusted, a warning appears. Click View
Certificate, click Install Certificate, and then follow the instructions.
Ensure that you have an Outlook profile configured for the server
1. Click Start, and then click Control Panel.
a. If you are viewing Control Panel in the default Category view, switch to
Classic view, and then double-click Mail.
b. If you are viewing Control Panel in Classic view, double-click Mail.
2. In the Mail Setup dialog box, click Show Profiles. If your profile
appears in the list, select your profile, click Properties, click E-mail
Accounts, select View or change existing e-mail accounts, and then click
Next. If your profile does not appear, open Outlook and follow the
instructions to create a profile before proceeding.
a. If Microsoft Exchange Server does not appear in the list, the existing
profile is not associated with a Microsoft Exchange Server e-mail account.
Click Cancel, and then click Close. Continue with step 3 to add a profile.
b. If there is an existing Microsoft Exchange Server profile, continue with
step 3 under Configure the computer for RPC over HTTP.
3. Click Add. The New Profile dialog box appears.
4. In the Profile Name box, type a name for the new profile, and then click
OK. The E-mail Accounts dialog box appears.
5. Under E-mail, select Add a new e-mail account, and then click Next. The
Server Type dialog box appears.
6. Click Microsoft Exchange Server, and then click Next.
7. Continue with step 4 under Configure the computer for RPC over HTTP.
Configure the computer for RPC over HTTP
1. Click Start, and then click Control Panel.
a. If you are viewing Control Panel in the default Category view, switch to
Classic view, and then double-click Mail.
b. If you are viewing Control Panel in Classic view, double-click Mail.
2. In the Mail Setup dialog box, click E-mail accounts, click View or
change existing e-mail accounts, and then click Next.
3. In the E-mail accounts dialog box, click Microsoft Exchange Server, and
then click Change.
4. In the Microsoft Exchange Server box, type the local name of the
Exchange server:
sbsserver.SBSC.local
5. In the User Name box, type the user name that you use to log on to the
Remote Web Workplace. Do not click Check Name.
6. In the Exchange Server settings page, click More Settings.
7. On the Connection tab, under Exchange over the Internet, select Connect
to my Exchange mailbox using HTTP, and then click Exchange Proxy Settings.
The Exchange Proxy Settings dialog box appears.
8. Under Use this URL to connect to my proxy server for Exchange, type the
following URL:
www.sbsc.com
9. Select Connect using SSL only, and then select Mutually authenticate the
session when connecting with SSL.
10. In the Principal name for proxy server box, type the following text:
msstd:www.sbsc.com
11. Select On slow networks, connect using HTTP first, then connect using
TCP/IP.
12. Under Proxy authentication settings, select Basic Authentication.
13. Click OK, and then click OK again. Click Next, and then click Finish.
Click Close.
14. In the Mail dialog box, if Always use this profile is selected, choose
the newly configured profile.
15. Open Outlook and type your Windows Small Business Server user name (in
the format SBSC\user name) and password. You can now work with your Outlook
mailbox.
Hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: bob.smith.0182@xxxxxxxxx
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: RPC over HTTP
| Date: Fri, 06 Jul 2007 22:02:36 -0700
| Organization: http://groups.google.com
| Lines: 32
| Message-ID: <1183784556.018428.121820@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 203.206.115.31
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1183784556 21669 127.0.0.1 (7 Jul 2007
05:02:36 GMT)
| X-Complaints-To: groups-abuse@xxxxxxxxxx
| NNTP-Posting-Date: Sat, 7 Jul 2007 05:02:36 +0000 (UTC)
| User-Agent: G2/1.0
| X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
InfoPath.2; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
| Complaints-To: groups-abuse@xxxxxxxxxx
| Injection-Info: i13g2000prf.googlegroups.com; posting-host=203.206.115.31;
| posting-account=wFYR4gwAAAA4F5_mBx7TA-uugU3cdUOR
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed.
cw.net!cw.net!news-FFM2.ecrc.de!news.glorb.com!postnews.google.com!i13g2000p
rf.googlegroups.com!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:48789
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi All,
|
| Just some questions about RPC over HTTP (first two relate to an
| external client machine NOT joined to domain):
|
| 1. Can we use NTLM rather than Basic Authentication and how do i
| configure it - i tried to get the IIS sub directory RPC to use NTLM
| authentication and the outlook client but when it tries to use NTLM,
| it does not allow me to log on - even though passwords are right, it
| repeatedly keeps on prompting for username and password.
|
| 2. How do we get it so that you DO NOT need to type Domain\Username
| when logging onto RPC over HTTP, only need to type Username and then
| password?
|
| 3. Which is more secure to use internally (i.e. within own office
| building):
| a) RPC over HTTP
| b) Just normal connection without configuring RPC over HTTP settings
|
| 4. Our company has two email accounts: an info @ domain.com and a
| sales @ domain.com account, which my boss wants all staff to access.
| All staff have their own CALs for logon to SBS. Is there any way for
| them to establish a profile in Outlook, that opens up the info @
| domain.com Email account (the info and sales accounts have their own
| CALs for Exchange to collect mail via POP3), however when they are
| logging on, must prompt for username and password and instead of using
| the info @ domain.com's CAL details, but instead allow them to use
| their own CAL logons.
|
| Thanks a lot
|
|
.
- References:
- RPC over HTTP
- From: bob . smith . 0182
- RPC over HTTP
- Prev by Date: Re: Roaming profile and my documents redirection not working with domain users on reinstal
- Next by Date: RE: company web. Error adding a web part
- Previous by thread: RPC over HTTP
- Next by thread: Re: RPC over HTTP
- Index(es):
Relevant Pages
|
