Outlook RPC over Http and ISA  
Author Message
SamSayers





PostPosted: Sat Jan 06 13:36:38 PST 2007 Top

SBS >> Outlook RPC over Http and ISA Hello,
following Setup:
-SBS 2003 (ISA Server 2004)
-XP Client SP2
-OWA is working fine
-Certificate is accepted by the server and client
-Secure Web Server was published in ISA vie SSL Bridging

I am trying to get RPC-HTTP working. Used to work before ISA 2004 was
installed.
I followed the instructions from the Microsoft site, but still can't get
access to the server. Outlook can't connect to the exchange server.

I tried https://FQDN/RPC and https://FQDN/rpcproxy.dll (access should be
denied), but the only message I get is 'principal name could not be
resolved'.

I am really strugling with that problem, because I think there must be an
easy solution to this problem.

Thank you for any hints!!!!
Marc

Information Technology1  
 
 
Steve





PostPosted: Sat Jan 06 13:36:38 PST 2007 Top

SBS >> Outlook RPC over Http and ISA You say you followed instructions on the Microsoft site-what were they?
Typically you should only need to run the CEICW and then follow the specific
instructions found on the RWW page about Outlook over the Internet. I have
never had a failure yet to setup Outlook over RPC/HTTP with ISA 2004
installed.

"Marc" <EMail@HideDomain.com> wrote in message
news:EMail@HideDomain.com...
> Hello,
> following Setup:
> -SBS 2003 (ISA Server 2004)
> -XP Client SP2
> -OWA is working fine
> -Certificate is accepted by the server and client
> -Secure Web Server was published in ISA vie SSL Bridging
>
> I am trying to get RPC-HTTP working. Used to work before ISA 2004 was
> installed.
> I followed the instructions from the Microsoft site, but still can't get
> access to the server. Outlook can't connect to the exchange server.
>
> I tried https://FQDN/RPC and https://FQDN/rpcproxy.dll (access should be
> denied), but the only message I get is 'principal name could not be
> resolved'.
>
> I am really strugling with that problem, because I think there must be an
> easy solution to this problem.
>
> Thank you for any hints!!!!
> Marc
>
>


 
 
Kevin





PostPosted: Sat Jan 06 21:06:03 PST 2007 Top

SBS >> Outlook RPC over Http and ISA I agree with Steve, rerunning CEICW should have been all you needed to do.

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"Marc" <EMail@HideDomain.com> wrote in message
news:EMail@HideDomain.com...
> Hello,
> following Setup:
> -SBS 2003 (ISA Server 2004)
> -XP Client SP2
> -OWA is working fine
> -Certificate is accepted by the server and client
> -Secure Web Server was published in ISA vie SSL Bridging
>
> I am trying to get RPC-HTTP working. Used to work before ISA 2004 was
> installed.
> I followed the instructions from the Microsoft site, but still can't get
> access to the server. Outlook can't connect to the exchange server.
>
> I tried https://FQDN/RPC and https://FQDN/rpcproxy.dll (access should be
> denied), but the only message I get is 'principal name could not be
> resolved'.
>
> I am really strugling with that problem, because I think there must be an
> easy solution to this problem.
>
> Thank you for any hints!!!!
> Marc
>
>


 
 
Charlie





PostPosted: Sun Jan 07 09:08:17 PST 2007 Top

SBS >> Outlook RPC over Http and ISA Stop obsessing about what's on the general MS site, and use the wizards. ;)
The wizards are your friend. In this case, the CEICW - rerun it, making sure
you specify Outlook over the Internet is allowed. Then connect to RWW and
click on the link on the right hand side for instructions on exactly what to
plug in to Outlook to make it all work. As usual, the wizards at MS who
wrote the SBS Wizards have made our lives a whole lot easier.

--
Charlie.
http://msmvps.com/blogs/xperts64

"Marc" <EMail@HideDomain.com> wrote in message
news:EMail@HideDomain.com...
> Hello,
> following Setup:
> -SBS 2003 (ISA Server 2004)
> -XP Client SP2
> -OWA is working fine
> -Certificate is accepted by the server and client
> -Secure Web Server was published in ISA vie SSL Bridging
>
> I am trying to get RPC-HTTP working. Used to work before ISA 2004 was
> installed.
> I followed the instructions from the Microsoft site, but still can't get
> access to the server. Outlook can't connect to the exchange server.
>
> I tried https://FQDN/RPC and https://FQDN/rpcproxy.dll (access should be
> denied), but the only message I get is 'principal name could not be
> resolved'.
>
> I am really strugling with that problem, because I think there must be an
> easy solution to this problem.
>
> Thank you for any hints!!!!
> Marc
>
>

 
 
Colin





PostPosted: Sun Jan 07 10:20:01 PST 2007 Top

SBS >> Outlook RPC over Http and ISA Hu guys,

On this note, to get Outlook over http working successfully, does TCP port
80 need to be opened up ? As it's the most attacked, I really don't want to
do this but so far, all I've found on configuring Outlook over http suggests
that this step is necessary. Can it be done using https only ?

Regards Colin.

"Charlie Russel - MVP" wrote:

> Stop obsessing about what's on the general MS site, and use the wizards. ;)
> The wizards are your friend. In this case, the CEICW - rerun it, making sure
> you specify Outlook over the Internet is allowed. Then connect to RWW and
> click on the link on the right hand side for instructions on exactly what to
> plug in to Outlook to make it all work. As usual, the wizards at MS who
> wrote the SBS Wizards have made our lives a whole lot easier.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
>
> "Marc" <EMail@HideDomain.com> wrote in message
> news:EMail@HideDomain.com...
> > Hello,
> > following Setup:
> > -SBS 2003 (ISA Server 2004)
> > -XP Client SP2
> > -OWA is working fine
> > -Certificate is accepted by the server and client
> > -Secure Web Server was published in ISA vie SSL Bridging
> >
> > I am trying to get RPC-HTTP working. Used to work before ISA 2004 was
> > installed.
> > I followed the instructions from the Microsoft site, but still can't get
> > access to the server. Outlook can't connect to the exchange server.
> >
> > I tried https://FQDN/RPC and https://FQDN/rpcproxy.dll (access should be
> > denied), but the only message I get is 'principal name could not be
> > resolved'.
> >
> > I am really strugling with that problem, because I think there must be an
> > easy solution to this problem.
> >
> > Thank you for any hints!!!!
> > Marc
> >
> >
>
 
 
Charlie





PostPosted: Sun Jan 07 12:44:28 PST 2007 Top

SBS >> Outlook RPC over Http and ISA no. 443 only.

--
Charlie.
http://msmvps.com/xperts64


"Colin" <EMail@HideDomain.com> wrote in message
news:EMail@HideDomain.com...
> Hu guys,
>
> On this note, to get Outlook over http working successfully, does TCP port
> 80 need to be opened up ? As it's the most attacked, I really don't want
> to
> do this but so far, all I've found on configuring Outlook over http
> suggests
> that this step is necessary. Can it be done using https only ?
>
> Regards Colin.
>
> "Charlie Russel - MVP" wrote:
>
>> Stop obsessing about what's on the general MS site, and use the wizards.
>> ;)
>> The wizards are your friend. In this case, the CEICW - rerun it, making
>> sure
>> you specify Outlook over the Internet is allowed. Then connect to RWW and
>> click on the link on the right hand side for instructions on exactly what
>> to
>> plug in to Outlook to make it all work. As usual, the wizards at MS who
>> wrote the SBS Wizards have made our lives a whole lot easier.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>>
>> "Marc" <EMail@HideDomain.com> wrote in message
>> news:EMail@HideDomain.com...
>> > Hello,
>> > following Setup:
>> > -SBS 2003 (ISA Server 2004)
>> > -XP Client SP2
>> > -OWA is working fine
>> > -Certificate is accepted by the server and client
>> > -Secure Web Server was published in ISA vie SSL Bridging
>> >
>> > I am trying to get RPC-HTTP working. Used to work before ISA 2004 was
>> > installed.
>> > I followed the instructions from the Microsoft site, but still can't
>> > get
>> > access to the server. Outlook can't connect to the exchange server.
>> >
>> > I tried https://FQDN/RPC and https://FQDN/rpcproxy.dll (access should
>> > be
>> > denied), but the only message I get is 'principal name could not be
>> > resolved'.
>> >
>> > I am really strugling with that problem, because I think there must be
>> > an
>> > easy solution to this problem.
>> >
>> > Thank you for any hints!!!!
>> > Marc
>> >
>> >
>>