QUESTION:
Is the exported data also compared with WinCC redundancy?

ANSWER:
You have a project with two redundant servers. You switch off one server, on the second server messages are exported via Storage. You are now interested about what happens when the server that has been switched off starts up again after exporting. The redundancy package only compares data that is entered during the down time. This data is transferred when the previously "failed" server returns to the database. However, no data is deleted when the databases are compared.

Description
This information is given in the WinCC Redundancy system messages and the system tag @RM_Server_Name.
Detailed information on WinCC Redundancy system messages and system tags is available in the WinCC Information System in the path "Configurations > Redundant Systems > Attachment".

Keywords
@RM_Master, @RedundantServerState, @RM_Master_Name, Active server, Standby server, Partner station, REDRT, SWITCH, Partner server, Partner computer

Standard procedure
According to the standard procedure in WinCC, you use the WinCC project duplicator to make a copy or backup of a WinCC project.
Detailed information on the WinCC project duplicator is available under:

• "WinCC Information System > Working with WinCC > Working with Projects > Duplicating and Archiving Projects"
• in Entry ID 22821109.

Exception: PI option
If the PI option is used with downtime Monitor V1.0 or Process Monitor Server V1.0, then the WinCC project data is not transferred correctly with the duplicator.
You will probably not be able to start the target project.
In this case, proceed as follows:

1. Back up and duplicate the WinCC project data including the DTM/PCM data
2. Restore the complete runnability of the source project
3. Provide the complete runnability of the source project

1. Back up and duplicate the WinCC project data including the DTM/PCM data
 

No.	Procedure
1	Open the WinCC source project Open the source project with WinCC Explorer and stop the WinCC Runtime if started.
2	Open the Project Manager Click on "PI Option" in the navigation tree of the WinCC Explorer. Right-click to open the pop-up menu " "Administrative Tools"". In the pop-up menu you select "Open Project Administrative Tools".  The Project Manager dialog opens.
3	Open the wizard for exporting DTM/PCM data In the Project Manager, select "Tools > Export Project". Fig. 01 Opening the "Export Project Wizard"
4	Export the DTM/PCM data Click on "Next" in the "Export Project Wizard". Enter a name and path and then click on "Next". Fig. 02   Click again on "Next". For "What do you want to export?" select either "Configuration Database" or "Configuration Database and Online Database Set" or "Configuration Database, Online and Offline Database Set" Fig. 03   Click on "Next" through to the end, because you normally do not need to enter anything else (dependent on the settings of the DTM or PCM). Click on "Finish". The PI data is exported. Acknowledge with "OK".
5	Delete PI project Delete the PI project in the Project Manager. Fig. 04
6	Note user authorizations for the PI option In the User Administrator, note the authorizations for the levels 600-605 for each WinCC user. Note: Levels 600-605 are authorization reservations for PI Option DTM/PCM, which will be deleted in the next step.
7	Disable PI Option Right-click to open the pop-up menu "PI_Option > Administrative Tools". Select the menu item "Options". Fig. 05   In the "Options" dialog you select "Disable PI Option". Fig. 06   Acknowledge with "OK".
8	Transfer the previous configuration Close the WinCC Explorer and re-open it to make the disabling of PI Options effective in the project.
9	Preparations for project backup Close the WinCC Explorer again so that the project can be backed up or copied.
10	Copy/backup project with the project duplicator Open the project duplicator (under "Start > SIMATIC > WinCC > Tools"). Fig. 07   Select the source project and use the menu command "Save as ...". Enter the target path and target name of the project backup. Click on "Save". The project is duplicated without PI Options and can now be copied together with the *.PIB file to a target system to restore it there.

2. Restore the complete runnability of the source project
In section 2, the DTM is re-incorporated so that the project can be re-enabled.
This step is necessary for the project to be able to run again with DTM on the source computer.
 

No.	Procedure
1	Open the WinCC source project Open the source project with the WinCC Explorer and stop the WinCC Runtime if started.
2	Enable PI Options Right-click to open the pop-menu "PI_Option > Administrative Tools" and select the menu item "Options" (see Fig. 05 ( 16 KB ) ). In "Options" you select "Enable PI Options" (see Fig. 06 ( 6 KB ) ). Acknowledge with "OK".
3	Transfer the previous configuration Stop and restart the WinCC Explorer to make the enabling of PI Options effective in the project.
4	Manually re-enter the user authorizations for the PI Options In the User Administrator, reset the previously noted authorization levels for 600-605 for all users, which are now newly created.
5	Open the wizard for re-importing DTM/PCM data into the source project In the Project Manager, select "Tools > New Project". Fig. 08 Opening the "Create Project Wizard".   Click on "Next" in the "Create Project Wizard". Select "Import an existing project" and then click on "Next". Fig. 09
6	Re-import the exported PIB file into the source project Part 1 Select <Path and name of PIB file to be imported> and click on "Next". Fig. 10
7	Re-import the exported PIB file into the source project Part 2 Under "What do you want to import?" you select "Configuration Database" or "Configuration Database and Online Database Set" or "Configuration Database, Online and Offline Database Set" and click on "Next". Fig. 11
8	Re-import the exported PIB file into the source project Part 3 Select <SQL Server Instance> and click on "Next". Fig. 12
9	Re-import the exported PIB file into the source project Part 4 Select the <Location of the PI configuration database> and click on "Next". Fig. 13
10	Re-import the exported PIB file into the source project Part 5 Select the <Location of the PI online database> and click on "Next". Fig. 14
11	Re-import the exported PIB file into the source project Part 6 Configure the data of the PI Online database set and the database parameters and click on "Next". Fig. 15
12	Re-import the exported PIB file into the source project Part 7 Define the project type and click on "Next". Fig. 16
13	Re-import the exported PIB file into the source project Part 8 Define the location for the offline database set and click on "Next". Fig. 17 Click on "Finish". The PI data is imported and created.
14	Start the source project Enable WinCC Runtime. The PI Options are once again fully available for the source project.

3. Provide the complete runnability of the source project
Section 3 is equivalent to Section 2 for the target project.
 

No.	Procedure
1	Open the WinCC target project Open the target project with the WinCC Explorer and stop the WinCC Runtime if started.
2	Adapt target project to the new computer Change the computer name in the project, close the project and then re-open it to make the changes effective.
3	Enable PI Options Right-click to open the pop-menu "PI_Option > Administrative Tools" and select the menu item "Options" (see Fig. 05 ( 16 KB ) ). In "Options" you select "Enable PI Options" (see Fig. 06 ( 6 KB ) ). Acknowledge with "OK".
4	Transfer the previous configuration Stop and restart the WinCC Explorer to make the enabling of PI Options effective in the project.
5	Manually re-enter the user authorizations for the PI Options In the User Administrator, set the previously noted authorization levels for 600-605, which are now newly created.
6	Open the wizard for re-importing DTM/PCM data into the target project In the Project Manager, select "Tools > New Project" (see Fig. 08 ( 10 KB ) ). The "Create Project Wizard" opens. Click on "Next" in the "Create Project Wizard". Select "Import an existing project" and then click on "Next" (see Fig. 09 ( 9 KB ) ).
7	Re-import the exported PIB file into the target project Part 1 Select <Path and name of PIB file to be imported> and click on "Next" (see Fig. 10 ( 8 KB ) ).
8	Re-import the exported PIB file into the target project Part 2 Under "What do you want to import?" you select "Configuration Database" or "Configuration Database and Online Database Set" and click on "Next" (see Fig. 11 ( 8 KB ) ).
9	Re-import the exported PIB file into the target project Part 3 Select <Server Instance> and click on "Next" (see Fig. 12 ( 8 KB ) ).
10	Re-import the exported PIB file into the target project Part 4 Select the <Location of the PI configuration database> and click on "Next" (see Fig. 13 ( 8 KB ) ).
11	Re-import the exported PIB file into the target project Part 5 Select the <Location of the PI online database> and click on "Next" (see Fig. 14 ( 9 KB ) ).
12	Re-import the exported PIB file into the target project Part 6 Configure the data of the PI Online database set and the database parameters and click on "Next" (see Fig. 15 ( 10 KB ) ).
13	Re-import the exported PIB file into the target project Part 7 Define the project type WARNING! Clear the check mark from "Enable Recovery from Stop to Start" (= disable this property) and click on "Next" (see Fig. 16 ( 7 KB ) ).
14	Re-import the exported PIB file into the target project Part 8 Define the location for the offline database and click on "Next" (see Fig. 17 ( 10 KB ) ).   Click on "Finish". The PI data is imported and created.
15	Start the target project Enable WinCC Runtime. The PI Options are once again fully available for the target project and the project can be run.

Guidance
In order to determine which server your client is connected to, you can query the internal tag "@RM_SERVER_NAME". In the Tag Management this tag is created in the tag group "Redundancy" as soon as you select "Activate Redundancy" in the WinCC project.


Fig. 1: Settings for redundancy

For example, use an I/O field and link this with the "@RM_SERVER_NAME" tag. In WinCC Runtime the name of the active server is then displayed in this I/O field.

Keywords
Switching, Redundancy

Instructions
On each redundant server the system creates internal tags with respect to redundancy. These provide information about the state of the redundant system from the point of view of each server. This entry shows one way of evaluating the redundancy state of both servers, making it available to higher-level systems and visualizing it in WinCC Runtime. Each server of a redundant server pair writes the state of the redundant system from its own point of view in a memory area reserved for it in the S7 controller. The controller evaluates the redundancy data of both servers, makes a plausibility check and makes the result available for further processing and visualization.

Benefits:

• Making the current state of the redundancy system available for higher-level systems
  In this way you can make the current state of the redundant WinCC server pair available for higher-level systems.
• Visualizing the redundancy state of both servers on the WinCC client
  At any specific time a client is always connected to only one of the two redundant servers. Therefore it can only display the redundancy tags of one of the two servers. This entry shows how to visualize the redundancy state of both servers in one process picture.
• Additional plausibility check in the controller (AS - automation system)
  The AS block of this entry makes a plausibility check. If an error occurs that is not recognized by WinCC redundancy, a message is triggered. Possible causes of errors:
  - Redundancy has not been activated after configuring and matching.
  - The redundancy system has an illegal state - e.g. when both WinCC servers are masters, because there is no connection between the redundant servers.

Requirements:
The following instructions require that the WinCC project be integrated in the SIMATIC Manager. The SCL and CFC editors are used. The WinCC tags and messages are created in AS-OS Engineering.
 

No.	Procedure
1	Creating an S7 function block for redundancy checking Create an S7 function block that evaluates the redundancy data of the redundant server pair. The following text document  shows the SCL source code of an S7 function block that can serve as a block template. You can enter the code in the SCL editor and change it to meet your specific requirements. I_STEP7.exe ( 10 KB )   Notes on creating the block: Before compiling the S7 program you should select the "Update scan time" option. Once you can assigned the block's symbolic name in the symbol table, you can compile the block. After successful compilation the associated function block (FB) is created in the block folder of the S7 program. Block function: Defined startup behavior Upon startup of the S7 program the relevant inputs/outputs including the monitoring timer are reset. Watchdog monitoring of both servers The block cyclically evaluates a watchdog bit for each of the two servers. Each watchdog bit must be set by WinCC and is reset by the monitoring block. If the watchdog bit is not reset after a parameterizable monitoring time, an error bit is set at the block output. Plausibility check of the redundancy state The block checks the redundancy state of both servers. An error bit is set at the block output as soon as the redundant server pair does not have the "MASTER" and "STANDBY" state and a parameterizable delay time has expired. Message behavior The errors are reported as alarms to WinCC by the ALARM_8P block. Master/Standby data at special block outputs According to the current redundancy state the computer name and the value of the "@RedundantServerState" tag are written to the corresponding output for master or standby. Possible values of the block connections "SV1_QiState" and  "SV2_QiState"(outputs): "0" (undefined state; start value of WinCC) "1" (server is master) "2" (server is standby) "3" (this server is faulty) "4" (server is standalone, no redundant operation) "9" (fault in connection to server) The states "0" to "4" correspond to the states of the system tag "@RedundantServerState". Only the state "9" is a special extension through this block.
2	Calling the S7 function block for redundancy checking in the S7 program Place the function block for redundancy checking in a CFC chart. Compile and load the S7 program. The following figure shows the built-in redundancy check block in Test mode. Fig. 01 Note: To be able to select the redundancy check block in the catalog and place it in the CFC chart you must create the block type for this block via "Options > Block Types...". Update the block type if you change the interface or attributes.
3	Compiling the OS Compile and load the WinCC station.
4	Creating C script cyclically in WinCC station In the WinCC station you create a cyclic action that writes the redundancy data to the relevant inputs of the redundancy check block in the S7. The following text document shows the source code of a C script that can serve as a template. You can insert the C code in the Global Script editor. You must change the code to meet your specific requirements and then compile it. Note: Change the constant "WINCC_SERVER1_NAME" (first #define-statement of the C script) so that it contains the computer name of one of the servers. The script compares the current computer name with this constant during Runtime. Depending on this the script writes the redundancy data to the relevant block connections of the S7 monitoring block (either "*.SV1_" or "*.SV2_" block connections). WinCC_RedundancyCheck.txt ( 3 KB ) The following figure shows the call of the function in the cyclic action. Fig. 02
5	Visualizing redundancy data Create a WinCC picture that visualizes the data of the redundancy check block. Note: You can also display messages of the redundancy check block in this picture using the WinCC Alarm Control and an appropriate filter. Fig. 03
6	Loading the standby OS Load the standby WinCC station.
7	Making a function test Test the required functionality during Runtime.

Configuration Notes:
The WinCC Project Duplicator provides an option for copying a WinCC project or duplicating it as a redundant server project.

Warning!
When using the PI options "Downtime Monitor" and "Process Monitor", refer to Entry ID: 29034551.

a) Copying a WinCC project using "Save as ..."
Using the "Save as..." button of the WinCC Project Duplicator you copy only the configuration data of the WinCC source project "1:1" into a target directory. The Runtime data of the source project is not copied. If not already available, a new empty Runtime database is created in the copied project. If a Runtime database is already available in the target directory, e.g. because the WinCC project already exists on the redundant server, the existing Runtime database will not be replaced by an empty Runtime database. The WinCC source project must not be active in Runtime nor opened in the WinCC Explorer during the copying procedure. The following holds for the target directory:

• You need "write access rights".
• There must be sufficient memory available.

Note:

• It is useful to delete all the "old" project data in the target directory before copying. This prevents project files from being open during the copying procedure. These could not be overwritten by the WinCC Project Duplicator.
• In more recent versions of Windows "write access rights" is no longer the default setting on network drive releases. You must manually assign the release for "Write".
  
  
  Fig. 01

If the "Save as" button of the WinCC Project Duplicator is to be used to generate a redundant server project, after copying you must make the following changes in the WinCC project of the redundant partner server.
 

No.	Procedure
1	Open the WinCC project in the WinCC Explorer You open the copied WinCC project in the WinCC Explorer. Note: Since the local computer name and the name of the server in the WinCC computer list do not match immediately after copying, you get an error message: "The configured server is not available. Do you want to open project using the local computer as the server?". Acknowledge the dialog with the "Start server locally" button.
2	Change the computer name Change the computer name in the computer list. For this you use the "Computer Properties" menu. Fig. 02 You must then close and reopen the WinCC project to make the change of computer name effective. For this you close the project with "File > Close" and open it again with "File > Recent File >".
3	Changing redundancy settings Make the changes with respect to redundancy. For this you open the "Redundancy" editor. Fig. 03 You enter the name of the partner server in the "Redundant Partner Server" input field. (After copying the project the local computer name is usually given here). Clear the "Standard Master" check box, because there must never be two "Standard Masters". Quit the "Redundancy" dialog by clicking on the "OK" button.
4	Activate Runtime Now you can activate WinCC Runtime on the redundant server computer.

b) Duplicating the WinCC project with "Duplicate"
Using the "Duplicate" button of the WinCC Project Duplicator you can copy the configuration and Runtime data of the WinCC source project into a target directory. The copied WinCC project is automatically changed with regard to computer name and redundancy settings.

Depending on the state of the source project either only the configuration data is copied or the configuration and Runtime data.

• Project closed
  The configuration and Runtime data is transferred.
• Project open and deactivated
  Only the configuration data is transferred.
• Project in Runtime
  Only the configuration data is transferred.
• Project open and activated
  Only the configuration data is transferred.

The same requirements hold for the target directory as when copying the project using the "Save as ..." button.

More information:

• More information is available in the WinCC Online Help under "WinCC Information System > Working with Projects > Duplicating and archiving projects" and "WinCC Information System > Configurations > Redundant Systems > Working with Redundancy > WinCC Redundancy Project Duplicator".
• If your WinCC project is integrated in the SIMATIC Manager, you should use the "PLC > Download" function of the SIMATIC Manager instead of the Project Duplicator.

Configuration Notes:
The @RedundantServerState tag indicates the redundancy status of the server - this is an internal WinCC system tag. This can be found among the tag management's internal tags.

The @RedundantServerState tag can have the following values:

• Value 1: This server is the master.
• Value 2: This server is the standby.
• Value 3: This server is faulty.
• Value 4: This server is standalone.

The redundancy option also comes with its own system tags. They are automatically created when redundancy is created.

Keywords:
Redundancy

Instructions
From the multi-client perspective, a redundant pair of servers is only a single server and is also only treated as such.

There is only one server package for the redundant pair of servers and, thus, only one server prefix. The multi-client then retrieves the relevant tags from the physical server to which it is currently connected, in other words from the master if there is no preferred server configured.

Open the pop-up menu of the "Server data" editor in the WinCC Explorer. The packages available on that computer are displayed in the data window. The symbolic package name in the "Name" column is also the server prefix.

You can also determine the name of the server prefix as described below.

• Create an IO field in the Graphics Designer and connect this to a tag of the desired server over the IO field configuration dialog. The server prefix is then set automatically in front of the tag.
• By double-clicking the "Server prefix" attribute (of a screen window, for example) you get a selection list of all the servers displayed.
  
  
  Fig. 01

The requirement for this is that the server data is created and downloaded on the client.

Instructions:
You can also use redundant servers in multi-client projects.

Requirement:
You must have completed configuration of the redundancy project, before you create the "Package" for the multiclient.

After configuring, create the package and then load it into the multiclient. If the server fails, the multiclient (as all other clients) fetches the data from the redundant server.

Keywords:
Multiple work-station system

Instructions:
Carry out the following steps on both computers of the redundant server pair. Then restart Runtime on both servers to confirm your settings.

1. Enabling redundancy:
 

No.	Procedure
1	In the WinCC "Redundancy" editor select the "Activate Redundancy" box. Fig. 01   Confirm your settings with "OK".
2	For WinCC V5.x only: In Startup under "Additional Tasks" "CCRedCodi.exe" is automatically entered. Fig. 02

2. Disabling redundancy
 

No.	Procedure
1	Clear the "Activate Redundancy" check box. Confirm your settings with "OK".
2	For WinCC V5.x only Delete "CCRedCodi.exe" manually from the startup list.
3	Delete all *.CS, *.RT and *.txt files in the Redundancy project path in Explorer. Fig. 03

Description:
One cause might be that the name resolution on one of the computers involved is not correct. Here you should check all the "HOSTS" and "LMHOSTS" files in the system path DRIVE:\WINNT\system32\drivers\etc of each computer involved. Make sure that all computers connected to the local network are correctly entered in these files with IP address and computer name (also the local computer itself). Enter the IP address and the computer name separated by at least two spaces or a tabulator.
Check whether the local LMHOSTS query is enabled in the Properties of the "WINS address" of the TCP/IP protocol. If this is not the case, then enable it.

Recommendation:
If you use the local name resolution via "HOSTS" and "LMHOSTS", we recommend creating the "LMHOSTS" and "HOSTS" file with all the computers in the network on one computer in the local network and then copying it to the other computers. This ensures that the name resolution is identical on all the computers. Enter the IP address and the computer name separated by at least two spaces or a tabulator.    

Note:
If you use the utilities "DNS" or "WINS", it is no longer necessary to have local name resolution via "LMHOSTS". 
Also remove any unnecessary network protocols. Make sure that the same network protocols are installed in the same order (DCOM protocols) on all the computers.

More information on the topic of name resolution is available in Entry ID 868014 and in the Online Help of Windows.

Keywords:
Name resolution, IP address, Network, HOSTS, LMHOSTS, DNS, WINS
 

Description
Several requirements must be fulfilled in the configuration of your Windows environment in order to enable multi-user operation of WinCC. If the settings required for this are not correct, there is no guarantee that WinCC functions error-free in multi-user mode or whether it is at all possible.

Procedure
Make the settings below on your computer to meet the requirements for multi-user operation.

1. IP addressing (TCP/IP)
The IP addressing is the basis for a working logical network. Ensure that the computers to be networked are in a physical and a logical network.

In order to fulfill this condition, you must think about how to structure you network already when assigning the IP addresses. It is not possible for two computers from different logical networks or subnetworks to communicate if you are not using a router.

The network address and subnet mask define the association of a computer to a logical network.

Note
Network address: it is not the IP address of a computer that is meant here, but the address of the network, in other words, just a part of the character string.
There are three different classes of network addresses:
 

Class	Available networks	Available hosts	Range	Example of a network address in the range	Standard subnet mask
A	126	16777214	1-126	5.0.0.0	255.0.0.0
B	16384	65534	128-191	129.10.0.0	255.255.0.0
C	2097151	254	192-223	198.10.20.0	255.255.255.0

Table 1: Network addresses with TCP/IP

Note on subnet masks and IP addresses
More information on the topic is available in the FAQ in Entry ID: 2073614.

Warning
The range of 127.X.Y.Z is reserved for loopback tests and interprocess communication and is not a reliable network address.

Example of a network address: 142.16.x.y | Network | Host |

This is an example of a Class B address. You can tell this from the address range which is from 128 to 191 for Class B. The first two tetrads correspond to the IP network address in this case.

In the case of different IP network addresses (142.16.x.y and 142.11.x.y, for example) you must make further preparations for the client-server operation, because you need a router (gateway) for different network addresses.
When using routers, it is absolutely necessary to read and apply the notes from the WinCC Information System in this path:
WinCC Installation / Release Notes > WinCC Release Notes > Notes on Operation > Network Technology and UPS.

Note
You can test correct computer addressing with the ping command.

For this you open the input prompt (Start > Run... > cmd) and execute the "ping + IP address" command (ping 128.0.0.1, for example) for each other computer.
If you do not get a response, you must check the complete network configuration and parameterization.

2. Name resolution
If you are not using a DHCP service in conjunction with DNS in your network which does this task automatically, you must configure the "lmhosts" file for name resolution. If you are using a DNS and WINS server, the system also does the name resolution.

The "lmhosts" file is in the path below in Windows:
<Drive>\Windows\system32\drivers\etc\
Open the file with the text editor and enter all the computers that can be reached in the network according to the example in the file. Delete the comments above the entries and then save the changes in the file.

Make these changes on all the computers.

Note
In order to continue optimizing the name resolution, write the keyword "#PRE" after each entry (standard maximum of 100 entries). Entries with this keyword are buffered in the cache right at system start. In the case of IP address resolution, the cache is read out first and then the lmhosts file if not all of the computer names can be resolved.

Fig. 01: The "lmhosts" file after configuration

Note
In large networks, in addition to the "lmhosts" file you should also configure the "hosts" file from the same directory in order to accelerate name resolution.

A detailed description of the "lmhosts" file is available at the Microsoft internet sites below.
German: http://support.microsoft.com/kb/102725/de
English: http://support.microsoft.com/kb/102725/en

You can perform another ping command to test whether the changes have been applied.
Open the input prompt (Start > Run... > cmd) (Start > Run... > cmd) and execute the "ping + computer name" command (for example, ping WINCCPC01) for all the computers that you entered in the "lmhosts" file in the previous step.
If you get a response and the computer name has been resolved in the associated IP address, the file is configured correctly and the name resolution works in the network.

Note
All SIMATIC WinCC stations must be logged on in the same workgroup or in the same domain.

3. Operating system
Which version of SIMATIC WinCC requires which operating system is given in Entry ID 21927773. (This also gives information about which WinCC client/server environments are possible.)

Assigning rights
Which user rights are required for specific actions is given in the WinCC Information System at the link below.
WinCC Installation / Release Notes > Installation Notes > Requirements for the Installation > Access Rights in the Operating System.

Note
If you install an update (formerly hotfix) or a Service Pack for WinCC, you should always read the Release Notes for this extension. Under certain circumstances the required user rights might change.

4. Terminal bus
The terminal bus must be configured for the right network card in the SIMATIC shell. If you are using multiple network cards there is the danger that the network card over which the WinCC communication is supposed to run is not selected here.
Notes on configuring the terminal bus are available in Entry ID 25437381.

Another indicator that the network is functioning (availability of the other computers) is that you can see the projects of the other computers in the network in the SIMATIC shell.

5. Order of network cards
The order of network cards defines the order in which the network services access the network cards. You must therefore ensure that the network card/connection (that you have selected as terminal bus) is in first place.

You make the settings in the path below: "Control Panel > Network Connections > Advanced > Advanced Settings... > Network Cards and Connections".

If you are using Windows 7 or Windows Server 2008, you must make settings in the Explorer window to get to this setting.
For this you switch to the Windows Explorer. Show the menu bar via "Organize > Layout". You can also have this menu bar displayed temporarily by pressing the "Alt" key.

Fig. 02: Display of the menu bar in Windows 7 and Microsoft Server 2008

Now, by way of the Control Panel, switch to the "Networks and Release Center". In the left window pane is the "Change adapter settings" button. Operate the button and then proceed with the "Advanced" step as already described above.

6. Firewall
For the sake of security computers often have a firewall installed. Only the Windows firewall is released for operation with WinCC. If you activate this, you must then run the SIMATIC Security Control again and "Make settings". Port filters are generally not released.

Further information
More information about the distributed systems is available in the WinCC Information at the following link:
Configurations > Distributed Systems

If you are using WinCC version V5 or older, refer also to the notes in the document below. There you will also find notes on WINS, DNS and IPX.

WinCC_PCS7_lmhost_e.pdf ( 258 KB )

Caution
The functions and solutions described in this article confine themselves to the realization of the automation task predominantly. Furthermore, please take into account that corresponding protective measures have to be taken in the context of Industrial Security when connecting your equipment to other parts of the plant, the enterprise network or the Internet. Further information can be found in Entry ID: 50203404.

Keywords
Network configuration, System requirements, HOSTS, LMHOSTS, LMHOST, DNS, WINS, IP address, Subnet, Subnet mask, 70775, 31385098, Client, Server