Re: .local vs .com

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

No problem. Let me know if i can help.
Jamie Nelson


"Dan Bronstein" <DanBronstein@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1304D745-1EB6-488D-AD9D-B809569FBC86@xxxxxxxxxxxxxxxx
Thanks for your efforts Jamie: I'm going to post on ISA's site and see if
there are any idea's there...Will let you know.

dab

"Jamie Nelson" wrote:

Would you like me to keep assisting you with this?
We have RPC over HTTP running at 15 of our client sites on SBS 2003 with
ISA
2004.
We have never had to add a publishing rule.
After running ICW, and filling in the exchange proxy details correctly,
it
just works (as long as the certificate is on the client computer).

On your servers RWW page, it also has the walk through for setting this
up
the SBS way.

Let me know if you want me to help you by verifying settings against our
servers or anything Dan.

Jamie

"Dan Bronstein" <DanBronstein@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C8DD55F5-7365-415E-87B5-6B80290986FC@xxxxxxxxxxxxxxxx
Thanks Jamie...Didn't work...I would think I need to make a change to
the
publishing rule that ISA created for the exchange server except I would
expect the wizard is already creating what MS feels it should...I've
found
the sbs wizards pretty good.

dab

"Jamie Nelson" wrote:

In the box that says:
Mutually authenticate the session when connecting with ssl
tick this box.
On the next line put:
msstd:<your fqdn>
eg
msstd:email.lsu.edu

Untick, on fast networks, and tick, on slow networks instead.

Also, make sure that the client computer has the current server
certificate
installed.

Give that a go,
Jamie


"Dan Bronstein" <DanBronstein@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:1B5DE424-0DE9-4031-8FDC-76723DC4C680@xxxxxxxxxxxxxxxx
Not using Proxy...Not suppose to need it when using ISA RPC. Did
try
it
w/proxy however and same issue...Tried all variations of setting as
shown
on
http://grok.lsu.edu/Article.aspx?articleId=94. Again, using ISA,
you're
not
suppose to need RPC over HTTP.

thanks

dab

"Jamie Nelson" wrote:

Well, it doesn't do that on our boxes.
What are all your settings on the exchange proxy page?

Jamie


"Dan Bronstein" <DanBronstein@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:0E2FDA53-F007-426F-A402-16C5B5C00268@xxxxxxxxxxxxxxxx
Thanks for response...

It works automatically UNTIL you actually connect to the mail
server.
Then
it changes the entry in the mail setup for the workstation from
.com
to
.local, and from then on, no connectivity.

dan

"Jamie Nelson" wrote:

Very easy indeed.
It works automatically.

On the outlook client, just use the external domain names
instead
of
the
..local.

as in:
msstd:server.domainname.com

Jamie Nelson
http://www.getithere.co.nz


"Dan Bronstein" <DanBronstein@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message
news:0FA7D114-97FF-4A00-88C3-B83F5259F08A@xxxxxxxxxxxxxxxx
topology: Windows 2003 SBS PREMIUM w/2 NICS, ISA 2004, all
current
spacks
Internal Name ABCompany.local
External Name ABCompany.com
Server Name ABServer

I like being able to use Outlook 2003 via RPC thru ISA (it's
wonderful!)
for
remote users. Up till now, I've had to put an entry into the
HOSTS
file
of
these remote computers so that when the mailbox name is
resolved
after
the
first connect (Mail settings changes the IP address to
ABServer.ABCompany.local), ABServer.ABCompany.local can be
resolved.

Recently moved an older client from sbs 2000 to sbs 2K3.
Their
Internal
name used .com and lo and behold, using a simple a record in
the
public
DNS,
I have these remote clients connected to exchange using
Outlook
via
RPC
via
ISA 2004 without the need for the hosts entry...

Any thoughts on how to accomplish this transparency when
.local
is
involved?
It would be nice to not have host file changes when IP address
change
(as
they do from time to time)

thanks

dab














.