Re: Server/Network setup question

Many of us don't like OEM preinstalls and it is fairly common for us to
flatten such and start again anyway. You might, as this is your fist go,
complete the OEM '15 minute' install procedure and take a look around the
box, see what you have and what you may wish to change.

Don't get me wrong, it ain't that anything bad happens during a standard
install, it is simply that lack of familiarity with SBS may lead to some bad
choices being taken during the procedure. It's human error, not the system.
By performing a full installation yourself, looking at what you may wish to
change, looking at the result of your choices, and then doing the whole
thing again, the system will be more optimally configured.

You _can_ take a system with a bare drive, or the OEM preinstall, and do
nothing but 'follow the bouncing ball'. The result will be a fully
functional SBS, _EVERY_ time. The SBS dev team _are_ that good. However,
this can be improved on. (HMMM, actually, I should take the OEM pre-install
out of that, it can have some gotchas, unless the OEM has addressed some
known issues)

Yes, you can disable the external NIC (but first have it live and connected
to something during install) and not install ISA until you are ready to
commit.

Yes, IP details will be:
IP Address/mask, same subnet as router.
DG, router.
DNS, SBS IP.

When you run the CEICW (don't worry, you'll find out what it is when you
complete the 'to-do list') you can supply either the router or your ISP's
DNS servers as forwarders.

REMEMBER: An SBS installation is complete _ONLY_ after all items in the
'to-do list' have been completed. Though I encourage you to look at and
modify choices during the installation procedure you want to do the absolute
minimum outside the SBS wizards until SBS installation is complete.


"D. Milton" <D.Milton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6A85F493-0E83-4921-AB75-EE653DBC6C9C@xxxxxxxxxxxxxxxx
Yes, my eventual aim is to have a two NIC SBS behind my
simple NAT router. Yes, ISA will eventually be used, as it is SBS
Premium.

I like the idea of getting the server into the subnet so that I can become
familiar with it. You mentioned that sometimes it is necessary to run
setup
multiple times. How long does it take, and how what types of things
generally go wrong? My server is coming with SBS pre-installed.

The second nic will already be installed in the box. Can I configure SBS
to
just ignore it until I am ready for the next phase?

The manual IP details will be the address range and static IP address for
the server, and the router address, yes? Anything else?

Thanks!
--
D. Milton

This posting is provided "AS IS" with no warranties, and
confers no rights.



"SuperGumby [SBS MVP]" wrote:

You can, to a degree, 'phase in' this box.

Your eventual aim, I believe, is to implement a two NIC SBS behind your
simple NAT router, this is good. Q: Will ISA eventually be used? (is it
SBS
Premium?)

Leave your router and workstations 'as is', including enabled DHCP on the
router, which I guess you are currently using. Install SBS with a single
NIC
but give it manual IP details rather than DHCP from the router. As you
progress through the installation you will get to a point where SBS
advises
'turn off DHCP on your router', do so at this time.

This will put the server into your current subnet and give you time to
familiarise yourself with her. Possibly even run the installation a 2nd,
and
maybe third time (many of us suggest you get it right third try :-). The
only SBS facilities that the workstations will use will be at the point
where you disable the router's DHCP, they will then start to get DHCP and
DNS from the SBS.

You might, once you have the server config down pat, grab a spare PC (or
Virtual PC/Virtual Server) and create a test user, play with joining the
domain, poke around a bit, more familiarisation.

When you are ready to commit to SBS you put your router into the seperate
subnet, shut everyone down, throw the 2nd NIC into SBS and attach it to
the
router, fire up, run the CEICW, and start joining workstations to the
domain.

"D. Milton" <D.Milton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:719A65A1-8F68-42F7-96C2-158B178CFC4F@xxxxxxxxxxxxxxxx
Merv,

When you say "You can set up quite a bit of the server
(setting up email, user accounts, computer accounts) before you
actually
connect the workstations the domain."

Are you saying that this can be done before the server is inserted into
the
existing network?

Will the users have internet and LAN connectivity even before they are
joined to the domain if the server has been added the the network?

Thanks
--
D. Milton

This posting is provided "AS IS" with no warranties, and
confers no rights.



"Merv Porter [SBS-MVP]" wrote:

IMO, "phasing in" a single (integrated) server like SBS rarely works
well.
Most companies who use SBS have a small number of users and
workstations/laptops. I've found it better to do your homework, pick
a
weekend, set up the network infrastructure, join all the
workstations/laptops to the domain and move existing Peer-to-Peer
profiles
to "domain" profiles uisng ConnectComputer. It's a whole lot cleaner
that
set up the network piecemeal. You can set up quite a bit of the
server
(setting up email, user accounts, computer accounts) before you
actually
connect the workstations the domain.

A big challenge has always been shifting your users' profiles from a
"workgroup" to a "domain" (which is where the ConnectComputer utility
in
SBS
2003 comes in handy). If you can get them to put all their data files
in
their My Documents folder prior to joining them to the domain, you
should
consider redirecting their My Documents folder to their user folder on
the
server so that all user data can be centrally located on the server
for
daily backup. Folder redirection (with or without offline file
synchonization) goes a long way to making this as transparent as
possible
for the end user.

The current POP3 accounts can be switched over to using the POP3
Connector
for downloading and delivering these to each Exchange mailbox. In
time,
you
may even want to move up to hosting your own Exchange server (all mail
delivered directly to your SBS server).

Just my $.02.

--
Merv Porter [SBS MVP]
===================================
"D. Milton" <D.Milton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:47641CEC-8794-4595-A66C-E588EC5954A2@xxxxxxxxxxxxxxxx
Thanks Merv and SuperGumby.

I guess my goal was to try to minimize the amount of time spent
getting
the
server in place as well as the impact to existing users and devices
on
the
network. I had hoped to be able to just add the server, get it
configured
correctly, and then have everything keep working. Guess I had
better
schedule some maintenance time.

The laptops on my network go wireless.

I wanted to phase in the server -- first just get connectivity and
routing
going, then add a switch, then migrate email from Pop3 to Exchange,
then
focus on SQL and client/server apps.

I think that approach will still work, but I may have the laptops
use
an
eternet connection until I am sure that phase I is solid, then add a
wap.
I
prefer to minimize the number of changes that I make at one time.

Thanks again for your help.
--
D. Milton

This posting is provided "AS IS" with no warranties, and
confers no rights.



"Merv Porter [SBS-MVP]" wrote:

Your internal SBS LAN IP range can be any private IP scheme you
like
(172.x.x.x, 10.x.x.x, 192.x.x.x). 192.168.16.x is just the SBS
2003
default. The LAN side of your router is probably set up as
192.168.1.x
now
and will need to be changed to another subnet (like 192.168.2.x) if
you're
going to use the 192.168.1.x scheme for your internal SBS LAN.

Correct about the WAP since, once you get your SBS network set up,
the
wireless router will be outside your LAN.

--
Merv Porter [SBS MVP]
===================================

"D. Milton" <D.Milton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:069E086A-68E0-4E7B-85F7-845855524E55@xxxxxxxxxxxxxxxx
Great diagram. Thanks.

Two questions: The internal LAN address range, according to the
diagram,
should be 192,168.1.x. The external address should be
192.168.1.10
or
any
address within the same subnet as the router. Currently, I have
several
devices, namely a rented printer installed and configured by the
printer
company to use address 192.168.1.20. Once I add my server and
assign
the
addresses according to the diagram, this printer will cease to
work
and
I
will need to call the not-very-responsive printer company back in
to
reconfigure the printer. Since my company is actively doing
business,
I
would prefer to avoid this if at all possible. I have have a
wireless
print
server with a static address also in the 192.168.1.x range. My
question
is
this: must the internal addresses be 192.168.16.x or can they
remain
as
the
are (192.168.1.x) and the external address could be something
else?

Also: my wireless connectivity will cease to work when I add the
server
between the modem/wireless router, hence the suggestion for a
wap,
yes?

Thanks!
--
D. Milton

This posting is provided "AS IS" with no warranties, and
confers no rights.



"Merv Porter [SBS-MVP]" wrote:

Take a look at the diagram at: (works for SBS 2003 with or
without
ISA)

Two Nics, a dynamic IP address, ISA and a router
http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&articleId=74

For wireless for the LAN workstations, I would buy a Wireless
Access
Point
(WAP) and connect it to the "hub" (which really should be a
"switch")
on
the
LAN side of that diagram.

--
Merv Porter [SBS MVP]
===================================
"D. Milton" <D.Milton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:0C092EE3-14EF-4757-AFD2-DBA1154988AE@xxxxxxxxxxxxxxxx
I have a windows 2003 SBS w/ 2 net cards. My internet
connection
is
via
a
DSL wireless modem/router combined. Currently, the one
ethernet
port
on
modem/router runs into a hub which provides connectivity for
the
clients
on
the LAN. Wireless also works.

Given my current configuration, what is the best place to
interject
the
server?

Thanks
--
D. Milton

This posting is provided "AS IS" with no warranties, and
confers no rights.















.

Relevant Pages

  • Re: Server/Network setup question
    ... currently the users are getting IP addresses from DHCP on the router. ... SBS server a static IP address in the same range as the router. ... be in a subnet that is different from the SBS LAN (with their own Internet ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... DNS on your server is broken. ... Les Connor [SBS Community Member - SBS MVP] ... and put in the ip of the router. ... The local router has the broadband connection ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I reinstall setup.exe file for clients in server?
    ... Deployment on SBS to rebuild client setup application. ... We need to select "Windows Small Business Server 2003" but not ... | installation was made late September. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... seleting full time broadband connection. ... Les Connor [SBS Community Member - SBS MVP] ... check the router as well and unless I missed a firewall setting on it, ... Anyway the Server Ipconfig /all is this... ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... I checked the router, I am running a laptop off of it so I can post. ... Les Connor [SBS Community Member - SBS MVP] ... make sure the DHCP Client Service is running on the server. ... First Page of the Internet Connection Wizard, ...
    (microsoft.public.windows.server.sbs)