Siebel Installation Guide for Microsoft Windows: Servers, Mobile Web Clients, Tools > Installing the Siebel Server >

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 Software 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\tcp_back.reg. If you want to reset them to the values prior to the Siebel installation, you can import them from this registry file.

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

1. 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.

2. Verify connectivity to the Siebel Database:
   • Oracle. Use the tnsping utility and Net9 database 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.
   • DB2 UDB for UNIX and Windows. 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.

   1. Choose Start > Programs > IBM DB2 > Command Line Tools > Command Window, and enter:

   db2 connect to database_alias user user_ID using password

   where:

   • database_alias = Your database alias
   • user_ID = A valid user name on DB2
   • password = The password for that user_ID

     If your connection is valid, you should 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

   If your connection is not valid, verify your configuration.

   2. To close the connection, type db2 terminate. You can also use the DB2 Command Center GUI tool to terminate.
3. Provide a network connection from the Siebel Server to the Siebel File System.

   Do not use a mapped network drive as this network connection. Instead, use a UNC share. The sharename syntax should be in this form: \\Siebel_Server_Name\Sharename.

4. Verify that the Siebel File System directory is visible and that the Siebel service owner account can copy files to and from it.

   If you are clustering the Siebel File System, use the Network IP resource or Network Hostname Resource assigned to that cluster file share.