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 server. Use the following procedure to verify that the Siebel Server can access the Siebel Enterprise.

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 Siebel Server Configuration wizard saves the original registry values in the SIEBEL_ROOT\siebsrvr\tcp_back.reg registry file. 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 and OS/390, see Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390.

To verify network connectivity for the Siebel Server

1. Verify network connectivity to the Siebel Gateway Name Server and Siebel Database Server 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 to the Siebel Database Server and Siebel Gateway Name Server.

2. Verify connectivity to the Siebel Database Server:
   • Oracle. Use the tnsping utility and Net8 or 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 Windows and UNIX. Open a db2 command window to make sure that you can connect to your database.

     Be sure to use the Command Window for this procedure and not the Command Line Processor window that appears directly above it. The Command Line Processor window looks similar to a Command Window, but it uses slightly different syntax. For this procedure, the commands will not work in a Command Line Processor window; they must be issued in a Command Window.

   1. Choose Start > Programs > (IBM DB2) > 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 appropriate password for that user_ID is in the preceding example

   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 file system.

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

4. Verify that the 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.