Upgrade to Vault Workgroup 2014 - Clients unable to obtain license

[Anonymous]

I've upgraded our license server with all our 2014 Subscription licenses, all generated on the same date as suggested. I've also run my combined license file thru the License Parser on the Up and Ready Blog. It all appears to be correct. Upgraded ADMS, both clients and server are running Workgroup Build 18.1.8.0 Update 1.

All my other 2014  subscriptions (Product Design Suite Ultimate, Premium & Standard) are working fine.

Problem is when I start Vault Workgroup Clients I get a failed to acquire license error as shown in attached screen shot.

Any ideas. I am stumped.

[TravisNave]

Vault is generally the most affected by IPv6 licensing issues.  Fortunately, it is easy to correct. 

For more information about Network License Manager connectivity issues and IPv6, please see my discussion post here:

http://forums.autodesk.com/t5/Installation-Licensing/Network-License-Error-1-5-15-and-IPv6/td-p/2982...

It's a good start.  Good luck!

[Anonymous]

Thanks Travis,

Read thru the post you provided. I don't think it's any of that. Every program in all 3 Product Design Suites can find license just fine. It's only Vault Workgroup 2014 that has an issue.Plus it all worked fine with Vault Workgroup 2013.IPv6 has been disabled for a while now.

[TravisNave]

Even with it disabled, it is good to check by PING, especially if the
license is on each individual client. Even with IPv6 off, localhost will
PING back as ::1 instead of 127.0.0.1.

[Anonymous]

It's a network license. LMTools does display they are being servers. A PING to my sername "dsi-pc865" results in the following:

Pinging dsi-pc865.DSIDSC.local [10.10.170.78] with 32 bytes of data:
Reply from 10.10.170.78: bytes=32 time<1ms TTL=128
Reply from 10.10.170.78: bytes=32 time=1ms TTL=128
Reply from 10.10.170.78: bytes=32 time<1ms TTL=128
Reply from 10.10.170.78: bytes=32 time=1ms TTL=128

Ping statistics for 10.10.170.78:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

[Anonymous]

Ping on the server to localhost:

Reply from ::1: time<ms

I believe that is NOT correct.

[TravisNave · Accepted solution]

Ah, there you go. If the ADMS is on the same as the License Manager, then
that will absolutely be the problem. The server gets the license, not the
client.

[Anonymous]

Success. Edited the hosts file on ADMS/license erver as recommended below and just like that I'm in. 

Thanks Travis for walking me thru this!

[TravisNave]

Awesome.  That's what I like to see!