We have had two ongoing problems that I think are network latency issues at their root. One is that AutoCAD will often claim there is no license server, requiring a user to type in the license server name (twice, thank you Autodesk 
) before they can get a license. Also, we are seeing what seems like a pretty high incidence of corrupt central files, which I believe can be triggered by excessive latency. I can fix the first problem by using the kludge of setting the FLEXLM_TIMEOUT environment variable to a high value, as you would when accessing a license server over a WAN. Which certainly says to me that the acad problem is truly a latency issue.
We are on a gigabit network, but with a long run to the server room in the basement, as well as a network infrastructure that isn't necessarily tuned for Revit use. So I am looking for some insight into just what "excessive" network latency would be. If there is some threshold value beyond which problems are known to arise, I can perhaps get IT to test our latency and show that we have a systemic problem. Or not.
Anyone have any data on the topic?
Thanks!
Gordon
) before they can get a license. Also, we are seeing what seems like a pretty high incidence of corrupt central files, which I believe can be triggered by excessive latency. I can fix the first problem by using the kludge of setting the FLEXLM_TIMEOUT environment variable to a high value, as you would when accessing a license server over a WAN. Which certainly says to me that the acad problem is truly a latency issue.We are on a gigabit network, but with a long run to the server room in the basement, as well as a network infrastructure that isn't necessarily tuned for Revit use. So I am looking for some insight into just what "excessive" network latency would be. If there is some threshold value beyond which problems are known to arise, I can perhaps get IT to test our latency and show that we have a systemic problem. Or not.
Anyone have any data on the topic?
Thanks!
Gordon
Comment