Upload
theodore-houston
View
216
Download
0
Tags:
Embed Size (px)
Citation preview
1
How to Design Task 2
Author: Rodger Burgess 27th October 2008 © Copyright reserved
2
Author: Rodger Burgess 27th October 2008 © Copyright reserved
3
Introduction
Author: Rodger Burgess 27th October 2008 © Copyright reserved
4
Deliverables
Author: Rodger Burgess 27th October 2008 © Copyright reserved
5
Write Down the Deliverables
What are you to DO and Document;1. AD Structure 2. DNS3. DHCP4. Folder Structure5. Global Groups6. DomainLocal Groups with Full and
Restrictive Rights7. Each User’s Drive Mapping 8. Design the Network9. Quote of ALL components of the
Network10.No Office Furniture is to be supplied
within this projectAuthor: Rodger Burgess 27th October 2008 © Copyright reserved
6
Author: Rodger Burgess 27th October 2008 © Copyright reserved
7
UsersOne could assume
there are the following Users;
1 x Owner1 x Personal Secretary6 x Accounts5 x Secretaries1 x Office Manager
Based on this, there are a total of 14 staff within this business
Author: Rodger Burgess 27th October 2008 © Copyright reserved
8
Author: Rodger Burgess 27th October 2008 © Copyright reserved
9
Information Gathered
All User have access to these OU’s and Folders
User here ONLY have access to these OU’s and
Folders
Author: Rodger Burgess 27th October 2008 © Copyright reserved
10
DepartmentsLets Assume
for this Tasks the Departments are as follows
1. Audit2. Public_Comp3. Group_Tax4. Super
Author: Rodger Burgess 27th October 2008 © Copyright reserved
11
OU & Folders
Audit
Public_Comp
Group_Tax
Super
User_Home
Groups - Global
- DomainLocal
OU Structure
Possible Folders
Admin Audit
Accounts Public_Comp
Payroll Group_Tax
HR Super
OHS Users_Home
Policies
Author: Rodger Burgess 27th October 2008 © Copyright reserved
12
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
Author: Rodger Burgess 27th October 2008 © Copyright reserved
13
Folder Structure
C:\Data Audit
Public
Group_Tax
Super
Users_Home
Admin
Accounts
Payroll
HR
OHS
Policies
Lets assume that the current Folder Structure is adequate.
Lets now look at 2 Users and see what possible Drive Mappings they will require.
User 1: Owner
The Owner could be allocated a total of 6 Drive Mappings
User 2: Secretary
The Secretary could be allocated a total of 7 Drive Mappings
In both cases this is an excessive mount of Drive Mappings
Author: Rodger Burgess 27th October 2008 © Copyright reserved
14
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.
Author: Rodger Burgess 27th October 2008 © Copyright reserved
15
Folder StructureHave 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
Author: Rodger Burgess 27th October 2008 © Copyright reserved
16
Folder StructureNew Folder Structure.
OwnerIf we Share Admin, Departments, Audit and Users_Home and allow Inheritance that should achieve our goal.
SecretaryIf we share Staff, Departments and Users_Home and allow Inheritance that should achieve our goal.
Author: Rodger Burgess 27th October 2008 © Copyright reserved
17
RecappingTo 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.
Author: Rodger Burgess 27th October 2008 © Copyright reserved
18
Author: Rodger Burgess 27th October 2008 © Copyright reserved
19
Designing a Network
Lets start at the beginning, we know there are 2 main types of Computer Networks.
1.Peer-to-Peer2.Server
There are also many configurations of these;
• Bus• Star• Mess• Ring
Author: Rodger Burgess 27th October 2008 © Copyright reserved
20
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.
Author: Rodger Burgess 27th October 2008 © Copyright reserved
21
Designing the NetworkWhat type of Network do we
requireAs a network Administrator, Engineer or
Consultant ask yourself 3 real questions regarding installing a peer-to-peer or server centric network. That is;
1. Do you require Data sharing2. Do you require Security3. 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
22
Designing the NetworkRemember 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 Author: Rodger Burgess 27th October 2008 © Copyright reserved
23
Designing the NetworkThe 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.
Author: Rodger Burgess 27th October 2008 © Copyright reserved
24
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 Software1 GB of Ram Windows XP256 Meg Video Card Office 2003160 HDD MYOB10/100/1000 Nic In house Access DatabaseAuthor: Rodger Burgess 27th October 2008 © Copyright reserved
25
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.
Author: Rodger Burgess 27th October 2008 © Copyright reserved
26
Designing the NetworkOther 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.8mHZ8Gb Ram 1050Mhz 2 x 500Gb HDD (RAID 1)10/100/1000
Possible Server 2 SpecQuad Core 2.8mHZ8Gb Ram 1050Mhz 2 x 1TB HDD (Files)10/100/1000Author: Rodger Burgess 27th October 2008 © Copyright reserved
27
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
Author: Rodger Burgess 27th October 2008 © Copyright reserved
28
Designing the Network
Author: Rodger Burgess 27th October 2008 © Copyright reserved
29
Author: Rodger Burgess 27th October 2008 © Copyright reserved
30
AAA Accountant Network Layout
MediaCable required 1500mWall Sockets 18
Author: Rodger Burgess 27th October 2008 © Copyright reserved
31
Author: Rodger Burgess 27th October 2008 © Copyright reserved
32
Setting Naming Convention
Domain Name:……………… task2.comServer 1:……………………… exchangeServer 2:……………………… dataWorkstations:……………….. WS-?Printers:……………………… prtPrinterNameOrganisation Units:………………………… ouOrganistionUnitNameGroups:………………………grpGroupNameGlobal Groups:……………..grpGroupNameGlobalDomain Local Groups:………………………grpGroupNameDomUser:…………………………. useUsernameNetwork Address:…………. 10.4.100.0Custom Subnet Mask:………………………… 255.255.255.0Default Gateway:………….. 10.1.100.5DHCP Scope Name:……….. Task2 ScopeDHCP Scope:……………….. 10.1.100.21-70Default Gateway:…………… 10.1.100.5
Author: Rodger Burgess 27th October 2008 © Copyright reserved
33
Author: Rodger Burgess 27th October 2008 © Copyright reserved
34
Group Structure
Global Groups•grpOwnerGlobal
•grpPerSecGlobal
•grpManagerGlobal
•grpAuditAccGlobal
•grpAuditSecGlobal
•grpGeneralAccGlobal
•grpGeneralSecGlobal
DomainLocal•grpAdminDomFull
•grpDepartmentsDomFull
•grpDepartmentsDomRestrict
•grpAuditDomFull
•grpUsers_HomeDomFull
•grpStaffDomFull
•grpStaffDomRestrictRights (NTFS)
Full = R&E, LFC, R
Res = W, R&E, LFC, R, M
SharingDelete Everyone
All DomainLocal groups have Full Rights here.
Author: Rodger Burgess 27th October 2008 © Copyright reserved
35
Author: Rodger Burgess 27th October 2008 © Copyright reserved
36
Drive Mappings
Data Server Drive Mappingsdefault.bat
\\data\netlogon\%username%
A Users Drive Mappingsnet use z: \\data\Departmentnet use y: \\data\Staffnet use x: \\data\Users_Home
Owners Drive Mappingsnet use z: \\data\Adminnet use y: \\data\Departmentsnet use x: \\data\Auditnet use w: \\exchange\User_Home
Author: Rodger Burgess 27th October 2008 © Copyright reserved
37
Author: Rodger Burgess 27th October 2008 © Copyright reserved
38
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
Author: Rodger Burgess 27th October 2008 © Copyright reserved
39
Designing the Network
Exchange Data (Alterative)
Switch 16 Port Switch 16 Port
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
Author: Rodger Burgess 27th October 2008 © Copyright reserved
40
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
Gateway Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
41
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
Gateway
Printer 1
Printer 2
Printer 3
Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
42
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
aaa.comaaa.com
Servers Names
Gateway
Printer 1
Printer 2
Printer 3
Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
43
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
aaa.comaaa.com
Servers Names
Gateway
Exchange Server•DNS•AD•DHCP
Data ServerAll Business Data is to be stored here
Printer 1
Printer 2
Printer 3
Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
44
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
aaa.comaaa.com
Servers Names
Gateway
192.168.1.2192.168.1.2
Exchange Server•DNS•AD•DHCP
Data ServerAll Business Data is to be stored here
Printer 1
Printer 2
Printer 3
Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
45
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
aaa.comaaa.com
Servers Names
Gateway
192.168.1.2192.168.1.2
192.168.1.1
Exchange Server•DNS•AD•DHCP
Data ServerAll Business Data is to be stored here
Printer 1
Printer 2
Printer 3
Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
46
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
aaa.comaaa.com
Servers Names
Gateway
192.168.1.2192.168.1.2
192.168.1.1
Exchange Server•DNS•AD•DHCP
Data ServerAll Business Data is to be stored here
Printer 1
Printer 2
Printer 3
192.168.1.11
192.168.1.12
192.168.1.13
Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
47
Designing the Network
Exchange Data (Alterative)
WS 1
WS 2
WS 3
WS 6
WS 4
WS 5
WS 7
WS 8
WS 9
WS 10
WS 13
WS 11
WS 12
WS 14
aaa.comaaa.com
Servers Names
Gateway
192.168.1.2192.168.1.2
192.168.1.1
Exchange Server•DNS•AD•DHCP
Data ServerAll Business Data is to be stored here
DHCP Scope: 192.168.1.25 : 75
Printer 1
Printer 2
Printer 3
192.168.1.11
192.168.1.12
192.168.1.13
Switch 16 Port Switch 16 Port
Author: Rodger Burgess 27th October 2008 © Copyright reserved
48
Author: Rodger Burgess 27th October 2008 © Copyright reserved
49
What have we Designed
Author: Rodger Burgess 27th October 2008 © Copyright reserved
50
What have we Designed
Author: Rodger Burgess 27th October 2008 © Copyright reserved
51
What have we Designed
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
55
What do we Need
Author: Rodger Burgess 27th October 2008 © Copyright reserved
56
What do we Need
Author: Rodger Burgess 27th October 2008 © Copyright reserved
57
Quote
Author: Rodger Burgess 27th October 2008 © Copyright reserved
58
Quote
Author: Rodger Burgess 27th October 2008 © Copyright reserved
59
Quote
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
66
Author: Rodger Burgess 27th October 2008 © Copyright reserved
Our Network Drawing
67
Author: Rodger Burgess 27th October 2008 © Copyright reserved
68
Network Structures
Author: Rodger Burgess 27th October 2008 © Copyright reserved
New ScenarioThe 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 !!!!
69
Network Structures
rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
Router
DNS: rodger.comIP: 10.1.1.1DHCP:Scope Sales: 10.1.2.11 to 10.1.2.40Scope sydney: 10.1.3.11 to 10.1.3.90Scope melbourne: 10.1.4.11 to 10.1.4.25Subnet Mask: 255.255.0.0
10.1.2.11 to 10.1.2.40
10.1.3.11 to 10.1.3.90 10.1.4.11 to 10.1.4.25
SalesServer: 10.1.2.1 SydneyServer: 10.1.3.1 MelbourneServer.10.1.4.1
Author: Rodger Burgess 27th October 2008 © Copyright reserved
accounts.sydney.rodger.com
Managed Switch
Accounts.SydneyServer: 10.1.3.1
70
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
Author: Rodger Burgess 27th October 2008 © Copyright reserved
Router
Move accounts.sydney.rodger.com to here and rename it to admin.rodger.com
71
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
Author: Rodger Burgess 27th October 2008 © Copyright reserved
Router
Now add 3 Child Domains Server of admin.rodger.com.
72
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
Router
Author: Rodger Burgess 27th October 2008 © Copyright reserved
Router
73
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
Router
Router
DNS: rodger.comIP: 10.1.1.1DHCP:Scope Sales: 10.1.2.11 to 10.1.2.40Scope sydney: 10.1.3.11 to 10.1.3.30Scope melbourne: 10.1.4.11 to 10.1.4.25Subnet Mask: 255.255.0.0
10.1.2.11 to 10.1.2.40
10.1.3.11 to 10.1.3.30 10.1.4.11 to 10.1.4.25
SalesServer: 10.1.2.1 SydneyServer: 10.1.3.1 MelbourneServer.10.1.4.1
DNS: admin.rodger.comIP: 192.168.1.1DHCP:Scope accrecivable: 192.168.20.11 to 192.168.20.40Scope accpayable: 192.168.30.41 to 192.168.30.60Scope wages: 192.168.40.61 to 192.168.40.85Subnet Mask: 255.255.255.0
Author: Rodger Burgess 27th October 2008 © Copyright reserved
74
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
Router
DNS: rodger.comIP: 10.1.1.1DHCP:Scope Sales: 10.1.2.11 to 10.1.2.40Scope sydney: 10.1.3.11 to 10.1.3.30Scope melbourne: 10.1.4.11 to 10.1.4.25Subnet Mask: 255.255.0.0
10.1.2.11 to 10.1.2.40
10.1.3.11 to 10.1.3.30 10.1.4.11 to 10.1.4.25
SalesServer: 10.1.2.1 SydneyServer: 10.1.3.1 MelbourneServer.10.1.4.1
Author: Rodger Burgess 27th October 2008 © Copyright reserved
Router
DNS: admin.rodger.comIP: 192.168.1.1DHCP:Scope accrecivable: 192.168.20.11 to 192.168.20.40Scope accpayable: 192.168.30.41 to 192.168.30.60Scope wages: 192.168.40.61 to 192.168.40.85Subnet Mask: 255.255.255.0
75
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
Router
DNS: rodger.comIP: 10.1.1.1DHCP:Scope Sales: 10.1.2.11 to 10.1.2.40Scope sydney: 10.1.3.11 to 10.1.3.30Scope melbourne: 10.1.4.11 to 10.1.4.25Subnet Mask: 255.255.0.0
10.1.2.11 to 10.1.2.40
10.1.3.11 to 10.1.3.30 10.1.4.11 to 10.1.4.25
SalesServer: 10.1.2.1 SydneyServer: 10.1.3.1 MelbourneServer.10.1.4.1
Author: Rodger Burgess 27th October 2008 © Copyright reserved
Router
DNS: admin.rodger.comIP: 192.168.1.1DHCP:Scope accrecivable: 192.168.20.11 to 192.168.20.40Scope accpayable: 192.168.30.41 to 192.168.30.60Scope wages: 192.168.40.61 to 192.168.40.85Subnet Mask: 255.255.255.0
192.168.1.2
129.168.1.1
76
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
Router
DNS: rodger.comIP: 10.1.1.1DHCP:Scope Sales: 10.1.2.11 to 10.1.2.40Scope sydney: 10.1.3.11 to 10.1.3.30Scope melbourne: 10.1.4.11 to 10.1.4.25Subnet Mask: 255.255.0.0
10.1.2.11 to 10.1.2.40
10.1.3.11 to 10.1.3.30 10.1.4.11 to 10.1.4.25
SalesServer: 10.1.2.1 SydneyServer: 10.1.3.1 MelbourneServer.10.1.4.1
Author: Rodger Burgess 27th October 2008 © Copyright reserved
DNS: admin.rodger.comIP: 192.168.1.1DHCP:Scope accrecivable: 192.168.20.11 to 192.168.20.40Scope accpayable: 192.168.30.41 to 192.168.30.60Scope wages: 192.168.40.61 to 192.168.40.85Subnet Mask: 255.255.255.0
192.168.1.2
129.168.1.1
192.168.20.11 to 192.168.20.40
192.168.30.41 to 192.168.30.60
192.168.40.61 to 192.168.40.85
Router
77
Network Structures
rodger.com
admin.rodger.com
sales.rodger.com
sydney.rodger.com
melbourne.rodger.com
accreceivable.admin.rodger .com
accpayable.admin.rodger.com
wages.admin.rodger.com
Router
DNS: rodger.comIP: 10.1.1.1DHCP:Scope Sales: 10.1.2.11 to 10.1.2.40Scope sydney: 10.1.3.11 to 10.1.3.30Scope melbourne: 10.1.4.11 to 10.1.4.25Subnet Mask: 255.255.0.0
10.1.2.11 to 10.1.2.40
10.1.3.11 to 10.1.3.30 10.1.4.11 to 10.1.4.25
SalesServer: 10.1.2.1 SydneyServer: 10.1.3.1 MelbourneServer.10.1.4.1
192.168.1.2
129.168.1.1
192.168.20.11 to 192.168.20.40
192.168.30.41 to 192.168.30.60
192.168.40.61 to 192.168.40.85ReceivableServer:
192.168.20.3WagesServer: 192.168.40.3
PayableServer: 192.168.30.3
Author: Rodger Burgess 27th October 2008 © Copyright reserved
Router
DNS: admin.rodger.comIP: 192.168.1.1DHCP:Scope accrecivable: 192.168.20.11 to 192.168.20.40Scope accpayable: 192.168.30.41 to 192.168.30.60Scope wages: 192.168.40.61 to 192.168.40.85Subnet Mask: 255.255.255.0
78
Author: Rodger Burgess 27th October 2008 © Copyright reserved