Discussion Locked

WAN infrastucture

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are implementing a WAN connecting 7 locations with 64 kb DDN lines. 2 Locations have 80 nodes each, 3 have 20 nodes each, 4 have 5 nodes each. Total 240 nodes. We are implementing Baan and Baan users will be using this network to access the application which will be hosted on a Compaq server in the Head Office location.
My question is what type of NT infrastructure should I have over the network. Do I need to have single domain model if I dont want to control/administer all the computers. Will the domain model increase traffic over the network due to longon authentication, etc. Can I run on workgroups in various locations.
Please give me pointers on what will be the best practical solution in this regard. Thanks

9 replies

by atifk

You can use a single domain model and put a BDC to all subnetwork. This will ease your account pains and you can optimize the SAM replication traffice to some acceptable degree.

by gbjoe

Yes I agree with "atifk@yahoo.com". I would also suggest trying this in a lab environment first.

good luck

by kasey

A single domain model will increase traffic over the links. nt will sync all servers within a domain. most of this data is in several books about nt admin.

The real question is:
1. whether you want to admin all of those sites or not.
2. do you need to NT share data across the wan.
3. are you inverse packet filtering out traffic that doesn't need to be on the wan.
4. are you creating a private net that would require all sites to come to a central site to access (route) to the internet and email.

NT infra is not the only thing to think about. You must put yourself into each user base and see how they will use the net. 1 site with 5 nodes could put a lot of traffic on your net (backbone) that could cause it to
crash. (ie: large file ftp transfers - they are a lot more reliable than nt netbios shares and heal themselves in low bandwidth/no bursting networks.

by vwalton

All the above is good advice. However, I think they are begging the question: 240 nodes connected over 64K?? They are going to hate you. That is just not enough bandwidth, no matter how you structure your domain model. Give serious consideration to a Terminal Server / Citrix implementation. You will have to use your bandwidth VERY carefully or this network will choke.

This discussion is closed to new replies.