I had to do a reinstall of my network server. When I did this last it took a while to learn that there are two ports that need to be opened in the firewall. Does anybody know which ones?
Also, where do people typically keep their license text file that the server reads?
Eric,
Here's one way: we use this process for all of our Flexlm license servers, so it may not be the approved Solidworks way.
We don't use the SW port defaults; I forget what they are (ah, 3123, and something else, looks like).
We use ports 27001 and 27002, which are typical Flexlm ports.
To use ports 27001 and 27002 (assuming no other application on your license server needs these ports; otherwise use 27003 and 27004, etc.)
a. Edit your license file so that the first few lines look something like:
#
# USB dongle FLEXID: FLEXID=9-1z223456
#
SERVER server19 FLEXID=9-1z223456 27001
VENDOR SW_D port=27002
USE_SERVER
#
Subsitute your server name, and dongle ID.
Note that the '#' character is a comment character, in Flexlm license file syntax.
Oh yeah: don't use Word or Wordpad for your editor -- use something dumb like Notepad so you don't get any special smart characters and reformatting in the revised license file -- that is really hard to troubleshoot when it happens.
b. Change your license server firewall exceptions to include TCP ports 27001 and 27002:
(Win XP and Server 2003 syntax here, not sure about Vista or Server 2008):
Add port / Port name: Flexlm_27001 / Port number: 27001 / TCP
Add port / Port name: Flexlm_27002 / Port number: 27002 / TCP
Edit the 'scope' settings for each exception if you need to restrict the license access to your subnet.
c. That should work OK on the license server; on client systems:
Client systems should not need to add any firewall port exceptions, if all you use is Windows Firewall on those.
You will likely need to revise the server settings on your client systems 'SolidNetwork License Administrator' settings to reflect the new server name, and the new port number:
Whichever port number is listed on the license file 'SERVER' line is the one to use here.
For the example above, the client system server setting would be '27001@server19'
--
Location of the license file: we just use the location that the SW installer puts it in.
--
More info:
1. If you use the Flexlm 'lmtools' program, then for the 'Config Services' tab, under 'Path to the debug log file':
I usually preface the path name with a '+', so that the string looks like (without the quotes):
'+C:\Flexlm_logs\Flexlm_solidworks.log'
The '+' character tells Flexlm to 'append to' the log file, instead of erasing the old info and starting from scratch, each time the system restarts.
This prevents the 'View log' button from working inside the lmtools application, but you can view the file using any editor, if you know its location.
If you use the lmtools program, remember to click the 'Save settings' button on the 'Config Services' page if you make any changes.
2. The Flexlm program 'lmutil' can let you test access to the license server from another system, once you think you have the license server set up (it's command-line only, so open a command window in the folder where you have the lmutil.exe program stored, and do):
'lmutil lmstat -a -c 27001@server19 ' without the quotes and the handy blue underline.
3. The Flexlm utility programs can be downloaded at no charge from whoever owns the Flexlm software these days.
Here's a link that probably will work, scroll down to find the Windows versions:
http://www.globes.com/support/fnp_utilities_download.htm
4. Troubleshooting:
If something is wrong, look first at the debug log file to see if there's an error message.
The first few lines after the restart messages in the log file will tell you which ports the license server thinks it's using.
Use the 'lmutil lmstat' command as above from a command window on the license server itself -- if it looks good to you, then the license server software for Soldiworks is probably running OK.
Use the 'lmutil lmstat' command as above on a client system: if it worked OK on the license server itself, but not on the client system: then you probably have a firewall problem somewhere on your network -- but look first at the license server itself, and review the firewall exceptions to make sure they match the license file.
Regards, Tom