Help First Timer Lost with Networking

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am new to the whole server/client setup. I have three offices spread out
geographically. I have just purchased a server and want to setup a network
so that all of the offices and the computers in those offices can communicate
through the server (I also want to centralize the database to be stored on
the server). I assume this is an easy task but I have NO idea where to
begin. Does anyone have any tips on where I can go to find resources on
setting up this network?

P.S. All existing desktops and laptops are running Windows XP and the
server is running Windows server 2003.
 
Biebs said:
I am new to the whole server/client setup. I have three offices
spread out geographically. I have just purchased a server and want
to setup a network so that all of the offices and the computers in
those offices can communicate through the server (I also want to
centralize the database to be stored on the server). I assume this
is an easy task but I have NO idea where to begin. Does anyone have
any tips on where I can go to find resources on setting up this
network?

P.S. All existing desktops and laptops are running Windows XP and the
server is running Windows server 2003.
Click to expand...

A few thoughts

1. How are the satellite offices supposed to connect to the main office? VPN
might work - I'd pick up three compatible Sonicwall firewalls and configure
site link VPNs between them.
2. Are you planning on using a domain or a workgroup?
3. Note that accessing anything largeish such as a database across any
remote connection is probably going to stink, performancewise, and is also
likely to cause problems/data errors.
4. What else do you want / plan to run?

I'd look into using Terminal Services if this were me - but if you want a
domain, you'll need a separate box for the TS.

If you haven't done anything like this kind of setup before, I strongly
suggest you engage a consultant to do the setup. Well worth it if you find
someone good.
 
Hey Biebs,

I admire your enthusiasum but I would suggest getting someone to help you
that really knows networking here. This is no easy task. It appears that you
will need more than one server to do this. After you figure that out you will
need to have an incredible internet connection/bill T-1 or better. To get an
Idea? Take a look at some of the other posts in this group and see what you
think?
 
Thanks for the great advice. I had thought about hiring a consultant to do
the setup for me. I plan to give it a try on my own first and if I can not
figure it out I will hire some help.

Lanwench to answer your questions:
1. I had thought that I would connect the satellite offices through a VPN.
Unless I find a better option a VPN is what I plan to use.
2. As for the domain or workgroup question, what are the pros and cons of
each? I have not considered these options yet so any info you have would be
helpful.
3. Is there any way around the issue of accessing large amounts of data
remotely to avoid problems/data errors?
4. Right now the reason that we are going to this setup is because we just
bought a new program that centralizes our client database, appointment
scheduling, financial data, and job specific programs. Other than that one
program I do not see any other uses for the server. Possibly as an email
server in the future but not at this point.

Thank you for your help.
 
Joe
Why do you say that I will need more than one server to do the tasks that I
want to do? Won't one server suffice?
 
Hello Biebs,

I say this because of the terminal server. It is possible to use one but you
would be putting an extreme load on it. But then again it depends on how you
set it up: Workgroup or Domain Controller.

I like them both but the Domain Controller gives you much more flexibility
and is harder to set up.

Here are a few good links for you

http://support.microsoft.com/?id=323441
http://support.microsoft.com/default.aspx?scid=kb;en-us;323381
http://support.microsoft.com/?id=314076



If clients from within the network (behind the server) are using it to
access the internet and also external clients incoming you will need to
assess the traffic and maybe you will need just one.On paper or somehow map
this out what you need from your network and see what is feasable. (Money and
Time)

This is about as far as I can go for now. Keep going and never quit!

Joe
 
Biebs said:
Thanks for the great advice. I had thought about hiring a consultant
to do the setup for me. I plan to give it a try on my own first and
if I can not figure it out I will hire some help.
Click to expand...

Seriously, if you haven't done this before, get some outside help and pick
up some basic Windows networking books first --unless you just plan to test
& tinker with this in a non-production/"lab" environment until you know
everything is done 100% properly. Especially given that you plan to have
remote offices - it will be a real pain in the said:
Lanwench to answer your questions:
1. I had thought that I would connect the satellite offices through a
VPN. Unless I find a better option a VPN is what I plan to use.
Click to expand...

Not a problem...
2. As for the domain or workgroup question, what are the pros and
cons of each?
Click to expand...

Short answer: a domain gives you centralized control/admin/security, and a
workgroup is just a bunch of computers chatting amongst themselves - they
each have their own logins/security/whatnot.

I have not considered these options yet so any info
you have would be helpful.
3. Is there any way around the issue of accessing large amounts of
data remotely to avoid problems/data errors?
Click to expand...

Yes. Terminal Services, as I mentioned previously. :)
4. Right now the reason that we are going to this setup is because we
just bought a new program that centralizes our client database,
appointment scheduling, financial data, and job specific programs.
Other than that one program I do not see any other uses for the
server. Possibly as an email server in the future but not at this
point.
Click to expand...

If you use Terminal Services, you will want to leave this box doing nothing
else - don't give it any other network roles.

For a domain controller/e-mail server, look into Small Business Server
2003 - includes Win2003/Exchange2003/etc. Note that you cannot use it for
terminal services (only Remote Desktop - for admin access only) - so you'd
be talking 2 servers.
Thank you for your help.
Click to expand...

No worries - hope this does help.
 
<jumping in, inline>
Hello Biebs,

I say this because of the terminal server. It is possible to use one
but you would be putting an extreme load on it.
Click to expand...

Not necessarily.
But then again it
depends on how you set it up: Workgroup or Domain Controller.
Click to expand...

It really depends more on the expected resource load, and the server
hardware. I would not want to use a domain controller as a TS box....
I like them both but the Domain Controller gives you much more
flexibility and is harder to set up.
Click to expand...

Yes, it's more complicated - but setting up a reliable workgroup is actually
more work in my view.
 
Biebs said:
Thanks for the great advice. I had thought about hiring a consultant to do
the setup for me. I plan to give it a try on my own first and if I can not
figure it out I will hire some help.
Click to expand...

That is fine up to a point,...but it can cost you much more if the
consultant has to spend a bunch of extra time fixing what you messed up
before he/she can get to the real work.
 
What do ya think Phillip?

Cheap is expensive ; )

I agree with you. This is a large task for a beginner.

Joe
 
Back
Top