Re: Private Domain Name #1 (.local) vs Public Domain Name #2 (.com)
- From: "Steve" <newsgroup@xxxxxxxxxx>
- Date: Wed, 7 Feb 2007 09:22:24 -0800
No headache, domain rename, or reinstall needed. Is Exchange actually
installed but just not being used? If not installed of course you have to do
that properly from the integrated setup under add/remove programs/Windows
Small Business Server 2003. I'd also advise installing Exchange SP2. After
that run the CEICW putting in the proper companyname.com when asked. That
will take care of not showing the .local as the outgoing name. Then make
sure your public DNS hosting service has an A record and a primary MX record
(something like mail.companyname.com) that points to your external IP
address. A secondary MX record pointing to another mail host (probably your
current ISP) will cover you if your SBS is down for a period of time. BTW
don't confuse a web site (www.companyname.com) with your registered domain
name (companyname.com) as its your domain name that's important here for
your mail.
"Oswego" <Oswego@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9E979129-DCCD-4E7B-A79E-B2D980FCD5B4@xxxxxxxxxxxxxxxx
Greetings,
I have an intersting issue that I've inherited from my company's original
SBS 2003 setup & configuration and would love some outside input for
possible
solutions.
SBS 2003 Sp1 was originally setup without Exchnage services active as the
company had chosen to continue using pop email services along with their
public web-hosting package via a local ISP (poor planning for the future
I'd
say!)..
My company now wants to start using Exchange for email and collaboration
and
now I have the following issue:
The SBS server is configured with an internal domain name
(sbs.ServerName.local) and and the public domain name that the ISP is
hosting
is actually the one I need to use (www.ComapnyName.com).
I understand that SBS 2003 does not support Domain Rename using
Rendom.exe,
so my only options at this point is to reinstall SBS 2003 and configure
the
new domain structure to match the public .com domain (argh!) - or try to
forward email traffic from the the www.CompanyName.com domain to Exchange
and
then have outbound smtp traffic appear as if it is coming from
www.CompanyName.com and not the sbs.ServerName.local domain.
This is where I get a headache... any ideas to get me pointed in the right
direction would be most helpful - Cheers!
.
- Follow-Ups:
- Prev by Date: Re: Password Problem - Server
- Next by Date: Re: Password Problem - Server
- Previous by thread: Re: Private Domain Name #1 (.local) vs Public Domain Name #2 (.com
- Next by thread: Re: Private Domain Name #1 (.local) vs Public Domain Name #2 (.com)
- Index(es):
Relevant Pages
|
