I have a strange occurrence happening that I was looking for some info on. I know what causes this error. The client times out when trying to communicate with the server, and produces this error. I already have the "fix" for the problem, but I want to solve the problem, not just patch it with a environmental variable to increase the time out period.
Here is what throws me for a loop. If the computer next to this computer is not currently connected to AutoCAD... it works fine. Once that OTHER computer loads AutoCAD and receives a license, it takes forever for the computer in question to get a license. Same also works in the opposite direction. If the computer in question is connected, the computer next to it takes forever to get a license.
What would cause this behavior? Physically these computers are connected to a switch, and no other cluster of computers has this issue. Only these two computers behave in this fashion.
What is the OS of the license server and what is the version of the license manager as well as the product that you are using?
Thank you for the reply.
Our License Server is running Windows Server 2008, and we are using LMTOOLs V184.108.40.206 Build 87342 x64 n6.
We are using AutoCAD 2013 Design Suite on the client machines.
My only thought is that I've seen the NLM have problems on Server 2008 with release 11.9 and 11.10. You might consider 11.7 as a test just to see if the problem goes away. I've had complete success with that version in every instance where the later versions caused problems on Server 2008.
Also ensure that the connection from the workstation to the server is using IPv4. You can verify with a PING.
I actually found your other post about updating the NLM to a version that 2013 supports. That may fix the issue, I will let you know if it does (but could you respond to that other post about the procedure?).
I do believe we run IP4 as ipconfig - all has no indication of IP6 being used.
Thank you for your assistance.
Using 11.7 did not resolve the latency issues with that particular machine.
The user is not happy with the delay, but it works so I can live with it for now.
Thank you anyway.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register