Re: Initial login problems via RPC over HTTP...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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

"centre21" wrote:

On Dec 28, 6:43 am, "hollenal" <newsgr...@xxxxxxxxxxxxxxxx> wrote:
Same here.
Easiest solution for me was to open a VPN connection into the server before
configuring RPC over HTTP.

Rgds.

"centre21" <centr...@xxxxxxxxx> schrieb im Newsbeitragnews:4e49b807-ad7e-490f-ab95-39a417d8efd9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

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.

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

.

Relevant Pages

  • Re: Exchange, Outlook and DNS problem
    ... > Company deceided to switch from ISP POP3 to local Exchange server. ... > Cisco routes to local ISA IP address.ISA is configured to do RPC over ... > HTTP routing for Exchange which is also located in internal network. ... > Outlook while connected internal network. ...
    (microsoft.public.win2000.dns)
  • RE: Requesting data from Microsoft Exchange Server.
    ... Exchange Server" while VPN to the server. ... What is your network topology? ... Is it site to site VPN or client to side VPN ... Disable Instant messaging in Outlook 2002. ...
    (microsoft.public.exchange2000.clients)
  • Re: Diagnosing client connection problems
    ... Can you successfully login with OWA over the VPN when Outlook users start having issues? ... Do the Outlook users at the main location have issues with Outlook when the Remote office is having problems? ... You need to narrow the issue down to Exchange at main location or VPN issues with remote offices ... users at both remote offices start receiving "Your Microsoft Exchange Server ...
    (microsoft.public.exchange.connectivity)
  • Re: Connecting Outlook via VPN
    ... > What is the proper procedure for connecting Outlook client ... Connect via VPN and make sure they can ping the Exchange server by name. ...
    (microsoft.public.exchange2000.clients)
  • Re: RPC over HTTP not configuring after Office 2007 SP2 install
    ... Other than that and my best recommendation is to contact the Exchange host provider to see if they are aware of this change in SP2 for Office/Outlook 2007 and/or verify that the KB article applies/resolves the issue. ... "An RPC Error was thrown by the RPC ... With this previous part in mind, is there a way to "trick" Outlook 2007 SP2 ... "No RFR Service" registry value on their exchange server and this could come ...
    (microsoft.public.outlook.installation)