19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Safeguard Catalogue - Communications Remarks<br />

____________________________________________________________________ .........................................<br />

Note: <strong>The</strong> IP address and the static name entered in WINS take priority over<br />

the IP address allocated by the DHCP server. In this case a client reservation<br />

is generated for the client which will be established in the WINS database.<br />

<strong>The</strong> following files are stored in the directory<br />

%SystemRoot%\SYSTEM32\DHCP, which is established when setting up a<br />

DHCP server:<br />

- DHCP.MDB is the DHCP database file.<br />

- DHCP.TMP is a temporary file, which DHCP installs for temporary<br />

database files.<br />

- <strong>The</strong> files JET.LOG and JET*.LOG contain protocols with the complete<br />

transactions that have been executed with the database. With the help of<br />

these files, DHCP can reproduce possible lost data if required.<br />

- SYSTEM.MDB is used by DHCP to save data regarding the structure of its<br />

database.<br />

Note: <strong>The</strong> files DHCP.TMP, DHCP.MDB, JET.LOG and SYSTEM.MDB<br />

should neither be deleted nor changed in any way since this can lead to faulty<br />

DHCP functions. Access to these files may only be granted to administrators<br />

as, otherwise, unsupervised changes to DHCP configuration are possible.<br />

WINS (Windows Internet Name Service)<br />

Via WINS, NetBIOS-computer-names can be allocated to IP addresses.<br />

Installation of a WINS server takes place as part of the installation of TCP/IP<br />

on Windows NT servers. To achieve a better availability of servers and a<br />

balanced workload, several WINS servers should be set up. Each WINS server<br />

must be configured in such a way that it functions as a reproduction partner<br />

for at least one other WINS server.<br />

<strong>Information</strong> regarding the reproduction of database entries for the partner is<br />

part of a WINS server configuration. A Pull-Partner is a WINS server that<br />

obtains copies of database entries from its partner by first sending a request<br />

and then receiving the desired copies. A Push-Partner is a WINS server that<br />

sends its partner a renewal message, if something has changed in the WINS<br />

database. If its partner then replies with a request for reproduction, the Push-<br />

Partner sends a copy of the up-to-date WINS database to the reproduction<br />

partner. To ensure that the databases on the primary WINS server and the<br />

back-up server always correspond to one another, both servers must act as<br />

Push and Pull-Partners. It is always advisable for reproduction partners to take<br />

both roles, i.e. Push and Pull-Partner.<br />

A particular point in time, length of time or number of data sets must be<br />

determined for every WINS server as a threshold value. If this value is<br />

reached, the reproduction of the databank will be performed. If a certain point<br />

in time is determined for the reproduction, this will be carried out once. On the<br />

other hand, if a certain length of time is established, reproduction will be<br />

repeated according to the appropriate intervals. Within a geographical region<br />

this could lie, for example, between ¼ and ½ an hour, whilst over larger<br />

distances, intervals of a few hours can be selected.<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!