Re: exchange set up

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



all members of an Active Directory should only look to DNS servers which
contain information about the AD. This applies to the DC's themselves as
much as it applies to client computers.

AD DC's normally run DNS as an AD integrated zone so the 'norm' is for all
members to use _only_ AD DC's for DNS. The DNS server(s) on the DC(s) will
then satisfy queries outside the AD by the use of either 'forwarders' or
'root hints'. It is quite feasible to use other DNS servers but such servers
need to be aware of all objects in the AD DNS space, your ISP's DNS servers
hopefully know NOTHING about your AD and therefore should not be used in the
NIC properties.

In a single server SBS environment it is quite straightforward, all members,
including the SBS itself, should look to the SBS's internal network address
for DNS. The CEICW configures the DNS server on SBS to use either root hints
or 'forwarders' if you supply them.

"duke" <duke@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:29117044-B54B-47CB-9127-1900EE70071D@xxxxxxxxxxxxxxxx
I'm still learning as I go. Would you mind explaining a little further
what
you reccomend i do?

"Cris Hanna (SBS-MVP)" wrote:

Assuming you only have one nic
The only dns address that should be listed is the IP address of you nic
10.0.1.6

Then when you run the CEICW again...it will ask you for the IP Addresses
of your ISPs DNS server and you'll put in the addresses you got on the
NIC DNS now

--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so
all can take advantage
"duke" <duke@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:04C43CD5-4F60-4505-BE22-89898D7369A4@xxxxxxxxxxxxxxxx
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ping 66.180.96.12

Pinging 66.180.96.12 with 32 bytes of data:

Reply from 66.180.96.12: bytes=32 time=10ms TTL=250
Reply from 66.180.96.12: bytes=32 time=11ms TTL=250
Reply from 66.180.96.12: bytes=32 time=11ms TTL=250
Reply from 66.180.96.12: bytes=32 time=10ms TTL=250

Ping statistics for 66.180.96.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

C:\Documents and Settings\Administrator>ping mail.kapproservices.com

Pinging mail.kapproservices.com [72.54.56.205] with 32 bytes of data:

Reply from 72.54.56.205: bytes=32 time<1ms TTL=255
Reply from 72.54.56.205: bytes=32 time<1ms TTL=255
Reply from 72.54.56.205: bytes=32 time<1ms TTL=255
Reply from 72.54.56.205: bytes=32 time<1ms TTL=255

Ping statistics for 72.54.56.205:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : kapserver2006
Primary Dns Suffix . . . . . . . : KAPPROServices.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : KAPPROServices.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-13-72-3D-83-EE
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.1.6
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.0.1.1
DNS Servers . . . . . . . . . . . : 10.0.1.6
66.180.96.12
64.238.96.12
Primary WINS Server . . . . . . . : 10.0.1.6

C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>

"Cris Hanna (SBS-MVP)" wrote:

> please run ipconfig /all on the server and post the entire results
here.
>
> --
> Cris Hanna [SBS-MVP]
> --------------------------------------
> Please do not respond directly to me, but only post in the newsgroup
so all can take advantage
> "duke" <duke@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B41E5A23-D4D1-421C-B3B9-A9C986B5C399@xxxxxxxxxxxxxxxx
> I have the DNS set up to run direct
>
> "Cris Hanna (SBS-MVP)" wrote:
>
> > re-run the CEICW Wizard and try telling it to send mail directly
using DNS
> >
> > --
> > Cris Hanna [SBS-MVP]
> > --------------------------------------
> > Please do not respond directly to me, but only post in the
newsgroup so all can take advantage
> > "duke" <duke@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0905E528-83BB-4686-89B1-9B9E925A8A36@xxxxxxxxxxxxxxxx
> > Hi, I have sbs 2003 with exchange 2003 sp2. Yesterday I did
the switchover
> > to exchange... we had been using our ISP before. OWA and
internal works but
> > we have problems:
> >
> > We can recieve but not send. Looking at the exchange queue all
messages to
> > external recipients are queued but not sent. Messages from one
internal user
> > to another internal user are sent and recieved normally
> >
> > Please help! The boss comes back on monday!


.



Relevant Pages

  • Re: sys vol check
    ... instead of the local DNS server and two ISP DNS servers. ... I need to configure the DHCP to use all three internal DNS servers ... If DNS zones are AD Integrated are writtable. ...
    (microsoft.public.windows.server.active_directory)
  • Re: sys vol check
    ... You've 3 DC DNS servers one in each Site with different subnets. ... You've A forward lookup Zone named CORP.DLECINC.COM and a reverse lookup ... The clients should use only their local DNSserver in ther NIC ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2k3 and Slow Logons
    ... > various DNS settings from the server and my router set up. ... for internal DNS servers, but it must NOT be listed on any ... >>>>bad world of the Internet. ...
    (microsoft.public.windows.server.dns)
  • Re: Prevent Caching of real world domain in W2K3 sp1 DNS.
    ... resolve anything usda.gov on either of my main DNS servers. ... and the cache is quite full. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS + Forwarders
    ... forward from a site that doesn't have it's own internet service to a DNS ... As to forwarders I agree again. ... The two DCs in head office are the main DNS servers. ...
    (microsoft.public.win2000.dns)