![Autodesk Combustion 4 discreet Network Manual Download Page 35](http://html1.mh-extra.com/html/autodesk/combustion-4-discreet/combustion-4-discreet_network-manual_3021206035.webp)
Troubleshooting Problems
31
❚❘❘
Configure TCP/IP before proceeding, then follow
the steps in
The AdLM runs diagnostics and then goes online.
The diagnostics may take as long as three minutes to
run. When the network version of
combustion
is
started on a workstation,
combustion
responds by
first sending a broadcast to the local network
segment to look for a license server with a free
combustion
license. If a license server is found, a
license is checked out from the server, and
combustion
will start on the workstation. If a
license server resides in a different network segment
from the workstation, the license server will not be
found unless the ACADSERVER environment
variable is set to include the license server’s
hostname on each
combustion
workstation. A
workstation may be restricted to pulling licenses
from specific license servers by the prefix symbol @
to the hostname listed in the ACADSERVER value.
Using the @ symbol effectively disables the
broadcast method of finding a license server.
Following are potential problems that can occur and
their solutions:
•
The License Manager Service does not start.
•
AdLM will not issue licenses for three minutes after
startup.
•
AdLM is running but combustion cannot find a
license server.
Cause
Solution
The AdLM is run
on the wrong
platform.
The AdLM requires Windows 2000 or
Windows NT running on an AMD or
Intel-compatible processor running
300 MHz or higher.
Microsoft TCP/IP
is not installed or
is improperly
configured.
The AdLM requires TCP/IP to operate.
Verify the TCP/IP configuration by
using the PING command at a DOS
command prompt.
The AdLM was not
launched from
the Start/ Stop/
Reread panel of
lmtools.exe.
Start lmtools.exe, go to the Start/Stop/
Reread tab, and press “Start server”.
Cause
Solution
The default diag-
nostic time set-
ting for the AdLM
is three minutes; it
does not issue li-
censes during this
time.
This is normal operation. While it is
possible to set the diagnostic time to a
shorter time period, Discreet does not
recommend it.
Cause
Solution
TCP/IP name reso-
lution is not con-
figured.
Try using the PING command at a DOS
prompt. The syntax of the PING
command is ping <hostname>. If you
cannot successfully "ping" the license
server from a
combustion
workstation
and "ping" the workstation from the
license server, the AdLM will not work.
Name resolution may be accomplished
in a variety of ways on a Microsoft TCP/
IP network. The simplest method to
provide name resolution is to create a
hosts file with entries for all
workstations on the network, and copy
it to the \winnt\system32\drivers\etc
folder on Windows 2000 and NT
systems. Windows 2000 and Windows
NT come with a sample hosts file
located in the proper destination folder
for that operating system.
The system date
and time are in-
correct.
Verify that the date and time are correct
on all workstations, and that they are
synchronized with the AdLM station.
The AdLM will not issue a license to a
workstation that has an invalid date.
The license server
is in a different
subnet from the
workstation.
Set the ACADSERVER environment vari-
able value to contain the hostname of
the license server so that
combustion
can connect to a license server on
another subnet. To set ACADSERVER to
multiple license servers, separate each
hostname with a semicolon. Consult
your operating system documentation
on how to properly set an environment
variable. The value of an environment
variable can be confirmed by typing set
|more at a DOS command prompt.
Summary of Contents for Combustion 4 discreet
Page 1: ...del 11 March 2005...
Page 5: ...1 R e q u i r e m e n t s Summary System Requirements 2 Network Installation Components 3...
Page 16: ...Network Planning Concepts 2 12...
Page 17: ...13 Installation Summary FLEXlm 14 Setting up the Network 14 Silently Installing combustion 15...
Page 22: ...Installation 3 18...
Page 26: ...License Server Configuration 4 22...
Page 30: ...Administration 5 26...
Page 38: ...Networking Quick Start and Troubleshooting 6 34...
Page 39: ...35 G l o s s a r y...