Re: rpc for http
- From: "Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@xxxxxxx>
- Date: Sun, 30 Jul 2006 09:36:02 -0400
Leythos,
I have never had to create a "new" cert in order to make Outlook over HTTP
work. I've always just folowed the custom guidelines generated by SBS. But,
those customized guidelines assume that the self cert you created is
correct. If you've changed the way you access the server from the public
side, you need to redo your self cert, and then the instructions for setting
up Outlook over RPC would be correct.
Sure, it's frustrating for you ... and you can say, well NOW I know that
it's required. But, that's the reason for these NG's - to help each other
out. Hopefully, down the road, some one else will get stuck with
implementing Outlook over RPC and you'll be the one to help them!!!
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"Leythos" <void@xxxxxxxxxxx> wrote in message
news:jv0zg.38871$vl5.6730@xxxxxxxxxxxxxxxxxxxxxxxxx
In article <#IgKPO5sGHA.4992@xxxxxxxxxxxxxxxxxxxx>, sbradcpa@xxxxxxxxxxx
says...
By definition with RWW/Outlook over HTTP you have to resolve using
public DNS to that box.. given that we never open up port 53 on our
boxes, we have to have something 'public'.
It can also be the public IP address of the server ... but it's got to
be something that can be resolved from the outside.
Yes, I now that, I was using mail.ourcompany.com that was our public
DNS, but the configuration page in /remote showed the INTERNAL DNS names
for the server. So, when I setup Outlook 2003 using that info it only
worked inside the company, then I tried, without luck, to determine what
server names (public/private) needed to be entered in what places in the
outlook https settings...
Again, until I stumbled on the idea of setting up a NEW certificate with
our public name, instead of the local name, the instructions were wrong
on the /remote page that tells users how to connect Outlook 2003.
After using the cert wizard, giving it our public name for the NEW cert,
the instructions were perfect and the connections (once changed) worked
the first time.
The thing to take away here is that the SBS team needs to find a clear
means to inform users that they need to create a new cert with a public
name that points to the server in order for the /remote page to properly
tell users how to connect Outlook 2003 remotely.
--
spam999free@xxxxxxxxxx
remove 999 in order to email me
.
- References:
- Re: rpc for http
- From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- Re: rpc for http
- From: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
- Re: rpc for http
- Prev by Date: Re: SBS 2003 Backup settings changes
- Next by Date: Re: Setup Public Sharepoint Site with OWA & RWW
- Previous by thread: Re: rpc for http
- Next by thread: Re: rpc for http
- Index(es):
Relevant Pages
|
