Siebel Installation Guide for Microsoft Windows > Verifying and Troubleshooting Your Installation >

Verifying Network Connectivity for the Siebel Server Computer

The Siebel Server must have network access to other Siebel Enterprise components, such as the Siebel Gateway Name Server, the Siebel database on the RDBMS, and the Siebel File System. Use the following procedure to verify that the Siebel Server computer can access other Siebel Enterprise components.

The Siebel Server Configuration Wizard sets the TCP/IP registry values as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

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 the applicable keys to the values prior to the Siebel installation, then you can import them from this registry file.

NOTE:  For information about verifying network connectivity for IBM DB2 for z/OS, see Implementing Siebel Business Applications on DB2 for z/OS.

To verify network connectivity for the Siebel Server computer

1. Verify network connectivity to the Siebel Gateway Name Server and the Siebel database from the Siebel Server computer, using the test utility for your network type.

   For TCP/IP networks, use the ping utility to verify network connectivity. Or test the connection through Control Panel, Administrative Tools, Data Sources (ODBC), and then System DSN.

2. For Oracle Database, verify connectivity to the Siebel database, then go to Step 5.

   Use the 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.

3. For IBM DB2, verify connectivity to the Siebel database, then go to Step 5.
   1. Open a DB2 Command Window to make sure that you can connect to your database.

      CAUTION:  Use the DB2 Command Window, not the DB2 command line processor, to enter these commands, because the DB2 command line processor window uses different syntax. The commands in this procedure work only if you issue them in a DB2 Command Window.

   2. Choose Start, All Programs, IBM DB2, Command Line Tools, and then Command Window. Enter:

   db2 connect to database_alias user user_ID using password

   where:

   • database_alias is your database alias
   • user_ID is a valid user name on DB2
   • password is the password for that user_ID

     If your connection is valid, then you see a message that looks like the following:

   Database Connection Information
   
   Database Server       = DB2/NT x.x.x
   SQL authorization ID  = SADMIN
   Database alias        = DB_Alias

   3. If your connection is not valid, then verify your configuration.
   4. To close the connection, type db2 terminate. You can also use the DB2 Command Center GUI tool to terminate the connection.
4. For Microsoft SQL Server, verify connectivity to the Siebel database, then go to the next step.

   Navigate to Control Panel, Administrative Tools, and then Data Sources (ODBC). Under System DSN, select the data source, and click Configure. This wizard provides a button for testing the connection.

5. Provide network connections from the Siebel Server to all of the 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.

6. 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, then use the Network IP resource or Network Hostname Resource assigned to that cluster file share.