Dan -
ACADSERVER doesn't work with the flexlm. That variable is only for the elan adlm. Anything you do with it won't get you anywhere.
In the licepath.lic file you should have something like
SERVER servername 0391A97EB07C
USE_SERVER
Notice that the ethernet address of the server has exactly 12 digits, no dashes (a number of people have dashes in theirs, and it
doesn't work). The actual number that is there doesn't matters as long as it is a 12 digit hexadecimal value (It does have to be
there). Please make sure that you don't have any dashes in the licepath.lic file.
If you can't get the licepath.lic file to work you might try the lm_license_file variable (rather than the acadserver variable). Set
it in the same way as you would the ACADSERVER variable (9x, in autoexec, NT in environmental variables) and set it to the host name
of the acad server (I actually set mine to @servername, it's different that the acadserver variable in that the @ doesn't specify
only that server, but you can put a port setting in front of the @).
Yes SP2 for win2k "fixes" the problem with the license finder sticking to the back of the acad window "in most cases" (there are
still some problems in some environments, but odds are that sp2 for w2k will fix the license finder problem).
A good way to check the port connectivity is to telenet into the ports that you need from the clients. To make sure that the ports
are open telenet into the server at ports 27000 (default FlexLM port) and 2080 (adeskflex port). I have no idea what to type there,
but if the connection isn't refused then you have the port connectivity that you need.
Yes, there is a newer build of the lmgrd than 7.1, but Autodesk hasn't recommended that anyone upgrade yet. I'd stick with the
shipping version for now, especially since you seem to be having trouble with it. Upgrading would likely just cause more
troubleshooting problems.
Please post back if none of that works.
hth
jason martin
frankfurt-short-bruza
"dan_wilk" wrote in message news:f09da8b.-1@WebX.maYIadrTaRb...
> I have several clients where we have deployed flex ADLM accros their
> site
> 2 are running 3rd party networks (UNIX and Novell 5) TCP/IP is the
> primary protocol
> and licence servers are on NT 4 server and 2000 server, another site is all NT environment with Win98 and 2000 clients
>
> one site is using windows 98 SE for clients the other is using 2000 pro
> or NT4 workstation for clients
>
> The problem is that when the client fires up Autocad or map etc they get
> the dialog box prompting for a server Every time, then type in the
> server name and they get the licence
> but this happens every time the client opens the program.
>
> I have tried adding ACADSERVER=[SERVER_NAME] to the autoexec.bat on the
> win98 clients and have no joy I have also tried
> ACADSERVER=@[SERVER_NAME].... no joy
>
> on the 2000 and NT4 clients I have added the envronment variable
> ACADSERVER=[SERVER_NAME] and also ACADSERVER=@[SERVER_NAME]
> no joy either
>
> nothing looks untoward with the LICPATH.LIC files either. I am really stumped with this because that
> window looking for the licencing server is actually showing up on the
> 2000 boxes!!!! (remember it used to snap to the back of
> the autocad window, could this be to do with SP2 for Win2K?)
>
> none of these seem to have had any effect.
>
> the only thing i can think of is that 2 installs had problems
>
> one site's server lost a couple of hard drives and so was re-installed
> (don't know if this has anything to do with it)
>
> the other had an incorrect .LIC file issued due to a typo in the licence
> request. I just had a new LIC file issued from sinagapore and all fired
> up again.
>
> however the 3rd and most recent site went fine and this problem is recuring
>
> All clients can see the Licence server by browsing the network. Ping by hostname is ok
> and the ports seem unobstruced
> (however none can access it directly due to permissions restrictions (This
> shouldn't have any effect should it?)
>
> It looks like these FlexLM are running version 7.1 Is this a newer build? (I think it might be)
> and therefore is this an introduced bug as none of the older installs are doing this?
> HELP!!!!!!
>
> Thanks from Dan
>
>
