Siebel Installation Guide for Microsoft Windows > Installing Siebel Enterprise Server and Related Components >
Verifying Network Connectivity for the Siebel Server Machine
The Siebel Server must have network access to other Siebel Enterprise components, such as the Siebel Gateway Name Server and the Siebel Database on the RDBMS. Use the following procedure to verify that the Siebel Server can access other Siebel Enterprise components.
The Siebel Configuration Wizard sets the TCP/IP registry values as follows:
TcpTimedWaitDelay = 30
MaxUserPort = 65534
MaxFreeTcbs = 10000
MaxHashTableSize = 2048
The Configuration Wizard saves the original registry values in the registry file SIEBEL_ROOT\siebsrvr\admin\tcp_bak.reg. If you want to reset them to the values prior to the Siebel installation, you can import them from this registry file.
NOTE: For information on verifying network connectivity for DB2 UDB for z/OS, see Implementing Siebel Business Applications on DB2 UDB for z/OS.
To verify network connectivity for the Siebel Server
- Verify network connectivity to the Siebel Gateway Name Server and the Siebel Database from the Siebel Server machine, using the test utility for your network type.
For TCP/IP networks, use the
ping utility to verify network connectivity.
- For Oracle Database, verify connectivity to the Siebel Database, then go to Step 5.
tnsping utility and Oracle database connectivity alias, as appropriate to your database, from a Command Prompt window to make sure that you can connect to the database, using the network connect string that you defined.
- For DB2 UDB for UNIX and Windows, verify connectivity to the Siebel Database, then go to Step 5.
Open a DB2 Command Window to make sure that you can connect to your database.
CAUTION: Be sure to use the DB2 Command Window, not the Command Line Processor, to enter these commands, because the Command Line Processor window uses different syntax. The commands in this procedure do not work unless issued in a DB2 Command Window.
- Choose Start, All Programs, IBM DB2, Command Line Tools, and then Command Window. Enter:
db2 connect to database_alias user user_ID using password
Database Connection Information
Database Server = DB2/NT x.x.x
SQL authorization ID = SADMIN
Database alias =
If your connection is not valid, verify your configuration.
- To close the connection, type
db2 terminate. You can also use the DB2 Command Center GUI tool to terminate.
- For MS SQL Server, verify connectivity to the Siebel Database, then go to the next step.
Navigate to Control Panel, Administrative Tools, then Data Sources (ODBC).
- Provide network connections from the Siebel Server to all applicable Siebel File System directories.
Do not use a mapped network drive as this network connection. Instead, use a UNC share. The sharename syntax must be in this form: \\Siebel_Server_Name\Sharename.
For more information, see Creating the Siebel File System.
- Verify that the Siebel File System directories are visible and that the Siebel service owner account has the necessary permissions on these directories.
If you are clustering the Siebel File System, use the Network IP resource or Network Hostname Resource assigned to that cluster file share.