Re: Server/Network setup question

Maybe we can make this easier to follow. Let's keep the P2P network and the
rented printer in the 192.168.1.x subnet. Nothing changes for the present
P2P network.

So, you buy a cheap switch and a WAP, power up the switch and connect the
SBS server's internal NIC to the switch. Then you complete the SBS install.
The internal NIC of the SBS server will default to 192.168.16.2 during the
install. After that, you manually assign the SBS external NIC a static IP
of 192.168.1.2 (like in the diagram I mentioned), connect it to a port on
the router and run CEICW to configure your SBS network. At that point you
can set up computer accounts, user accounts, configure domain name, email,
etc. on the SBS. You can even set up the WAP and attach it to the switch.
Your P2P workstations/printers still don't know anything about a "domain
server".

CEICW Walkthrough (Andy Goodman)
http://www.12c4pc.com/sbs2k3/sbs2k3-n2.htm

When you're ready to bring the P2P workstations and printers into the
domain, you change the IP of the rented printer to 192.168.16.8 (or some
other IP from .3 to .9). Then, one by one, you connect each
workstation/printer to the new switch and you start adding your workstations
and user profiles to the domain using ConnectComputer.

The end result is an SBS network like:

Internet
|
Broadband Modem
|
Router WAN side (ISP Static or Dynamically assigned Public IP Address)
Router LAN side (192.168.1.1)
|
External NIC (192.168.1.2)
SBS
Internal NIC (192.168.16.2)
|
Switch
| | | | | | | | |
Workstations, WAP, rented printer (all 192.168.16.x)


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

"D. Milton" <D.Milton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1D703546-9C23-4F3A-941A-2B3CE4CEE4F7@xxxxxxxxxxxxxxxx
Yes, currently the users are getting IP addresses from DHCP on the router.

Since you have two 2 NICs in your SBS server, under other circumstances,
you
could connect the external NIC to a port on your router and not disturb
your
P2P users.

Ok, I'm convinced that I should deal with the rented printer seperately.

If you can overcome this rented printer problem, I'd change the LAN IP
range
of the router now.
Change it to 192.168.16.x or to a subset of the current range or to
something else?

Then all your workstations would just need to reboot to
get an IP in this new range. After that, you give the external NIC on
your
SBS server a static IP address in the same range as the router.
The router is currently 192.168.1.0. So, 192.168.1.2, for example?

Then set up
your SBS server, making sure to connect the internal NIC to a live
(turned
on) hub or switch during the install procedure.
That would be the existing hub, yes?

Since your P2P users will
be in a subnet that is different from the SBS LAN (with their own
Internet
and P2P network connectivity), you should be able to do considerable
(almost
all) setup of the SBS server without affecting them.
Can you elaborate on what subnet I should add my P2P user to?

Wow - great information.

Am I taking an unusual approach?

--
D. Milton

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



"Merv Porter [SBS-MVP]" wrote:

Basically, what you want to do is isolate your current Peer-to-Peer (P2P)
users. Currently, I suspect your users are getting IP addresses
automatically from the DHCP service on the router.

Since you have two 2 NICs in your SBS server, under other circumstances,
you
could connect the external NIC to a port on your router and not disturb
your
P2P users. However, your requirement that you maintain the 192.168.1.x
IP
range for your SBS LAN complicates things a bit. You could change the IP
scheme used by the router but then that "rented" printer is going to need
to
have it's IP address changed (which you should be able to do yourself
with a
call to their tech support department).

If you can overcome this rented printer problem, I'd change the LAN IP
range
of the router now. Then all your workstations would just need to reboot
to
get an IP in this new range. After that, you give the external NIC on
your
SBS server a static IP address in the same range as the router. Then set
up
your SBS server, making sure to connect the internal NIC to a live
(turned
on) hub or switch during the install procedure. Since your P2P users
will
be in a subnet that is different from the SBS LAN (with their own
Internet
and P2P network connectivity), you should be able to do considerable
(almost
all) setup of the SBS server without affecting them.

I suppose another approach would be to leave everything as it is now in
the
P2P network, connect the SBS server using the 192.168.1.x range for the
external NIC, set up the SBS with an IP range of 192.168.16.2, then later
have the IP of the rented printer changed to an IP address in the
192.168.16.x range, then join your workstations to the domain.

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

"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: DHCP Fails on Authorized Server
    ... The DHCP shutdowns may because the SBS detects another DHCP in network. ... How to configure Internet access in Windows Small Business Server 2003 ... On the Connection Type page, click Broadband, and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with Permissions
    ... And SBS server is only take ... the role of an internal server. ... they are all configured to connected to internal network. ... g. Run the Configure Email and Internet Connection Wizard on SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server & a WiFi Hotspot (some DHCP for good measure too)
    ... ISA2k4 is currently not supported on SBS ... To review - you have LAN clients that you want to have ... card for your server. ... > network with 5 client computers. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... This newsgroup only focuses on SBS technical issues. ... | Subject: RE: VPN Connection Problems ... you can not ping anything on the SBS network from WAN. ... |> FQDN of the SBS server on the Web Server Certificate page. ...
    (microsoft.public.windows.server.sbs)
  • RE: Cannot access companyweb
    ... to migrate from SBS 2003 to SBS2003, in this period, you can't achieve this ... 825763 How to configure Internet access in Windows Small Business Server ... By this method, you need to manually restore Exchange data, SharePoint ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)