Re: Server/Network setup question

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: Wireless Network Issue - SBS2K3 - Configuration and / or Topol
    ... I am quietly confident that moving the SBS to ... and the SBS is the DHCP/DNS server - but everything else in my house is ... wireless and it works fine. ... cause is incorrect network configuration and / or hardware topology. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connect a Wireless Router to my SBS Network
    ... what are you using for the IP address of the external NIC in your SBS ... ipconfig /all for the SBS server may be a good idea. ... wireless resolves DNS requests? ... plugged into the WAN port of the Airlink router (not one of the 4 ...
    (microsoft.public.windows.server.sbs)
  • Re: Server/Network setup question
    ... any two ranges can be used on the SBS internal and external sides. ... The internal LAN address range, according to the diagram, ... server with a static address also in the 192.168.1.x range. ... my wireless connectivity will cease to work when I add the server ...
    (microsoft.public.windows.server.sbs)
  • Re: vpn access from hotel room
    ... If you have a dedicated workstation on the LAN (or just access to any LAN ... users to keep all their data on the server so it's ... A VPN requires significantly more bandwidth ... If you're laptop has been joined to the SBS domain, ...
    (microsoft.public.windows.server.sbs)
  • Re: RDP through RWW
    ... I also check logs and found the SBS ... RDP Server Access Rule is correctly created. ... <192.168.30.10 - RAS VPN ... <192.168.30.11 - LAN ...
    (microsoft.public.windows.server.sbs)
Loading