Re: Server/Network setup question
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Sun, 9 Apr 2006 10:44:50 +1000
really, my first proposal sounds like the best way forward. To expand on it
a little:
1st, let's prepare the existing network for SBS. On the router, look at the
DHCP server properties, is the DHCP range adjustable? (it normally is)
We want to specify a range of addresses in the router DHCP which account for
our other items (SBS & Printer, got anthing else that changing the IP of
causes a headache?)
Diversion about 'rules'. I have some general rules I follow about IP
networks, and much of them comes from SBS space.
In SBS space you are unlikely to have more than ~100 devices needing IP
addresses.
By default SBS assumes the server is going to be in the low end of the range
(actually .2) and excludes a few addresses in this area.
Computers might be happier with binary math but despite my geekiness I'm a
decimal man.
I have really bad RAM, so the more consistent I make things the better off
we both are.
Routers are historically put at one or the other end of a range of
addresses.
I _love_ DHCP. Even where I wish to set a static address to something I do
it via DHCP.
SO
We leave .1-.10 alone
I tend to allow all PC's on the network to get IP's in the range .11-.100
I set (via DHCP reservation) PC's desiring static IP's (other than SBS) to
..101-.120
Non-PC devices requiring static IP's get .151- .200 (except routers, so my
printers go here and I normally assign their IP via DHCP reservation)
Routers go at .1, .254, or, IF I have several, addresses close to these.
Which means, if I was doing your job, I'd change that DHCP range on the
router to .11-.100, then either release/renew or simply resart all PC's.
If the router is at .1 (or .254, or really, anything but .2) I'd use .2 for
the SBS. (My SpeedTouch ADSL modem annoys me, it's default IP is .138. Who
chose this stupid number and just WHY? :-)
Do my obligatory 3 installs and it's time to do similar with the SBS DHCP
server.
If that problematic printer does not fit into this proposal we can adjust
the proposal without adjusting the printer.
"D. Milton" <D.Milton@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:042026D8-FA79-49EF-BE80-35AC8A5E3CC5@xxxxxxxxxxxxxxxx
or do it with external in .1.x and internal in .2.x, then 'Change ServerAh, this might answer my previous question. When I change the Server IP
IP
address' wiz at changeover time.
address, what will I change it to?
Thank you
--
D. Milton
This posting is provided "AS IS" with no warranties, and
confers no rights.
"SuperGumby [SBS MVP]" wrote:
or do it with external in .1.x and internal in .2.x, then 'Change Server
IP
address' wiz at changeover time.
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:OXJUt41WGHA.2356@xxxxxxxxxxxxxxxxxxxxxxx
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
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
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.
.
- References:
- Re: Server/Network setup question
- From: Merv Porter [SBS-MVP]
- Re: Server/Network setup question
- From: D. Milton
- Re: Server/Network setup question
- From: Merv Porter [SBS-MVP]
- Re: Server/Network setup question
- From: D. Milton
- Re: Server/Network setup question
- From: Merv Porter [SBS-MVP]
- Re: Server/Network setup question
- From: D. Milton
- Re: Server/Network setup question
- From: Merv Porter [SBS-MVP]
- Re: Server/Network setup question
- From: SuperGumby [SBS MVP]
- Re: Server/Network setup question
- From: D. Milton
- Re: Server/Network setup question
- Prev by Date: RWW Works on LAN - NOT on WAN!
- Next by Date: Re: RWW Works on LAN - NOT on WAN!
- Previous by thread: Re: Server/Network setup question
- Next by thread: Re: Server/Network setup question
- Index(es):
Relevant Pages
|
Loading
