I had RPC over HTTPS working fine with Outlook 2003 (and our Exchange Server
2003) but at some point it stopped working - I suspect after I upgraded my
laptop to Outlook 2007. What happens now is that if I enable Outlook
Anywhere I get repeated prompts for username and password. If I turn Outlook
Anywhere back off, they go away. I have seen an MS article about
LMCompatability in the registry and that does not appear to be the problem
(the compatability level is set to 3).

It may be that Outlook is getting confused because we have only one Exchange
server, but it has two different network adapters and addresses. Internally
it is called 'apollo' and externally it is known as 'mailgate'. The mailgate
address is published by DNS servers but no one can access apollo from
outside our firewall. Although it is the mailgate address that I have put
into Outlook Anywhere, the password prompt that comes up says it is for the
apollo server, which I don't think is correct.

I have tried using the mailgate address both in setting up the main Exchange
server address in Outlook but that always gets changed automatically back to
apollo.

I have changed nothing has changed on the Exchange server end except for
allowing Microsoft Update Services to install updates. I have tried changing
the RPC port table in the registry from 'apollo' to 'mailgate' but this has
no apparent effect.

Regards,

William

did you try using hosts for apollo?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"William Hudson" wrote in message
...
I had RPC over HTTPS working fine with Outlook 2003 (and our Exchange
Server 2003) but at some point it stopped working - I suspect after I
upgraded my laptop to Outlook 2007. What happens now is that if I enable
Outlook Anywhere I get repeated prompts for username and password. If I
turn Outlook Anywhere back off, they go away. I have seen an MS article
about LMCompatability in the registry and that does not appear to be the
problem (the compatability level is set to 3).

It may be that Outlook is getting confused because we have only one
Exchange server, but it has two different network adapters and addresses.
Internally it is called 'apollo' and externally it is known as 'mailgate'.
The mailgate address is published by DNS servers but no one can access
apollo from outside our firewall. Although it is the mailgate address that
I have put into Outlook Anywhere, the password prompt that comes up says
it is for the apollo server, which I don't think is correct.

I have tried using the mailgate address both in setting up the main
Exchange server address in Outlook but that always gets changed
automatically back to apollo.

I have changed nothing has changed on the Exchange server end except for
allowing Microsoft Update Services to install updates. I have tried
changing the RPC port table in the registry from 'apollo' to 'mailgate'
but this has no apparent effect.

Regards,

William

Diane -

Sorry, but I don't understand the question. 'apollo' is not visible outside
of our local network so it is not useful as a host name when I travelling.
Is that what you meant?

Regards,

William


"Diane Poremsky [MVP]" wrote in message
...
did you try using hosts for apollo?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"William Hudson" wrote in message
...
I had RPC over HTTPS working fine with Outlook 2003 (and our Exchange
Server 2003) but at some point it stopped working - I suspect after I
upgraded my laptop to Outlook 2007. What happens now is that if I enable
Outlook Anywhere I get repeated prompts for username and password. If I
turn Outlook Anywhere back off, they go away. I have seen an MS article
about LMCompatability in the registry and that does not appear to be the
problem (the compatability level is set to 3).

It may be that Outlook is getting confused because we have only one
Exchange server, but it has two different network adapters and addresses.
Internally it is called 'apollo' and externally it is known as
'mailgate'. The mailgate address is published by DNS servers but no one
can access apollo from outside our firewall. Although it is the mailgate
address that I have put into Outlook Anywhere, the password prompt that
comes up says it is for the apollo server, which I don't think is
correct.

I have tried using the mailgate address both in setting up the main
Exchange server address in Outlook but that always gets changed
automatically back to apollo.

I have changed nothing has changed on the Exchange server end except for
allowing Microsoft Update Services to install updates. I have tried
changing the RPC port table in the registry from 'apollo' to 'mailgate'
but this has no apparent effect.

Regards,

William

in windows there is a file called hosts that contains names and ip addresses
windows can use for resolution rather than a dns server. Use it to assign
apollo to the mailgate ip.

also - are you trying to set this up inside the network or are you outside
the network?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"William Hudson" wrote in message
...
Diane -

Sorry, but I don't understand the question. 'apollo' is not visible
outside of our local network so it is not useful as a host name when I
travelling. Is that what you meant?

Regards,

William


"Diane Poremsky [MVP]" wrote in message
...
did you try using hosts for apollo?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"William Hudson" wrote in message
...
I had RPC over HTTPS working fine with Outlook 2003 (and our Exchange
Server 2003) but at some point it stopped working - I suspect after I
upgraded my laptop to Outlook 2007. What happens now is that if I enable
Outlook Anywhere I get repeated prompts for username and password. If I
turn Outlook Anywhere back off, they go away. I have seen an MS article
about LMCompatability in the registry and that does not appear to be the
problem (the compatability level is set to 3).

It may be that Outlook is getting confused because we have only one
Exchange server, but it has two different network adapters and
addresses. Internally it is called 'apollo' and externally it is known
as 'mailgate'. The mailgate address is published by DNS servers but no
one can access apollo from outside our firewall. Although it is the
mailgate address that I have put into Outlook Anywhere, the password
prompt that comes up says it is for the apollo server, which I don't
think is correct.

I have tried using the mailgate address both in setting up the main
Exchange server address in Outlook but that always gets changed
automatically back to apollo.

I have changed nothing has changed on the Exchange server end except for
allowing Microsoft Update Services to install updates. I have tried
changing the RPC port table in the registry from 'apollo' to 'mailgate'
but this has no apparent effect.

Regards,

William