<< Client/Server Configuration - LAN Manager networks or Windows for Workgroups | Client/Server Configuration - Enable networking on NetBIOS host >>
Client/Server Configuration - Enable networking on IPX/SPX host
<< Client/Server Configuration - LAN Manager networks or Windows for Workgroups | Client/Server Configuration - Enable networking on NetBIOS host >>
provide SilkTest with both the hardware address and a unique Agent name.
To do this, enter the hardware address and the Agent name into the [Network]
section of the Agent's partner.ini file as shown in this example:
protocols) and SilkTest will use that host name to map to the hardware
address. When selecting the host name for each Agent, take care that it is not
the same as any of the other options in the [Network] section. Using a prefix
like "IPX" is one way to do this.
Agent
protocol type in the Agent window (this operation was described in "One or
more remote applications" on page 355). When you select IPX/SPX as the
protocol, the Machine Name field is disabled. Click OK.
IPX/SPX host
all the Agents, you can enable networking on the host. Do this by selecting
Options/Runtime and selecting the IPX/SPX network type. Then fill in the
Agent name if you have a single-remote-application configuration.
control panel, you must have NetBEUI set as the default protocol.
hardware, before you specify the network type in the Runtime Options
dialog. In Windows NT, Windows 95, and Windows for WorkGroups,
NetBIOS is started automatically.
SilkTest can identify the Agent when your testcase issues a Connect function
for that machine. This step is not necessary for Agents using TCP/IP because
SilkTest automatically uses the workstation's TCP/IP name.
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, you could call the Agent
Rome_QAP.)