slow nethasp

[Jaz]

We have several MasterCam workstations on a nethasp. As our company has grown the network has become slow and MasterCam's responsiveness has declined. This is particularly noticable when going into toolpaths' parameters to make changes. I am guessing this has something to do with MasterCam checking to see if you have a license available. Does anybody know what can be done to alleviate this click-and-wait scenario?

[Todd Tracey from Fastech]

Do you have a custom ini file in use? If not, contact your dealer for Aladdin DiagnostiX to create a custom ini file. See if that helps. I use that on all NetHASP installs that I do.

 

Back up your old ini file before overwriting!

 

Makes life a more simple for me later.

JM2C

[Jaz]

We are using a customized ini file to direct license queries to a specific address.

[iowajim62]

quote:

---

As our company has grown the network has become slow and MasterCam's responsiveness has declined

---

Is the server only used for Mcam ? Prolly not.

I would suggest a separate server just for Mastercam.

jm2c

[Todd Tracey from Fastech]

A license server doesn't even need to be 'Server'. It can be a PC on the network usually in a more secure area to protect loss of the HASP. If the network itself is getting overloaded,or you are trying to read and write code to a network location instead of local, you might just be running out of system HP. I had a school with similar issues but they were buried under about 6 or 7 subnets. Put the key on the teacher's PC and fixed the issue.

[Jaz]

The key is on its own PC server. I believe that the network is simply overloaded and can't route requests qiickly enough. I have heard that upgrades for the network are in the works but what has happened in the past is any upgrade would have been adequate a year ago when it was first requested. I will investigate the possibility of MasterCam looking for other information (tool libraries).