Networks

Ask something
Discussion Locked

What are the network requirements?

0 helpful
4 replies

by baby_girl_no1_fan

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

I have a mixed mode (Ethernet and Token Ring) nw in Sydney and Melbourne, both need to be upgraded to a 100Mb fully switched Ethernet network. We have a mix of MS Win NT workstation & server, Win98 and several IBM main frames. I want to converge all multiple OS platforms to stands MS Win2k Operating Environment. I have a Phoenix headquarter which requires a permanent WAN network link with the Sydney branch,this needs to be a safe and secure link as there will be transfer of financiial information. There is 1 common email serverin our Phoenix office which all world wide employees need to access to check & send emails. Each office needs access to the internet with some means to restrict unauthorized users from gaining access to the network.Security is mandatory as we deal with credit card information. The following needs to be deployed:
*An upgraded network where the administrator can administer the network remotely & in a centralised manner.
*Guarantee that nw drives are mapped when logging on to the domain.
*Ensure network is secure from external attack and within.
*Ensure new software is compatible with the environment
*Perform and document testing of the system.
*Ensure maintenance agreements are in place.

If you were to plan a network requirements document for this, what would be the network requirements?

4 replies

by tp205

question 1 Time frame how fast does this need to be put together.
question 2 how old and what makes are the mainframes?
question 3 do have access to the Internet now?
Question 4 how many users do you have at Sydney?

Please answer these and I will try and give you a better estimate but if you need the answer now here is my best guess.
First you will need at least 3 w2k servers, one for print and file one for the email server connector and one for backup. If I need a true connection to PHX you could go Point to point but I would more then likely not go that why because of the cost and the lack of redundency.
I would go with a dual T1 connection to the Internet with a cisco 515e at both points PHX and SYD and use a VPN tunnel.
As far as man hours you are looking close to 100 hrs just for the servers then the change of all the Nic cards the upgrade to the workstations and servers I would think you are looking at least 1500 to 2000 man-hours for labor just for setup then for documentation and disaster recovery antoher 500.
These are all best guesses and I hope they help.

by baby_girl_no1_fan

The contract will be for a 3 month period with the provision of a roll over of 3 weeks. There is no limit on the budget, absolutely no budget..millions being okay. Being stated already that the mainframes will be replaced with servers. Yes,there is access to the internet. And finally, there are 420 users(workstations) in Sydney.

baby_girl_no1_fan@hotmail.com

by drsysadmin

I have to say, its good you have a hefty budget. 2000 characters is not enough to get everything in, so look for more in comments.

Your correct on moving all clients to W2k Pro (or XP, depending on your preference).

Now - your best bet is to set up one forest with 3 seperate domain tree's, one for your US office, 2 for your Australia offices. Assuming you want to administrate from Phoenix, make the 2 Australian offices "sub-domains" in the AD forest.

Each office will need the following:
1 PDC
1 BDC
1 Email Server - Exchange being my preference.

You could get away with everyone connecting to a central email server, but its easier (from an admin perspective) to have your HQ server do relaying to the branches.

I would also suggest an SMS server onsite at all locations, making alot of admin tasks much easier.

As for Security, start with routers at each site. Properly configured, routers are an excellent first layer. Second, look into either a Brick (hardware) or Software security system at each site. Examples are Lucent (Hardware) or ISA (software). Both will allow you to configure a security schema, utilize tunnelling VPN's for site to site connections, etc.

Mapping of Network Drives is easy - script it in the login script for the appropriate group/user. Now - we are not mapping a drive in Phoenix from Australia, are we? If we are, then other options need to be explored, such as replication.

by drsysadmin

Documenting and testing of the network will occur as you build it - thats pretty basic.

Insuring compatability of software - your helping yourself already by going to a standard operational platform. Just insure that your purchases or upgrades are the appropriate type for the environment.

Now - a couple of things to mention. Its worthwhile to set up internal DNS. Also consider multiple VLAN's for large offices. This helps segment things, making admin a lot easier.

I could go on (and on and on) about security, but this is a good start. If you REALLY want to invest in some heavy duty security, look into IDS and real-time monitoring. Remember, you asked to INSURE security - and that just isn't possible, unless you want to disconnect your network from the outside world. You can make it bloody difficult, but you can't make it impossible, unless business activity also stops. And - if someone asks about wireless - throw them out a window!

If you have any more questions, fire me an email at drsysadmin@hotmail.com.

Luck,
Dr. Sys

This discussion is closed to new replies.