I have a new Windows 2003 Business Server. Everything seems to work, can get
to the web do updates, etc.
However none of the workstations can join the Domain, I have the DNS on the
work stations pointing to the new server. The workstations cannot ping the
server. However the Server CAN ping the work stations. What am I missing?

Hello Terry,

What OS are the workstations? Are firewalls on the workstations enabled?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> I have a new Windows 2003 Business Server. Everything seems to work,
> can get
> to the web do updates, etc.
> However none of the workstations can join the Domain, I have the DNS
> on the
> work stations pointing to the new server. The workstations cannot ping
> the
> server. However the Server CAN ping the work stations. What am I
> missing?

Firewall was on, but turned off same problem

"Meinolf Weber" wrote:

> Hello Terry,
>
> What OS are the workstations? Are firewalls on the workstations enabled?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > I have a new Windows 2003 Business Server. Everything seems to work,
> > can get
> > to the web do updates, etc.
> > However none of the workstations can join the Domain, I have the DNS
> > on the
> > work stations pointing to the new server. The workstations cannot ping
> > the
> > server. However the Server CAN ping the work stations. What am I
> > missing?
>
>
>

How are you pinging? by name? by address? Try setting the IP address and DNS
address manually and joining.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Terry" wrote:
> Firewall was on, but turned off same problem

On May 2, 11:00pm, "Dave Patrick" <DSPatr...@nospam.gmail.com> wrote:
> How are you pinging? by name? by address? Try setting the IP address and DNS
> address manually and joining.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]http://www.microsoft.com/protect
>
>
>
> "Terry" wrote:
> > Firewall was on, but turned off same problem- Hide quoted text -
>
> - Show quoted text -

Do you get an error message?

I'm pinging by IP. How do you mean set IP and DNS manually? I have the IP set
in TCP properties to it's IP same for DNS. One workstation the same the other
is Dymantic

"Dave Patrick" wrote:

> How are you pinging? by name? by address? Try setting the IP address and DNS
> address manually and joining.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Terry" wrote:
> > Firewall was on, but turned off same problem
>

The erro whtn trying to join the Domain is "cannot find path"

"Tmack" wrote:

> On May 2, 11:00 pm, "Dave Patrick" <DSPatr...@nospam.gmail.com> wrote:
> > How are you pinging? by name? by address? Try setting the IP address and DNS
> > address manually and joining.
> >
> > --
> >
> > Regards,
> >
> > Dave Patrick ....Please no email replies - reply in newsgroup.
> > Microsoft Certified Professional
> > Microsoft MVP [Windows]http://www.microsoft.com/protect
> >
> >
> >
> > "Terry" wrote:
> > > Firewall was on, but turned off same problem- Hide quoted text -
> >
> > - Show quoted text -
>
> Do you get an error message?
>

On the static machine can you ping the DNS server and DC by IP address?


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Terry" wrote:
> I'm pinging by IP. How do you mean set IP and DNS manually? I have the IP
> set
> in TCP properties to it's IP same for DNS. One workstation the same the
> other
> is Dymantic

NO

"Dave Patrick" wrote:

> On the static machine can you ping the DNS server and DC by IP address?
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Terry" wrote:
> > I'm pinging by IP. How do you mean set IP and DNS manually? I have the IP
> > set
> > in TCP properties to it's IP same for DNS. One workstation the same the
> > other
> > is Dymantic
>

Actually the DNS Server is being done by the router. We can ping the router
but not the DC

"Dave Patrick" wrote:

> On the static machine can you ping the DNS server and DC by IP address?
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Terry" wrote:
> > I'm pinging by IP. How do you mean set IP and DNS manually? I have the IP
> > set
> > in TCP properties to it's IP same for DNS. One workstation the same the
> > other
> > is Dymantic
>

You'll need to get by this problem before you can proceed. You have a
hardware and or hardware configuration problem.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Terry" wrote:
> Actually the DNS Server is being done by the router. We can ping the
> router
> but not the DC

Actually the DC should have the DNS role with forwarders to the ISP's DNS
server addresses. The DNS should point to itself for DNS using the actual
server's static address and not using 127.0.0.1



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

Correct, but I have other DCs that use the router as DNS and do not have this
problem. In this case the Router is controlled by the ISP and they will not
change it

"Dave Patrick" wrote:

> Actually the DC should have the DNS role with forwarders to the ISP's DNS
> server addresses. The DNS should point to itself for DNS using the actual
> server's static address and not using 127.0.0.1
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>

Terry <Terry@discussions.microsoft.com> wrote:
> I have a new Windows 2003 Business Server. Everything seems to work,
> can get to the web do updates, etc.
> However none of the workstations can join the Domain, I have the DNS
> on the work stations pointing to the new server. The workstations
> cannot ping the server. However the Server CAN ping the work
> stations. What am I missing?

1) It's best to post SBS questions in microsoft.public.windows.server.sbs -
SBS does many things its own way

2) DNS must be handled by your SBS box alone, not your router (the CEICW
will prompt you for your ISP's DNS servers)

3) DHCP should be handled by your SBS box, not your router

4) You need to use the setup wizards for *everything* in SBS- do not try to
join computers to the domain the non-SBS way or you will end up with
problems.

I'm setting up my reply to crosspost to the SBS group for your convenience
in this thread - but again, post all future SBS questions in there for the
best results, even if you also crosspost (not multipost!) to other groups.

OK but as I said the IPS owns the router, it was like pulling teeth to have
them point the first DNS IP to the server. THey will NOT allow us to remove
it form doing DNS

"Lanwench [MVP - Exchange]" wrote:

> Terry <Terry@discussions.microsoft.com> wrote:
> > I have a new Windows 2003 Business Server. Everything seems to work,
> > can get to the web do updates, etc.
> > However none of the workstations can join the Domain, I have the DNS
> > on the work stations pointing to the new server. The workstations
> > cannot ping the server. However the Server CAN ping the work
> > stations. What am I missing?
>
> 1) It's best to post SBS questions in microsoft.public.windows.server.sbs -
> SBS does many things its own way
>
> 2) DNS must be handled by your SBS box alone, not your router (the CEICW
> will prompt you for your ISP's DNS servers)
>
> 3) DHCP should be handled by your SBS box, not your router
>
> 4) You need to use the setup wizards for *everything* in SBS- do not try to
> join computers to the domain the non-SBS way or you will end up with
> problems.
>
> I'm setting up my reply to crosspost to the SBS group for your convenience
> in this thread - but again, post all future SBS questions in there for the
> best results, even if you also crosspost (not multipost!) to other groups.
>
>
>

Since part of this thread must be missing, it might be hard to understand
what is going on. I don't see any reference to "isp owns the router", but
if they demand that they and they alone control the router, you have either
got the wrong ISP, or you need another device between you and them.

Can you be a bit more specific about the information they gave you regarding
IP addresses, Sub Net Mask, Default Gateway, and DNS settings? And what you
have done with that information, as in where you typed it in.

The usual approach is to put all that info on the WAN facing side of the
router, and put your stuff, on the LAN side, then put your stuff and their
DNS settings into the CEICW, which will setup all the internal stuff
automagically. There should be no reason for the public WAN facing side to
even know your server exists.

Internet - Inet Device - Router - SBS Nic2 - SBS Nic1 - Switch -
Workstations.

If you have just a single nic

Internet - Inet Device - Router - Switch - SBS Nic
\
\ -
Workstations

--
Larry

Please post the resolution to
your issue so that all can benefit.


"Terry" <Terry@discussions.microsoft.com> wrote in message
news:1C2B8875-C64A-46CB-93B3-353402256041@microsoft.com...
> OK but as I said the IPS owns the router, it was like pulling teeth to
> have
> them point the first DNS IP to the server. THey will NOT allow us to
> remove
> it form doing DNS
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Terry <Terry@discussions.microsoft.com> wrote:
>> > I have a new Windows 2003 Business Server. Everything seems to work,
>> > can get to the web do updates, etc.
>> > However none of the workstations can join the Domain, I have the DNS
>> > on the work stations pointing to the new server. The workstations
>> > cannot ping the server. However the Server CAN ping the work
>> > stations. What am I missing?
>>
>> 1) It's best to post SBS questions in
>> microsoft.public.windows.server.sbs -
>> SBS does many things its own way
>>
>> 2) DNS must be handled by your SBS box alone, not your router (the CEICW
>> will prompt you for your ISP's DNS servers)
>>
>> 3) DHCP should be handled by your SBS box, not your router
>>
>> 4) You need to use the setup wizards for *everything* in SBS- do not try
>> to
>> join computers to the domain the non-SBS way or you will end up with
>> problems.
>>
>> I'm setting up my reply to crosspost to the SBS group for your
>> convenience
>> in this thread - but again, post all future SBS questions in there for
>> the
>> best results, even if you also crosspost (not multipost!) to other
>> groups.
>>
>>
>>

Terry <Terry@discussions.microsoft.com> wrote:
> OK but as I said the IPS owns the router, it was like pulling teeth
> to have them point the first DNS IP to the server. THey will NOT
> allow us to remove it form doing DNS

Have them undo what they did. You need your *own* router/firewall appliance
between your network & their equipment - something that does NAT. You
haven't mentioned whether you'r running ISA or not, but if you aren't, use a
single NIC in your server and plug it, and your clients, and *your*
firewall/router, into the same Ethernet switch.


>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Terry <Terry@discussions.microsoft.com> wrote:
>>> I have a new Windows 2003 Business Server. Everything seems to work,
>>> can get to the web do updates, etc.
>>> However none of the workstations can join the Domain, I have the DNS
>>> on the work stations pointing to the new server. The workstations
>>> cannot ping the server. However the Server CAN ping the work
>>> stations. What am I missing?
>>
>> 1) It's best to post SBS questions in
>> microsoft.public.windows.server.sbs - SBS does many things its own
>> way
>>
>> 2) DNS must be handled by your SBS box alone, not your router (the
>> CEICW will prompt you for your ISP's DNS servers)
>>
>> 3) DHCP should be handled by your SBS box, not your router
>>
>> 4) You need to use the setup wizards for *everything* in SBS- do not
>> try to join computers to the domain the non-SBS way or you will end
>> up with problems.
>>
>> I'm setting up my reply to crosspost to the SBS group for your
>> convenience in this thread - but again, post all future SBS
>> questions in there for the best results, even if you also crosspost
>> (not multipost!) to other groups.

Terry <Terry@discussions.microsoft.com> wrote:
> Correct, but I have other DCs that use the router as DNS and do not
> have this problem. In this case the Router is controlled by the ISP
> and they will not change it

Please see the other "leg" in this thread.
>
> "Dave Patrick" wrote:
>
>> Actually the DC should have the DNS role with forwarders to the
>> ISP's DNS server addresses. The DNS should point to itself for DNS
>> using the actual server's static address and not using 127.0.0.1
>>
>>
>>
>> --
>>
>> Regards,
>>
>> Dave Patrick ....Please no email replies - reply in newsgroup.
>> Microsoft Certified Professional
>> Microsoft MVP [Windows]
>> http://www.microsoft.com/protect

OK I will try.
This will take several days so I will start a new discussion if I still have
issues

Thank

"Lanwench [MVP - Exchange]" wrote:

> Terry <Terry@discussions.microsoft.com> wrote:
> > OK but as I said the IPS owns the router, it was like pulling teeth
> > to have them point the first DNS IP to the server. THey will NOT
> > allow us to remove it form doing DNS
>
> Have them undo what they did. You need your *own* router/firewall appliance
> between your network & their equipment - something that does NAT. You
> haven't mentioned whether you'r running ISA or not, but if you aren't, use a
> single NIC in your server and plug it, and your clients, and *your*
> firewall/router, into the same Ethernet switch.
>
>
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> Terry <Terry@discussions.microsoft.com> wrote:
> >>> I have a new Windows 2003 Business Server. Everything seems to work,
> >>> can get to the web do updates, etc.
> >>> However none of the workstations can join the Domain, I have the DNS
> >>> on the work stations pointing to the new server. The workstations
> >>> cannot ping the server. However the Server CAN ping the work
> >>> stations. What am I missing?
> >>
> >> 1) It's best to post SBS questions in
> >> microsoft.public.windows.server.sbs - SBS does many things its own
> >> way
> >>
> >> 2) DNS must be handled by your SBS box alone, not your router (the
> >> CEICW will prompt you for your ISP's DNS servers)
> >>
> >> 3) DHCP should be handled by your SBS box, not your router
> >>
> >> 4) You need to use the setup wizards for *everything* in SBS- do not
> >> try to join computers to the domain the non-SBS way or you will end
> >> up with problems.
> >>
> >> I'm setting up my reply to crosspost to the SBS group for your
> >> convenience in this thread - but again, post all future SBS
> >> questions in there for the best results, even if you also crosspost
> >> (not multipost!) to other groups.
>
>
>
>

Just to add, I disagree with SINGLE NIC..., Hi Lanwench... lol

Make your own decision whether you go single nic or 'as recommended by
microsoft / sbs ' dual nic.

Ciao


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in message
news:%23Oayo2frIHA.3900@TK2MSFTNGP05.phx.gbl...
> Terry <Terry@discussions.microsoft.com> wrote:
>> OK but as I said the IPS owns the router, it was like pulling teeth
>> to have them point the first DNS IP to the server. THey will NOT
>> allow us to remove it form doing DNS
>
> Have them undo what they did. You need your *own* router/firewall
> appliance between your network & their equipment - something that does
> NAT. You haven't mentioned whether you'r running ISA or not, but if you
> aren't, use a single NIC in your server and plug it, and your clients, and
> *your* firewall/router, into the same Ethernet switch.
>
>
>>
>> "Lanwench [MVP - Exchange]" wrote:
>>
>>> Terry <Terry@discussions.microsoft.com> wrote:
>>>> I have a new Windows 2003 Business Server. Everything seems to work,
>>>> can get to the web do updates, etc.
>>>> However none of the workstations can join the Domain, I have the DNS
>>>> on the work stations pointing to the new server. The workstations
>>>> cannot ping the server. However the Server CAN ping the work
>>>> stations. What am I missing?
>>>
>>> 1) It's best to post SBS questions in
>>> microsoft.public.windows.server.sbs - SBS does many things its own
>>> way
>>>
>>> 2) DNS must be handled by your SBS box alone, not your router (the
>>> CEICW will prompt you for your ISP's DNS servers)
>>>
>>> 3) DHCP should be handled by your SBS box, not your router
>>>
>>> 4) You need to use the setup wizards for *everything* in SBS- do not
>>> try to join computers to the domain the non-SBS way or you will end
>>> up with problems.
>>>
>>> I'm setting up my reply to crosspost to the SBS group for your
>>> convenience in this thread - but again, post all future SBS
>>> questions in there for the best results, even if you also crosspost
>>> (not multipost!) to other groups.
>
>
>

But understand that future versions of SBS may change what you have to do...

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Teneo" <not@here.com> wrote in message
news:ur5ldhgrIHA.3456@TK2MSFTNGP05.phx.gbl...
> Just to add, I disagree with SINGLE NIC..., Hi Lanwench... lol
>
> Make your own decision whether you go single nic or 'as recommended by
> microsoft / sbs ' dual nic.
>
> Ciao
>
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in
> message news:%23Oayo2frIHA.3900@TK2MSFTNGP05.phx.gbl...
>> Terry <Terry@discussions.microsoft.com> wrote:
>>> OK but as I said the IPS owns the router, it was like pulling teeth
>>> to have them point the first DNS IP to the server. THey will NOT
>>> allow us to remove it form doing DNS
>>
>> Have them undo what they did. You need your *own* router/firewall
>> appliance between your network & their equipment - something that does
>> NAT. You haven't mentioned whether you'r running ISA or not, but if you
>> aren't, use a single NIC in your server and plug it, and your clients,
>> and *your* firewall/router, into the same Ethernet switch.
>>
>>
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> Terry <Terry@discussions.microsoft.com> wrote:
>>>>> I have a new Windows 2003 Business Server. Everything seems to work,
>>>>> can get to the web do updates, etc.
>>>>> However none of the workstations can join the Domain, I have the DNS
>>>>> on the work stations pointing to the new server. The workstations
>>>>> cannot ping the server. However the Server CAN ping the work
>>>>> stations. What am I missing?
>>>>
>>>> 1) It's best to post SBS questions in
>>>> microsoft.public.windows.server.sbs - SBS does many things its own
>>>> way
>>>>
>>>> 2) DNS must be handled by your SBS box alone, not your router (the
>>>> CEICW will prompt you for your ISP's DNS servers)
>>>>
>>>> 3) DHCP should be handled by your SBS box, not your router
>>>>
>>>> 4) You need to use the setup wizards for *everything* in SBS- do not
>>>> try to join computers to the domain the non-SBS way or you will end
>>>> up with problems.
>>>>
>>>> I'm setting up my reply to crosspost to the SBS group for your
>>>> convenience in this thread - but again, post all future SBS
>>>> questions in there for the best results, even if you also crosspost
>>>> (not multipost!) to other groups.
>>
>>
>>
>
>

Teneo <not@here.com> wrote:
> Just to add, I disagree with SINGLE NIC..., Hi Lanwench... lol
>
> Make your own decision whether you go single nic or 'as recommended by
> microsoft / sbs ' dual nic.
>
> Ciao

Yes, of course, but I don't know that Microsoft officially recommends two
NICs (esp. if you've got a decent firewall, which you absolutely should in
any case).

Note that I work not only with SBS but with the enterprise products in
plenty of my clients' offices. Outside of SBS-land, two NICs in a domain
controller/DNS server is considered bad practice.


>
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in
> message news:%23Oayo2frIHA.3900@TK2MSFTNGP05.phx.gbl...
>> Terry <Terry@discussions.microsoft.com> wrote:
>>> OK but as I said the IPS owns the router, it was like pulling teeth
>>> to have them point the first DNS IP to the server. THey will NOT
>>> allow us to remove it form doing DNS
>>
>> Have them undo what they did. You need your *own* router/firewall
>> appliance between your network & their equipment - something that
>> does NAT. You haven't mentioned whether you'r running ISA or not,
>> but if you aren't, use a single NIC in your server and plug it, and
>> your clients, and *your* firewall/router, into the same Ethernet
>> switch.
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> Terry <Terry@discussions.microsoft.com> wrote:
>>>>> I have a new Windows 2003 Business Server. Everything seems to
>>>>> work, can get to the web do updates, etc.
>>>>> However none of the workstations can join the Domain, I have the
>>>>> DNS on the work stations pointing to the new server. The
>>>>> workstations cannot ping the server. However the Server CAN ping
>>>>> the work stations. What am I missing?
>>>>
>>>> 1) It's best to post SBS questions in
>>>> microsoft.public.windows.server.sbs - SBS does many things its own
>>>> way
>>>>
>>>> 2) DNS must be handled by your SBS box alone, not your router (the
>>>> CEICW will prompt you for your ISP's DNS servers)
>>>>
>>>> 3) DHCP should be handled by your SBS box, not your router
>>>>
>>>> 4) You need to use the setup wizards for *everything* in SBS- do
>>>> not try to join computers to the domain the non-SBS way or you
>>>> will end up with problems.
>>>>
>>>> I'm setting up my reply to crosspost to the SBS group for your
>>>> convenience in this thread - but again, post all future SBS
>>>> questions in there for the best results, even if you also crosspost
>>>> (not multipost!) to other groups.

As per microsoft 'recommended'
http://www.microsoft.com/Windowsserv...s/default.mspx

Also in the installation guides, but who reads them... :-)

I too support enterprise, Exchange is not recommended on a DC outside of SBS
land but we all know the SBS team have done a terrific job.

But as Charlie points out ... things are changing in 2008


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in message
news:Oe$V2ChrIHA.4788@TK2MSFTNGP03.phx.gbl...
> Teneo <not@here.com> wrote:
>> Just to add, I disagree with SINGLE NIC..., Hi Lanwench... lol
>>
>> Make your own decision whether you go single nic or 'as recommended by
>> microsoft / sbs ' dual nic.
>>
>> Ciao
>
> Yes, of course, but I don't know that Microsoft officially recommends two
> NICs (esp. if you've got a decent firewall, which you absolutely should in
> any case).
>
> Note that I work not only with SBS but with the enterprise products in
> plenty of my clients' offices. Outside of SBS-land, two NICs in a domain
> controller/DNS server is considered bad practice.
>
>
>>
>>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in
>> message news:%23Oayo2frIHA.3900@TK2MSFTNGP05.phx.gbl...
>>> Terry <Terry@discussions.microsoft.com> wrote:
>>>> OK but as I said the IPS owns the router, it was like pulling teeth
>>>> to have them point the first DNS IP to the server. THey will NOT
>>>> allow us to remove it form doing DNS
>>>
>>> Have them undo what they did. You need your *own* router/firewall
>>> appliance between your network & their equipment - something that
>>> does NAT. You haven't mentioned whether you'r running ISA or not,
>>> but if you aren't, use a single NIC in your server and plug it, and
>>> your clients, and *your* firewall/router, into the same Ethernet
>>> switch.
>>>>
>>>> "Lanwench [MVP - Exchange]" wrote:
>>>>
>>>>> Terry <Terry@discussions.microsoft.com> wrote:
>>>>>> I have a new Windows 2003 Business Server. Everything seems to
>>>>>> work, can get to the web do updates, etc.
>>>>>> However none of the workstations can join the Domain, I have the
>>>>>> DNS on the work stations pointing to the new server. The
>>>>>> workstations cannot ping the server. However the Server CAN ping
>>>>>> the work stations. What am I missing?
>>>>>
>>>>> 1) It's best to post SBS questions in
>>>>> microsoft.public.windows.server.sbs - SBS does many things its own
>>>>> way
>>>>>
>>>>> 2) DNS must be handled by your SBS box alone, not your router (the
>>>>> CEICW will prompt you for your ISP's DNS servers)
>>>>>
>>>>> 3) DHCP should be handled by your SBS box, not your router
>>>>>
>>>>> 4) You need to use the setup wizards for *everything* in SBS- do
>>>>> not try to join computers to the domain the non-SBS way or you
>>>>> will end up with problems.
>>>>>
>>>>> I'm setting up my reply to crosspost to the SBS group for your
>>>>> convenience in this thread - but again, post all future SBS
>>>>> questions in there for the best results, even if you also crosspost
>>>>> (not multipost!) to other groups.
>
>
>

Terry wrote:
> OK but as I said the IPS owns the router, it was like pulling teeth to have
> them point the first DNS IP to the server. THey will NOT allow us to remove
> it form doing DNS
>
That doesn't really matter, there can be any number of DNS servers in a
network. It's up to a client which server it uses. It's DHCP where only
a single server is practical, and if your SBS has two NICs then it
doesn't matter whether the router is a DHCP server or not, as the
workstations won't see it. Nor does the router need to use SBS as its
DNS server, but the SBS and all its domain member computers *must* do so.

That point cannot be overemphasised. The SBS and all its domain member
clients must shown *only* the SBS LAN IP address under DNS servers as
listed by an ipconfig command. The SBS DNS server provides
domain-specific information which no public DNS server can possibly have.

The SBS may use either a local router, the ISP's DNS servers (which the
router probably uses anyway), any other public DNS servers, or none at
all as its DNS *forwarders*, for lookups of public Internet IP
addresses, and these addresses are entered (or not) in the CEICW wizard.

Under normal conditions, the SBS runs both DHCP and DNS servers for its
workstations, which are all set to get IP address and DNS server
information automatically. No domain machine should ever need or get IP
or DNS server addresses set manually in TCP/IP properties. If any need
fixed addresses, find out their MAC addresses and set up DHCP
reservations for them.

"may change" ? :-)
http://sbs.seandaniel.com/2008/05/pr...for-small.html



Single nic is the only "supported" scenario for SBS 2008


--
Cris Hanna [SBS-MVP]
------------------------------------------
MVPs Do Not Work For Microsoft
-----------------------------------------------------
Please do not contact me directly. Please post only in the newsgroup so all can benefit


"Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org> wrote in message news:8F46A1CA-987D-4AEB-8FCD-586FB6D06B90@microsoft.com...
But understand that future versions of SBS may change what you have to do...

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Teneo" <not@here.com> wrote in message
news:ur5ldhgrIHA.3456@TK2MSFTNGP05.phx.gbl...
> Just to add, I disagree with SINGLE NIC..., Hi Lanwench... lol
>
> Make your own decision whether you go single nic or 'as recommended by
> microsoft / sbs ' dual nic.
>
> Ciao
>
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatya hoo.com> wrote in
> message news:%23Oayo2frIHA.3900@TK2MSFTNGP05.phx.gbl...