Transcript Designing the Network

How to
Design Task 2
1
Author: Rodger Burgess
27th October 2008 © Copyright reserved
2
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Introduction
3
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Deliverables
4
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Write Down the Deliverables
What are you to DO and Document;
1.
2.
3.
4.
5.
6.
AD Structure
DNS
DHCP
Folder Structure
Global Groups
DomainLocal Groups with Full and Restrictive
Rights
7. Each User’s Drive Mapping
8. Design the Network
9. Quote of ALL components of the Network
10.No Office Furniture is to be supplied within this
project
5
Author: Rodger Burgess
27th October 2008 © Copyright reserved
6
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Users
One could assume there are
the following Users;
1 x Owner
1 x Personal Secretary
6 x Accounts
5 x Secretaries
1 x Office Manager
Based on this, there are a total of 14 staff
within this business
7
Author: Rodger Burgess
27th October 2008 © Copyright reserved
8
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Information Gathered
User here ONLY have access to
these OU’s and Folders
All User have access to these
OU’s and Folders
9
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Departments
Lets Assume for
this Tasks the
Departments
are as follows
1.
2.
3.
4.
Audit
Public_Comp
Group_Tax
Super
10
Author: Rodger Burgess
27th October 2008 © Copyright reserved
OU & Folders
OU Structure
Possible Folders
Audit
Admin
Audit
Public_Comp
Accounts
Public_Comp
Group_Tax
Payroll
Group_Tax
Super
HR
Super
User_Home
OHS
Users_Home
Groups - Global
Policies
- DomainLocal
11
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Folder Structure
Admin
Audit
Accounts
Public_Comp
Payroll
Group_Tax
HR
Super
OHS
Users_Home
Policies
C:\Data
Audit
Public
Group_Tax
Super
Users_Home
Admin
Accounts
Payroll
HR
OHS
Policies
12
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Folder Structure
C:\Data
Lets assume that the current Folder
Structure is adequate.
Audit
Public
Lets now look at 2 Users and see
what possible Drive Mappings they
will require.
Group_Tax
Super
Users_Home
User 1: Owner
Admin
Accounts
Payroll
The Owner could be allocated a total
of 6 Drive Mappings
HR
User 2: Secretary
OHS
The Secretary could be allocated a
total of 7 Drive Mappings
Policies
In both cases this is an excessive
mount of Drive Mappings
13
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Folder Structure
It would be very difficult for users to navigate
through 6 to 7 Drive Mappings.
Our task here is to restructure our Folder Structure
so Users have no more than 4 Drive Mappings.
Have a go and see what you can come up with.
TIP
By adding a Department and Staff folder could help.
14
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Folder Structure
Have any luck. Here is what I think could achieve
our goal.
C:\ Data
Admin
Accounts
Payroll
Staff
HR
Policies
OHS
Departments
Public_Tax
Group_Tax
Super
Audit
Users_Home
15
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Folder Structure
New Folder Structure.
Owner
If we Share Admin, Departments,
Audit and Users_Home and allow
Inheritance that should achieve our
goal.
Secretary
If we share Staff, Departments and
Users_Home and allow Inheritance
that should achieve our goal.
16
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Recapping
To this point we have designed the AD and Folder
Structure. We could design our Groups and Drive
Mappings to suit.
At this stage we are still uncertain as to the configuration
of our Network. How many Workstations and what
Server configuration will we implement. For us to
develop our Drive Mappings we will need to know the
names of our server/s
I would suggest at this stage we design at least our
Server/s. If this is the case then why not design the
Network completely.
17
Author: Rodger Burgess
27th October 2008 © Copyright reserved
18
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing a Network
Lets start at the beginning, we know there are
2 main types of Computer Networks.
1. Peer-to-Peer
2. Server
There are also many configurations of these;
•
•
•
•
Bus
Star
Mess
Ring
19
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing a Network
Lets look at the differences between these networks
Peer-to-Peer
• Files are stored on each computer.
• Security can be limited.
• Duplication of resources such as printer, scanners can be
difficult.
• Backups can be difficult to perform and schedule.
• Less costly to setup.
Server
•
•
•
•
•
Files are stored on the server/s.
Security is by way of Unique Username and Password.
Sharing of resources easier.
Backups can be run and maintained from a central location.
Expensive to setup and maintain.
20
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
What type of Network do we require
As a network Administrator, Engineer or Consultant ask
yourself 3 real questions regarding installing a peer-topeer or server centric network. That is;
1. Do you require Data sharing
2. Do you require Security
3. Number of staff using the network.
If you require either 1 or 2, then a server centric system
MUST be designed and installed
If there are more then say 12 staff using the network then a
server centric network should be installed due to its cost
effectiveness.
Author: Rodger Burgess
27th October 2008 © Copyright reserved
21
Designing the Network
Remember our Network and Server Bottlenecks
Your servers should be a powerful computer/s capable of
handling all the work your network will throw at them.
Don't cut corners by using a bottom-of-the-line computer
that you bought at a discount computer store. No
substitute for quality. Remember these:
1. Processor
2. Memory
3. Disk
4. Network card
22
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
The Server's Configuration Options
All network operating systems have options that you
can configure. Unfortunately, no hard-and-fast rules
exist for setting these options. Otherwise, you
wouldn't have options.
The following are some of the more important tuning
options available for most servers:
Virtual memory options, Disk striping, Network
protocols, Free disk space on the server, Servers like
to have plenty of breathing room on their disks.
23
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
As we assessed from the information given there are 14
staff within AAA Accountants. Therefore a Server Centric
system MUST be implemented.
Based on this information we now need at least 14
Workstations. Lets assume that the architecture of these
workstation are as follows. A good starting point.
P4 2.6Hz
1 GB of Ram
256 Meg Video Card
160 HDD
10/100/1000 Nic
Software
Windows XP
Office 2003
MYOB
In house Access Database
24
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
A General Network Rule
• Workstations do 95% of there processing
• Server do 5% of the processing
If this is the case then 20 workstation can be located on
a network segment, if the server has the same
architecture as the workstations.
If we change the specification on the server to have
more RAM, Faster HDD and CPU or a better
motherboard then in theory we can have more
workstations on that network segment.
25
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Other Factors to
Consider
•RAID
•Amount of Storages space
•Amount of RAM
•Network distance (100m)
•Type of NIC
•Router or Switch
•Or just general network
traffic
•Do the users do more right
or read request of the
servers
Possible Server 1 Spec
A starting point
Quad Core 2.8mHZ
8Gb Ram 1050Mhz
2 x 500Gb HDD (RAID 1)
10/100/1000
Possible Server 2 Spec
Quad Core 2.8mHZ
8Gb Ram 1050Mhz
2 x 1TB HDD (Files)
10/100/1000
26
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
We can split the work load of the 2 Servers into the
following configuration;
•Server 1
DNS, AD, DHCP and Exchange Server (All
emails and Permission are handled by this server)
•Server 2
File Server (All files are stored on this server)
The following slide will demonstrate how this can be
achieved
27
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
28
Author: Rodger Burgess
27th October 2008 © Copyright reserved
29
Author: Rodger Burgess
27th October 2008 © Copyright reserved
AAA Accountant Network Layout
Media
Cable required 1500m
Wall Sockets 18
30
Author: Rodger Burgess
27th October 2008 © Copyright reserved
31
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Setting Naming Convention
Domain Name:………………
Server 1:………………………
Server 2:………………………
Workstations:………………..
Printers:………………………
Organisation
Units:…………………………
Groups:………………………
Global Groups:……………..
Domain Local
Groups:………………………
User:………………………….
Network Address:………….
Custom Subnet
Mask:…………………………
Default Gateway:…………..
DHCP Scope Name:………..
DHCP Scope:………………..
Default Gateway:……………
task2.com
exchange
data
WS-?
prtPrinterName
ouOrganistionUnitName
grpGroupName
grpGroupNameGlobal
grpGroupNameDom
useUsername
10.4.100.0
255.255.255.0
10.1.100.5
Task2 Scope
10.1.100.21-70
10.1.100.5
32
Author: Rodger Burgess
27th October 2008 © Copyright reserved
33
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Group Structure
Global Groups
DomainLocal
•grpOwnerGlobal
•grpPerSecGlobal
•grpManagerGlobal
•grpAuditAccGlobal
•grpAuditSecGlobal
•grpGeneralAccGlobal
•grpGeneralSecGlobal
•grpAdminDomFull
•grpDepartmentsDomFull
•grpDepartmentsDomRestrict
•grpAuditDomFull
•grpUsers_HomeDomFull
•grpStaffDomFull
•grpStaffDomRestrict
Sharing
Rights (NTFS)
Delete Everyone
Full = R&E, LFC, R
All DomainLocal groups have Full
Rights here.
Res = W, R&E, LFC, R, M
34
Author: Rodger Burgess
27th October 2008 © Copyright reserved
35
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Drive Mappings
Data Server
Drive Mappings
default.bat
\\data\netlogon\%username%
A Users Drive Mappings
net use z: \\data\Department
net use y: \\data\Staff
net use x: \\data\Users_Home
Owners Drive Mappings
net use z: \\data\Admin
net use y: \\data\Departments
net use x: \\data\Audit
net use w: \\exchange\User_Home
36
Author: Rodger Burgess
27th October 2008 © Copyright reserved
37
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Data (Alterative)
Exchange
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
WS 11
WS 4
38
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Data (Alterative)
Exchange
Switch 16 Port
Switch 16 Port
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
WS 11
WS 4
39
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Data (Alterative)
Exchange
Gateway
Switch 16 Port
Switch 16 Port
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
WS 11
WS 4
40
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Data (Alterative)
Exchange
Gateway
Switch 16 Port
Switch 16 Port
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
Printer 1
Printer 2
Printer 3
WS 11
WS 4
41
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
aaa.com
Servers Names
Exchange
Gateway
Switch 16 Port
aaa.com
Data (Alterative)
Switch 16 Port
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
Printer 1
Printer 2
Printer 3
WS 11
WS 4
42
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Exchange Server
aaa.com
•DNS
•AD
•DHCP
Exchange
Gateway
Servers Names
Switch 16 Port
aaa.com
Data (Alterative)
Data Server
All Business
Data is to be
stored here
Switch 16 Port
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
Printer 1
Printer 2
Printer 3
WS 11
WS 4
43
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Exchange Server
aaa.com
•DNS
•AD
•DHCP
Exchange
Servers Names
aaa.com
Data (Alterative)
192.168.1.2
192.168.1.2
Gateway
Switch 16 Port
Data Server
All Business
Data is to be
stored here
Switch 16 Port
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
Printer 1
Printer 2
Printer 3
WS 11
WS 4
44
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Exchange Server
aaa.com
•DNS
•AD
•DHCP
Exchange
Servers Names
aaa.com
Data (Alterative)
192.168.1.2
192.168.1.2
Gateway
Switch 16 Port
Data Server
All Business
Data is to be
stored here
Switch 16 Port
192.168.1.1
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
Printer 1
Printer 2
Printer 3
WS 11
WS 4
45
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Exchange Server
aaa.com
•DNS
•AD
•DHCP
Exchange
Servers Names
aaa.com
Data (Alterative)
192.168.1.2
192.168.1.2
Gateway
Switch 16 Port
Data Server
All Business
Data is to be
stored here
Switch 16 Port
192.168.1.1
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
Printer 1
192.168.1.11
Printer 2
192.168.1.12
Printer 3
192.168.1.13
WS 11
WS 4
46
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Designing the Network
Exchange Server
aaa.com
•DNS
•AD
•DHCP
Exchange
aaa.com
Servers Names
Data (Alterative)
192.168.1.2
192.168.1.2
Gateway
Switch 16 Port
Data Server
All Business
Data is to be
stored here
Switch 16 Port
192.168.1.1
WS 1
WS 5
WS 12
WS 8
WS 2
WS 6
WS 13
WS 9
WS 3
WS 7
WS 14
WS 10
Printer 1
192.168.1.11
Printer 2
192.168.1.12
Printer 3
192.168.1.13
WS 11
WS 4
DHCP Scope: 192.168.1.25 : 75
47
Author: Rodger Burgess
27th October 2008 © Copyright reserved
48
Author: Rodger Burgess
27th October 2008 © Copyright reserved
What have we Designed
49
Author: Rodger Burgess
27th October 2008 © Copyright reserved
What have we Designed
50
Author: Rodger Burgess
27th October 2008 © Copyright reserved
What have we Designed
51
Author: Rodger Burgess
27th October 2008 © Copyright reserved
52
Author: Rodger Burgess
27th October 2008 © Copyright reserved
53
Author: Rodger Burgess
27th October 2008 © Copyright reserved
54
Author: Rodger Burgess
27th October 2008 © Copyright reserved
What do we Need
55
Author: Rodger Burgess
27th October 2008 © Copyright reserved
What do we Need
56
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Quote
57
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Quote
58
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Quote
59
Author: Rodger Burgess
27th October 2008 © Copyright reserved
60
Author: Rodger Burgess
27th October 2008 © Copyright reserved
61
Author: Rodger Burgess
27th October 2008 © Copyright reserved
62
Author: Rodger Burgess
27th October 2008 © Copyright reserved
63
Author: Rodger Burgess
27th October 2008 © Copyright reserved
64
Author: Rodger Burgess
27th October 2008 © Copyright reserved
65
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Our Network Drawing
66
Author: Rodger Burgess
27th October 2008 © Copyright reserved
67
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
New Scenario
The goal in the exercise is to delete, move or change
accounts.sydney.rodger.com and create a child domain
of rodger.com that will cater for 3 other servers. These
servers have to be on a different Network Address from
the 3 servers currently in place.
These 3 servers will deal with;
1. Accounts Payable
2. Accounts Receivable
3. Wages
What would you come up with !!!!
Author: Rodger Burgess
27th October 2008 © Copyright reserved
68
Network Structures
rodger.com
Router
DNS: rodger.com
IP: 10.1.1.1
DHCP:
Scope Sales: 10.1.2.11 to 10.1.2.40
Scope sydney: 10.1.3.11 to 10.1.3.90
Scope melbourne: 10.1.4.11 to 10.1.4.25
Subnet Mask: 255.255.0.0
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
10.1.2.11 to 10.1.2.40
SalesServer: 10.1.2.1
10.1.3.11 to 10.1.3.90
SydneyServer: 10.1.3.1
10.1.4.11 to 10.1.4.25
MelbourneServer.10.1.4.1
Managed Switch
accounts.sydney.rodger.com
Accounts.SydneyServer: 10.1.3.1
69
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
rodger.com
Router
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
Move accounts.sydney.rodger.com to
here and rename it to admin.rodger.com
70
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
rodger.com
Router
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
Now add 3 Child Domains Server of admin.rodger.com.
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
71
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
rodger.com
Router
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
Router
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
72
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
DNS: admin.rodger.com
IP: 192.168.1.1
DHCP:
rodger.com
Scope accrecivable: 192.168.20.11 to 192.168.20.40
Scope accpayable: 192.168.30.41 to 192.168.30.60
Scope wages: 192.168.40.61 to 192.168.40.85
Subnet Mask: 255.255.255.0
admin.rodger.com
DNS: rodger.com
IP: 10.1.1.1
DHCP:
Scope Sales: 10.1.2.11 to 10.1.2.40
Scope sydney: 10.1.3.11 to 10.1.3.30
Scope melbourne: 10.1.4.11 to 10.1.4.25
Subnet Mask: 255.255.0.0
Router
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
10.1.2.11 to 10.1.2.40
SalesServer: 10.1.2.1
10.1.3.11 to 10.1.3.30
SydneyServer: 10.1.3.1
10.1.4.11 to 10.1.4.25
MelbourneServer.10.1.4.1
Router
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
73
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
DNS: admin.rodger.com
IP: 192.168.1.1
DHCP:
rodger.com
Scope accrecivable: 192.168.20.11 to 192.168.20.40
Scope accpayable: 192.168.30.41 to 192.168.30.60
Scope wages: 192.168.40.61 to 192.168.40.85
Subnet Mask: 255.255.255.0
admin.rodger.com
DNS: rodger.com
IP: 10.1.1.1
DHCP:
Scope Sales: 10.1.2.11 to 10.1.2.40
Scope sydney: 10.1.3.11 to 10.1.3.30
Scope melbourne: 10.1.4.11 to 10.1.4.25
Subnet Mask: 255.255.0.0
Router
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
10.1.2.11 to 10.1.2.40
SalesServer: 10.1.2.1
10.1.3.11 to 10.1.3.30
SydneyServer: 10.1.3.1
10.1.4.11 to 10.1.4.25
MelbourneServer.10.1.4.1
Router
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
74
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
DNS: admin.rodger.com
IP: 192.168.1.1
DHCP:
rodger.com
Scope accrecivable: 192.168.20.11 to 192.168.20.40
Scope accpayable: 192.168.30.41 to 192.168.30.60
Scope wages: 192.168.40.61 to 192.168.40.85
Subnet Mask: 255.255.255.0
admin.rodger.com
129.168.1.1
192.168.1.2
DNS: rodger.com
IP: 10.1.1.1
DHCP:
Scope Sales: 10.1.2.11 to 10.1.2.40
Scope sydney: 10.1.3.11 to 10.1.3.30
Scope melbourne: 10.1.4.11 to 10.1.4.25
Subnet Mask: 255.255.0.0
Router
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
10.1.2.11 to 10.1.2.40
SalesServer: 10.1.2.1
10.1.3.11 to 10.1.3.30
SydneyServer: 10.1.3.1
10.1.4.11 to 10.1.4.25
MelbourneServer.10.1.4.1
Router
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
75
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
DNS: admin.rodger.com
IP: 192.168.1.1
DHCP:
rodger.com
Scope accrecivable: 192.168.20.11 to 192.168.20.40
Scope accpayable: 192.168.30.41 to 192.168.30.60
Scope wages: 192.168.40.61 to 192.168.40.85
Subnet Mask: 255.255.255.0
admin.rodger.com
129.168.1.1
192.168.1.2
DNS: rodger.com
IP: 10.1.1.1
DHCP:
Scope Sales: 10.1.2.11 to 10.1.2.40
Scope sydney: 10.1.3.11 to 10.1.3.30
Scope melbourne: 10.1.4.11 to 10.1.4.25
Subnet Mask: 255.255.0.0
Router
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
10.1.2.11 to 10.1.2.40
SalesServer: 10.1.2.1
10.1.3.11 to 10.1.3.30
SydneyServer: 10.1.3.1
10.1.4.11 to 10.1.4.25
MelbourneServer.10.1.4.1
Router
accreceivable.admin.rodger .com
192.168.20.11 to 192.168.20.40
accpayable.admin.rodger.com
192.168.30.41 to 192.168.30.60
wages.admin.rodger.com
192.168.40.61 to 192.168.40.85
76
Author: Rodger Burgess
27th October 2008 © Copyright reserved
Network Structures
DNS: admin.rodger.com
IP: 192.168.1.1
DHCP:
rodger.com
Scope accrecivable: 192.168.20.11 to 192.168.20.40
Scope accpayable: 192.168.30.41 to 192.168.30.60
Scope wages: 192.168.40.61 to 192.168.40.85
Subnet Mask: 255.255.255.0
admin.rodger.com
129.168.1.1
192.168.1.2
DNS: rodger.com
IP: 10.1.1.1
DHCP:
Scope Sales: 10.1.2.11 to 10.1.2.40
Scope sydney: 10.1.3.11 to 10.1.3.30
Scope melbourne: 10.1.4.11 to 10.1.4.25
Subnet Mask: 255.255.0.0
Router
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
10.1.2.11 to 10.1.2.40
SalesServer: 10.1.2.1
10.1.3.11 to 10.1.3.30
SydneyServer: 10.1.3.1
10.1.4.11 to 10.1.4.25
MelbourneServer.10.1.4.1
Router
accreceivable.admin.rodger .com
192.168.20.11 to 192.168.20.40
ReceivableServer: 192.168.20.3
accpayable.admin.rodger.com
192.168.30.41 to 192.168.30.60
PayableServer: 192.168.30.3
wages.admin.rodger.com
192.168.40.61 to 192.168.40.85
WagesServer: 192.168.40.3
77
Author: Rodger Burgess
27th October 2008 © Copyright reserved
78
Author: Rodger Burgess
27th October 2008 © Copyright reserved