Networking Help

Hi,

I need a some ideas on how to reconfigure my network at work. I"m new with
the company and the boss has handed the responsibility to me.
Here's the current network configuration:
Business Class DSL ----> HP LVX2000 Server ---> Switch ----> 5 Windows XP
Pro Clients.
On the server it's running SBS 2K with AD, Exchange 2000, Termincal
Services, Quicken

My boss has just bought two new servers: Both are same hardware
configuration, one is running Server 2003 and the other SBS 2003.
Server 2003 would be the domain controller and file server and the SBS would
be used for Exchange solely. I would then use the HP LVX2000 as a web
server.
Is this a good idea? Should I put in a router?

SBS just support one DC by design. So you have two options. One keeps the same SBS DC, use other server as web server and exchange server. Or install another DC to replace the SBS DC.

It is better to have a router instead of using the SBS as the router.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Du Lam" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
Hi,

I need a some ideas on how to reconfigure my network at work. I"m new with
the company and the boss has handed the responsibility to me.
Here's the current network configuration:
Business Class DSL ----> HP LVX2000 Server ---> Switch ----> 5 Windows XP
Pro Clients.
On the server it's running SBS 2K with AD, Exchange 2000, Termincal
Services, Quicken

My boss has just bought two new servers: Both are same hardware
configuration, one is running Server 2003 and the other SBS 2003.
Server 2003 would be the domain controller and file server and the SBS would
be used for Exchange solely. I would then use the HP LVX2000 as a web
server.
Is this a good idea? Should I put in a router?

Here's what I would do:

1.) Yes, put in a router. Take that load off of the SBS.
2.)
a. Migrate from the old SBS2K to the new SBS2K3. Just like Bob said,
you can only have 1 SBS per domain.
b. After you migrate from the old SBS to the new, I suggest recycling
the old server. Load Server Standard, or Web Edition, or even deploy it
as a workstation w/ XPP. Perhaps you could use a Terminal Server on
your network. If that's the case, you can load Standard Server onto it,
and get some TS CALs. However, your boss and the people in your office
all get their very own "Terminal Servers" in essence, because w/ SBS2K3
you have Remote Web Workplace (RWW), which is a very slick and simple
and secure way to allow any users to get into their computer using
Remote Desktop (but it must be accessed via the RWW website on your
server. So a TS would probably only be useful if you have permanent
off-site workers.
Whatever you do w/ your old SBS2K, just remember that it can't co-exist
in the same domain w/ your newer SBS.
3.) After you migrate from the old SBS to the new, then set your member
servers up. You join them to the domain by running
http://sbsservername/connectcomputer. According to Microsoft, that is
even the right way to join a server to an SBS2K3 network.
You can then make your Server 2003 Standard box a file server & promote
it to a DC to help out w/ authentication.

We do networks like this all the time in our region. Fee free to give
us a call if you'd like to utilize our consulting services. We a
network integration company servicing the SouthWest US, and the whole
world remotely.

Doug Mortensen
Think Network Technologies
(970) 247-1885

Doug,

Thank you for the details.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"DKMortensen" <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
Here's what I would do:

1.) Yes, put in a router. Take that load off of the SBS.
2.)
a. Migrate from the old SBS2K to the new SBS2K3. Just like Bob said,
you can only have 1 SBS per domain.
b. After you migrate from the old SBS to the new, I suggest recycling
the old server. Load Server Standard, or Web Edition, or even deploy it
as a workstation w/ XPP. Perhaps you could use a Terminal Server on
your network. If that's the case, you can load Standard Server onto it,
and get some TS CALs. However, your boss and the people in your office
all get their very own "Terminal Servers" in essence, because w/ SBS2K3
you have Remote Web Workplace (RWW), which is a very slick and simple
and secure way to allow any users to get into their computer using
Remote Desktop (but it must be accessed via the RWW website on your
server. So a TS would probably only be useful if you have permanent
off-site workers.
Whatever you do w/ your old SBS2K, just remember that it can't co-exist
in the same domain w/ your newer SBS.
3.) After you migrate from the old SBS to the new, then set your member
servers up. You join them to the domain by running
http://sbsservername/connectcomputer. According to Microsoft, that is
even the right way to join a server to an SBS2K3 network.
You can then make your Server 2003 Standard box a file server & promote
it to a DC to help out w/ authentication.

We do networks like this all the time in our region. Fee free to give
us a call if you'd like to utilize our consulting services. We a
network integration company servicing the SouthWest US, and the whole
world remotely.

Doug Mortensen
Think Network Technologies
(970) 247-1885