Outlook2003 via RPC over HTTP (Full Version)

All Forums >> [Microsoft Exchange 2003] >> General



Message

bist -> Outlook2003 via RPC over HTTP (1.Oct.2003 5:46:00 PM)

people,

I followed the guid which explains how to set it up. At a certain moment in the guide it states that you must select basic authentication. But in my outlook client I can only select (kerberos and ntlm)

This is probably the reason why I cannot connect my client to the exchange server.

Anyone any suggestions?



Henrik Walther -> RE: Outlook2003 via RPC over HTTP (1.Oct.2003 7:34:00 PM)

bist,

You can't select basic authentification under the security tab in the mail profile, you should as you already did, choose Kerberos/NTLM Password Authentification.

Is it the new guide here on MSExchange.org you're following ?

I can recommend you look in the very end of Tom Shinders article, which you can find here - it provides detailed instructions on how you setup the client profile.



bist -> RE: Outlook2003 via RPC over HTTP (1.Oct.2003 10:11:00 PM)

no go,,,I doesn't work. Should I open some ports? I don't think so.

The guide which is available on this site doesn't work. Maybe I'm missing something.

Anyone any ideas?



Henrik Walther -> RE: Outlook2003 via RPC over HTTP (2.Oct.2003 8:27:00 AM)

You must have configured something else wrong then, because RPC over HTTP setup works with Kerberos/NTLM Password Authentification chosen (my setup does too!).

What do you mean the link doesn't work ? Do you get a page cannot be displayed or what ?

Try to enter page through:

http://www.tacteam.net/isaserverorg/exchangekit/

And pick article 14.



bist -> RE: Outlook2003 via RPC over HTTP (2.Oct.2003 2:08:00 PM)

sorry,, I didn't make it clear. What i meant was that I've followed the document but this is not bringing the solution. Also, the article is about how you should enable it via ISA server. I did everything on the page but it still doesn't work. When I create the outlook exchange profile it says that the exchange server is not available.

That's the errror I get when trying to log on on the exhange server remotely via RPC over HTTPS.



Henrik Walther -> RE: Outlook2003 via RPC over HTTP (2.Oct.2003 3:16:00 PM)

And you have created the RPC over HTTP profile while connected to the network, where the Exchange Server resides ? You have to as RPC communication is required when you create the profile.

I know the article is for ISA publishing, but the end of article concerning client configuration was what I refered to.

I don't use ISA either (yet!), but have followed the mention article and it works perfectly.



bist -> RE: Outlook2003 via RPC over HTTP (2.Oct.2003 3:26:00 PM)

ooh ok. Now I get it. My problem is that I don't have the possibility to connect directly to the server. So I cannot setup the account over RPC first and then change the profile.

Is there no other way to do that. Because in the article which is available on the home page it says that this would be ideal for ISP's. But in my understanding you do not have a direct connection either to the ISP's exchange server. So there is no way I can setup RPC over HTTPS without setting up the profile first via RPC?



Henrik Walther -> RE: Outlook2003 via RPC over HTTP (2.Oct.2003 3:32:00 PM)

I heard MS would come up with some scripts for customizing the RPC over HTTP environment, but don't know when.

But you should be able to create the profile with profgen.exe utility from the Exchange Server Resource Kit.



bist -> RE: Outlook2003 via RPC over HTTP (2.Oct.2003 3:37:00 PM)

ok thnx. I will try this tonight. Maybe it is a good idea to post that to the article because this is not very clear.

I'll keep you posted if it worked.

Thnx for the help you guys are providing.



bist -> RE: Outlook2003 via RPC over HTTP (2.Oct.2003 9:30:00 PM)

Sorry,,didn't work. I did every single step I ever found on this subject. I just can't get it to work. Any more suggestions?

I got the profile configured. But when I try to connect he just hangs for a while and the says that the exchange server is not available



gjackson78 -> RE: Outlook2003 via RPC over HTTP (9.Oct.2003 12:45:00 AM)

My question is how do I initially set up a profile over RPC initially and inside my network? My FQDN for my website is outside my network and I can't access my exchange server using that name internally. Help.

Gary



Henrik Walther -> RE: Outlook2003 via RPC over HTTP (9.Oct.2003 8:02:00 PM)

Just insert the internal Exchange server name, it's only under the RPC over HTTP tab you need to enter the external FQDN.



gjackson78 -> RE: Outlook2003 via RPC over HTTP (9.Oct.2003 8:38:00 PM)

Ok. I have done this. Under the Proxy settings in the client I've set up my FQDN along with Basic Auth and checked the two HTTP fast/slow network options then under the first box I've typed in my local exchange server name and typed in a username. When I hit "Check name", I get the OWA user prompt wanting username and password. I typed in the domain\user and password and hit ok. Outlook seemed to hang or freeze for about 5 minutes and then timed out saying it couldn't establish a connection to the exchange server. This is in fact remotely outside of my network. I have 443 open on the firewall as well as 135. What am I doing wrong as to why I can't get the names to resolve over the net?



abraham -> RE: Outlook2003 via RPC over HTTP (9.Oct.2003 9:37:00 PM)

Hi.

To troubleshoot this problem, use one of the following methods.
Method 1: Use RPCPing.exe
Note RPCPing.exe is included with the Windows Server 2003 Resource Kit Tools. To download the resource kit tools, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en

To use RPCPing.exe to identify this problem, follow these steps:
On the client computer, click Start, click Run, type cmd.exe in the Open box, and then click OK.
Type the following command, where user and domain are the user name and domain that you use to log on to Outlook :
rpcping.exe -t ncacn_http -s ExchangeServerName -o RpcProxy=ProxyServerName -P "user,domain,*" -H 1 - u 10 -a connect -F 3 -E -R none

The other parameters must be defined to connect to your Exchange server in the same way that Outlook does.
When you are prompted to do so, type your password.
Notice that RPCPing.exe generates the following output:

RPCPinging proxy server ServerName with Echo Request Packet
Send ping to server
Error 12175 returned in the WinHttpSedRequest
Ping Failed
Method 2: Verify the Certificate
If the RPC Proxy computer is also configured to be a Microsoft Outlook Web Access (OWA) server, start Microsoft Internet Explorer and log on to your OWA mailbox. When you log on, use the same server name that you used for your Outlook RPC Proxy. If you receive a message that you do not have access to the RPC Proxy computer, click View Certificate, and then verify that the certificate was issued to the server that you are trying to log on to



Henrik Walther -> RE: Outlook2003 via RPC over HTTP (9.Oct.2003 10:45:00 PM)

quote:
Originally posted by gjackson78:
This is in fact remotely outside of my network. I have 443 open on the firewall as well as 135. What am I doing wrong as to why I can't get the names to resolve over the net?
I thought you did the Outlook profile setup on the internal network ?

If not use PROFGEN.EXE or something similar to setup the profile.



gjackson78 -> RE: Outlook2003 via RPC over HTTP (10.Oct.2003 4:20:00 AM)

I did. However when I click on connection status in Outlook 2003 it disconnects HTTP and goes to TCP/IP. It tries to do HTTP but nothing happens.

help me with the rpcping. Do I do this inside my network or outside? If my server is server1 and the FQDN that I use to configure outlook 2003 remotely for HTTP is secure.solutions.net what is the rpc command? Whenever I run the rpcping command it comes back with the switches and the explanations.

This is getting frustrating.



abraham -> RE: Outlook2003 via RPC over HTTP (10.Oct.2003 4:41:00 AM)

Hi. You can run RPCPING from Outside

rpcping.exe -t ncacn_http -s server1 -o RpcProxy=secure.solutions.net -P "user,domain,*" -H 1 - u 10 -a connect -F 3 -E -R none

Do you have a FE, BE Configuration??

Check this

http://support.microsoft.com/default.aspx?scid=kb;EN-US;167260

Regards



gjackson78 -> RE: Outlook2003 via RPC over HTTP (10.Oct.2003 4:59:00 AM)

I have a backend server. This is my home network so my exchange and DC are the same. ok I ran that rpcping from an outside source and I got the prompt to enter a password for the HTTP proxy. I typed in the password for the user "gjackson" that I had entered in the rpcping command and I got a "ping failed" response. I have 80 and 443 enabled into my network on my firewall.



abraham -> RE: Outlook2003 via RPC over HTTP (10.Oct.2003 5:05:00 AM)

Hi. Are you using SSL, or have the option (My server require authentication selected on the Client)?



gjackson78 -> RE: Outlook2003 via RPC over HTTP (10.Oct.2003 5:10:00 AM)

Yup sure do. Have SSL working on the server just fine with OWA. Is there something that needs to be done on the Exchange website in IIS? When I try to set up the client I immediately get an OWA-like login screen when I hit check name....but then after 4 minutes of Outlook hanging it finally says unable to establish connection with the Exchange server. ON the "Check name" window I have the local server name of my exchange server entered and then under the Exchange over HTTP settings i have the "secure.solutions.net" one...(btw, its not really secure.solutions.net...)..but anyway... what about the security settings? I have basic auth and the two HTTP first over fast and slow boxes checked... no Mutual SSL..



Page: [1] 2 3   next >   >>