Extreme Lag Inside Mastercam on Net-Hasp

[betts]

This started last week, about Thursday.  Anytime you invoke a command that (presumably) cause Mastercam to page out to the Net-Hasp there is lag, extreme lag.  The screen will haze out, or plain wait for "file open", or right click in the ops manager.

 

We have not had this problem, or it has been really rare and isolated and we have been on Net-Hasp (offsite) for months.  Now this issue going on for a week and getting worse is everybody, though only five are working today.

 

IT guy says he has been monitoring network traffic and it isn't showing overloaded.

 

Anybody experience this or have any guesses??

[Allan]

Since you say it started last Thursday, and there have been no updates since then, I can assume that nothing has changed software wise.

 

You also mention the HetHASP is offsite, so the network between the 2 locations would be my first suspect.

Check the connection statistics using a tracert command, your IT guy should be able to accomplish this.

I would not be supprised if you will see response times in the 150+ms.

The NetHASP default settings in Mastercam use the UDP protocol.

Conjested networks will drop UDP packets to save bandwidth, TCP connection may prove more reliable.

 

 

HTH

 

Allan

[betts]

Thanks Allan.  Turns out some people "had a bunch of things hosed up" at one of our main locations.  A new firewall was rolled out and some internal things fixed.  Today seems much better so I hope it sticks.

[dan.w]

Hi Alan -

 

i was wondering about the network settings you commented on.  We are a multi-site user and one location has  started describing problems.   When i measured the connection it was slightly over 125ms - which didn't seem that bad.   If we wanted to try using the TCP protocol - do we only have to modify the .ini file in the local computers, or does it also require changes on the license server. 

 

Thanks,

Dan

[huskermcdoogle]

If I recall correctly, changing protocols for us back when I was on a nethasp made things significantly faster, still had a little lag, but it was manageable instead of frustratingly slow.

[Fred @ Slate Industries]

I recall everything that moved on the network had to loaded (Temp) and then sniffed for trouble at on place I worked.

That was the killer.

FIX = Backed up to the network after that but worked straight off my HD from then on out.

[Allan]

Hi Alan -

 

i was wondering about the network settings you commented on.  We are a multi-site user and one location has  started describing problems.   When i measured the connection it was slightly over 125ms - which didn't seem that bad.   If we wanted to try using the TCP protocol - do we only have to modify the .ini file in the local computers, or does it also require changes on the license server. 

 

Thanks,

Dan

The .ini files on server as well as the client machines need to change.

The service on the NetHASP server will also need to be stopped and restarted to take the settings change.

 

Allan