Initial login problems via RPC over HTTP...

[centre21]

I have a problem that has been plaguing me since Microsoft implemented
RPC over HTTP. It seems if I'm on the internal network, I can
configure RPC over HTTP, logon and never have a problem. But if I'm
out of the office and configure RPC over HTTP, my initial logon always
fails. My domain, ID and password are never accepted and I cannot log
into Outlook. Once I go into the office it works just fine and I never
have logon problems again.

Has anyone seen this issue and know why it happens? I've been looking
for an answer for this for 3 years.

Thanks in advance.

 

[Milly Staples [MVP - Outlook]]

When you first configure RPC over HTTPS, you must have direct access to the
exchange server, e.g., connected to the exchange domain. If you try to
confiure it remotely, it will fail.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact.
ALWAYS post your Outlook version.
How to ask a question: http://support.microsoft.com/KB/555375


After furious head scratching, centre21 asked:

| I have a problem that has been plaguing me since Microsoft implemented
| RPC over HTTP. It seems if I'm on the internal network, I can
| configure RPC over HTTP, logon and never have a problem. But if I'm
| out of the office and configure RPC over HTTP, my initial logon always
| fails. My domain, ID and password are never accepted and I cannot log
| into Outlook. Once I go into the office it works just fine and I never
| have logon problems again.
|
| Has anyone seen this issue and know why it happens? I've been looking
| for an answer for this for 3 years.
|
| Thanks in advance.

 

[hollenal]

Same here.
Easiest solution for me was to open a VPN connection into the server before
configuring RPC over HTTP.

Rgds.

 

[centre21]

When you first configure RPC over HTTPS, you must have direct access to the
exchange server, e.g., connected to the exchange domain.  If you try to
confiure it remotely, it will fail.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact.
ALWAYS post your Outlook version.
How to ask a question:http://support.microsoft.com/KB/555375

After furious head scratching, centre21 asked:

| I have a problem that has been plaguing me since Microsoft implemented
| RPC over HTTP. It seems if I'm on the internal network, I can
| configure RPC over HTTP, logon and never have a problem. But if I'm
| out of the office and configure RPC over HTTP, my initial logon always
| fails. My domain, ID and password are never accepted and I cannot log
| into Outlook. Once I go into the office it works just fine and I never
| have logon problems again.
|
| Has anyone seen this issue and know why it happens? I've been looking
| for an answer for this for 3 years.
|
| Thanks in advance.

Okay, that's what I thought. Thanks for the tip.

 

[centre21]

Same here.
Easiest solution for me was to open a VPN connection into the server before
configuring RPC over HTTP.

Rgds.

I thought this might be the issue. I'll see what I can do about the
VPN.
Thanks

 

[Lumberjack]

I can connect to my office Exchange server when in the office (LAN) but I
cannot connect outside with Outlook.

I can only use the webmail after entering a web VPN access:
- First portal for VPN : https://xxx.yyy.com --> I enter my
user_VPN/password_VPN
- On the next web page, I have the choice for the webmail and it's a link as
https://xxx.yyy.com/go/webmail.yyy.com~ssl where I can enter my
user_mail/password_mail

So I can't enter the url in RPC as every slash is forbidden

In my Outlook, the Exchange server (EXC.yyy.com) is not reachable by ping
(or tracert) and I can't resolve it even after entering the VPN.

I use Outlook 2007 and the Exchanger server shall be 2003. For my collegue,
he's using Outlook2003 and after entering the same web VPN, he just have to
launch Outlook to retrive mail (without RPC). (I tried is user name and vice
versa so it's not a right issue).

Regards