<< Client/Server Configuration - Enable networking on Agent | 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 Agent | Client/Server Configuration - Enable networking on IPX/SPX host >>
licenses
because SilkTest has started up an unplanned Agent on the local workstation.
If you do not want to use the local workstation as a test machine, set the
Runtime Options dialog's Agent Name field to "(none)" instead of "(local)."
This will free up one license for a remote Agent.
Workgroups...
increase the SESSIONS value (the default is 6) to a higher value. This
variable is defined in the protocol.ini file, which is normally located in your
Windows directory. You should also increase the NCBS value in protocol.ini
to twice the SESSIONS value.
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 SilkTest 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 would (as
always) be 0 (zero), and that for TCP/IP would be 1 (one).
all of the Agents and SilkTest are running on 16-bit PCs and they are running
some kind of Novell network software, such as Netware or Personal Netware,
that can use IPX/SPX as the communications protocol.
because host names do not exist on a Novell network. This address is a string
of 20 hexadecimal digits, usually written in this format:
local area network. The last six bytes are the host address. You can find the
host address by means of the Netware Diagnostics program, or by asking
your system manager.