Sorry, I was away all day. SBS is truly simple. We tend to overcomplicate
things. I suggest you get one of the books on the subject and keep it for
reference. When you see one of the several 300 page plus books on SBS you
will realize how much is packed into that box, and when you understand how
the wizards tie it all together you will appreciate how simple it is.
Yes, some things can break. It is a fairly complicated, integrated system
made simple by the carefully constructed wizards developed by the SBS Dev
Team at Microsoft. If you set up the SBS with, and use and follow the wizards,
it 'just works'. But there is a lot that has to come together, and hence
there are a lot of wizards. If a wiz exists you should use it.
The MX records are maintained by whoever controls your public DNS records.
Just ask them for help, or tell us who holds them and we can help you make
the changes yourself. What that record does is tell mail servers accross
the world where to send mail, so the MX record points to the A record which
points to the external, public facing, WAN side ip address of your edge device.
The edge device, unless it is the SBS itself (bad) then "port fowards" point
25 to the listening nic on the SBS. if you have just one nic, use that,
if you have two nics, use the other one. <g> The other one is the nic
that is in the same subnet as the LAN side of the router and has a patch
cord from it to the router.
As for the Connect to the Internet wiz, you can run that as many times as
you wish. One of the tests of a functioning SBS is the ability to sucessfuly
complete that wizard. So once the MX records are done, you run the wizard
which populates all the settings for email, RWW, and so on.
After you are done, you should see no reference to any DNS settings on any
NIC in the LAN except the internal, private LAN nic in the SBS. The wizard
takes care of setting up the DNS forwarders to enable your clients to find
web sites outside the SBS network.
Another way to find if your SBS is running smoothly is to run the SBS BPA
and fix anything it finds.
I would do that first.
Please post the resolution to your
issue so others may benefit
Get Your SBS Health Check at
> No Comcast does not, Network Solutions does. My FQDN is
> "SteveB" wrote:
>> Does your ISP also provide your DNS hosting? That's not always the
>> case. What is the FQDN? There should be an A record with the current
>> static IP (you don't need to use another one) pointed to the FQDN of
>> the server. Then an MX record with the appropriate priority is setup
>> for that FQDN.
>> "Scott C." <ScottC@newsgroup> wrote in message
>>> I have another question about MX records. I need to give my ISP
>>> FQDN and the IP address of the mail server. I believe my IP for the
>>> server is the same static IP I used on the server, correct? They
>>> gave us
>>> static IP's but I only used 1 of them. Should I use a different one
>>> mail server? If so, where do I make this change?
>>> "Larry Struckmeyer[SBS-MVP]" wrote:
>>>> Sorry for the error. There should be no setup required for
>>>> Exchange on
>>>> 2003, other than to run the wizards and get your ISP to set your MX
>>>> So to establish a base line for helping you can you give us a
>>>> Did you install this SBS yourself or was it done by an IT Pro
>>>> SBS 2003. An enterprise geek may not be familiar with SBS, so you
>>>> Have all the steps been performed by using the wizards? Add users
>>>> for example. Have you run the Connect to the Internet Wizard found
>>>> "To do" page of Server Managment? Does it complete or error out.
>>>> at what phase?
>>>> What other errors that might be relevant in the event logs?
>>>> Please download and fix any erros found by the SBS BPA.
>>>> Please post the resolution to your
>>>> issue so others may benefit
>>>> Get Your SBS Health Check at
>>>>> I am new to Exchange and trying to set it up. All the Exchange
>>>>> services are
>>>>> running except: Exchange Routing Engine service terminated with
>>>>> error. Error 3. The system cannot find the path specified.
>>>>> I can receive emails but no one can send. The emails aren't
>>>>> in the
>>>>> sent folder on the client computers but when I check say hotmail,
>>>>> there is no
>>>>> Is this because of the above error?
>>>>> If so, how do I fix this?
>>>>> When I google this error, Microsoft suggests I reinstall the
>>>>> this what needs to be done?