Configuring Your Test Environment (Classic Agent)

This functionality is supported only if you are using the Classic Agent.

This topic contains information about configuration tasks that you can perform on your test environment to test on multiple machines with the Classic Agent.

When you are working with ...
Configure the following ...
PC-Class Platforms
Explicitly assign a unique network name to remote agents so that Silk Test Classic can identify the agent when your test case connects to that machine.
TCP/IP
On PCs. Windows machines generally come with TCP/IP. Silk Test Classic on Microsoft Windows can use any TCP/IP software package that supports the Windows Sockets Interface Standard, Version 1.1, (WINSOCK), and supplies WINSOCK.DLL.
LAN Manager or Windows for Workgroups
  • Increase the SESSIONS value, the default is 6, to a higher value. This variable is defined in the protocol.ini file, which is typically located in your Windows directory.
  • Increase the NCBS value in protocol.ini to twice the SESSIONS value.
  • The LAN Manager network environment and Windows for Workgroups have the ability to use more than one protocol driver at a time. NetBEUI is the protocol driver frequently used by LAN Manager. In order for Silk Test Classic and the agent to run, the NetBEUI protocol must be the first protocol loaded. The LANABASE option under the [NETBEUI_XIF] section of protocol.ini must be set to 0 (zero). If additional protocols are loaded, they must have a sequentially higher LANABASE setting. For example, if you are running both NetBEUI and TCP/IP, the LANABASE setting for NetBEUI is (as always) 0 (zero), and the value for TCP/IP is1 (one).
NetBIOS on PCs
  • Under Windows, install NetBEUI with NetBIOS.
  • In the Network control panel, set NetBEUI as the default protocol.
  • On Windows, NetBIOS is started automatically.
  • Explicitly assign a unique network name to remote agents so that Silk Test Classic can identify the agent when your test case issues a Connect function for that machine. This step is not necessary for agents using TCP/IP because Silk Test Classic automatically uses the workstation’s TCP/IP name. The name must be from 1 to 16 alphanumeric characters long and must not be the standard name you use for your machine itself or the name of any other distributed agent. On some systems, using the same name can cause a system crash. A safe alternative is to derive the agent name from the machine name. For example, if a machine is called Rome, call the Agent Rome_QAP.
  • Your NetBIOS adapter may be configured as any host adapter number, including adapter 0. Check with your network administrator if you are not sure how to do this or need to change your configuration.