Installation & Licensing

Reply
Contributor
merlin25
Posts: 11
Registered: ‎08-20-2001
Message 1 of 3 (90 Views)

Network Liscence Fails in remote office

90 Views, 2 Replies
11-27-2000 08:39 AM
We have 2 offices. In the main office we have a computer designated without a static ip address that has the ADLM installed. It works fine in the main office for all to connect. In the other office it connect with the ACAD Variable connecting to the computer name solely allowing WINS to resolve the address. The first time each computer in this other office attempts to connect it gives the msg it cannot find the ADLM or assign liscence. But if you open the program a second time it then works. I have tried adjusting the timeout variable and that does not work.

We currently have 48 liscences to AD2000. We have designated a non server computer at this time and not a main server due to network congestion. Can anyone tell me what kind of Network congestion I can estimate for 48 Liscenses connecting to it. It is my understanding that a network liscence will ping that computer at a minimum every 6 minutes. Is that correct?

I would like to move the ADLM to one of our main servers that has a static IP address which I think could resolve the timeout issues in the other office the first time the program is opened becaue it would no longer need to rely on WINS to resolve it's location.

Also, on a non patterend scenario it seems as though the other office about 1 time a week will start failing to connect to the ADLM all togather. The oly solution has been to Reboot the ADLM. Will moving the ADLM to the main server resolve this problem? could the Setting for the ACADSERVER Variable be incorrect? The ACAD SErver Variable is currently configured to find the name of that computer and not it's IP.

Currently we run NT 4.0 Servers. The ADLM is on NT 4.0 Workstation. All 48 CAd stations run NT 4.0. The 2 office are on different subnets.

Any suggesttions or adives would be great.

THANKS!!!

Merlin
*Lawson, Robert
Message 2 of 3 (90 Views)

Re: Network Liscence Fails in remote office

11-28-2000 05:30 AM in reply to: merlin25
What if you loaded the ADLM on three machines? This might help availability,
and add some fault tolerance. Another benefit of going static IP is you can
use the IP address in lieu of the computer name in the ACADSERVER
environment variable. This probably saves a trip to the WINS server and
whatever traffic that is, plus may help since you have two subnets.

"merlin25" wrote in message
news:ef54406.-1@WebX.SaUCah8kaAW...
We have 2 offices. In the main office we have a computer designated without
a static ip address that has the ADLM installed. It works fine in the main
office for all to connect. In the other office it connect with the ACAD
Variable connecting to the computer name solely allowing WINS to resolve the
address. The first time each computer in this other office attempts to
connect it gives the msg it cannot find the ADLM or assign liscence. But if
you open the program a second time it then works. I have tried adjusting the
timeout variable and that does not work.
We currently have 48 liscences to AD2000. We have designated a non server
computer at this time and not a main server due to network congestion. Can
anyone tell me what kind of Network congestion I can estimate for 48
Liscenses connecting to it. It is my understanding that a network liscence
will ping that computer at a minimum every 6 minutes. Is that correct?
I would like to move the ADLM to one of our main servers that has a static
IP address which I think could resolve the timeout issues in the other
office the first time the program is opened becaue it would no longer need
to rely on WINS to resolve it's location.
Also, on a non patterend scenario it seems as though the other office about
1 time a week will start failing to connect to the ADLM all togather. The
oly solution has been to Reboot the ADLM. Will moving the ADLM to the main
server resolve this problem? could the Setting for the ACADSERVER Variable
be incorrect? The ACAD SErver Variable is currently configured to find the
name of that computer and not it's IP.
Currently we run NT 4.0 Servers. The ADLM is on NT 4.0 Workstation. All 48
CAd stations run NT 4.0. The 2 office are on different subnets.
Any suggesttions or adives would be great.
THANKS!!!
Merlin
*milana, jerry
Message 3 of 3 (90 Views)

Re:

12-05-2000 10:07 AM in reply to: merlin25
You should not use an IP address in the ACADSERVER value! Doing so is not
supported by Autodesk and in most networks will not work. Make sure that
you are setting the ACADSERVER value to the correct case as the wrong case
has been known to cause problems similar to what you describe. For example,
if your server hostname is "paradise", setting ACADSERVER to PARADISE would
cause problems. Don't confuse the NetBios Machine Name with the hostname.
The first is always set to upper case and the hostname by convention, should
be lower case. Best way to check is to look at the server's adlm.log file.
You will find a line that tells you the name of the system it has started on
(just search the log file for the word "started").

jerry milana,
Autodesk Product Support

"Robert Lawson" wrote in message
news:EAFDD9F52EE80BD88037EE085499BB1A@in.WebX.SaUCah8kaAW...
> What if you loaded the ADLM on three machines? This might help
availability,
> and add some fault tolerance. Another benefit of going static IP is you
can
> use the IP address in lieu of the computer name in the ACADSERVER
> environment variable. This probably saves a trip to the WINS server and
> whatever traffic that is, plus may help since you have two subnets.
>
> "merlin25" wrote in message
> news:ef54406.-1@WebX.SaUCah8kaAW...
> We have 2 offices. In the main office we have a computer designated
without
> a static ip address that has the ADLM installed. It works fine in the main
> office for all to connect. In the other office it connect with the ACAD
> Variable connecting to the computer name solely allowing WINS to resolve
the
> address. The first time each computer in this other office attempts to
> connect it gives the msg it cannot find the ADLM or assign liscence. But
if
> you open the program a second time it then works. I have tried adjusting
the
> timeout variable and that does not work.
> We currently have 48 liscences to AD2000. We have designated a non server
> computer at this time and not a main server due to network congestion. Can
> anyone tell me what kind of Network congestion I can estimate for 48
> Liscenses connecting to it. It is my understanding that a network liscence
> will ping that computer at a minimum every 6 minutes. Is that correct?
> I would like to move the ADLM to one of our main servers that has a static
> IP address which I think could resolve the timeout issues in the other
> office the first time the program is opened becaue it would no longer need
> to rely on WINS to resolve it's location.
> Also, on a non patterend scenario it seems as though the other office
about
> 1 time a week will start failing to connect to the ADLM all togather. The
> oly solution has been to Reboot the ADLM. Will moving the ADLM to the main
> server resolve this problem? could the Setting for the ACADSERVER Variable
> be incorrect? The ACAD SErver Variable is currently configured to find the
> name of that computer and not it's IP.
> Currently we run NT 4.0 Servers. The ADLM is on NT 4.0 Workstation. All 48
> CAd stations run NT 4.0. The 2 office are on different subnets.
> Any suggesttions or adives would be great.
> THANKS!!!
> Merlin
>

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
Are you familiar with the Autodesk Expert Elites? The Expert Elite program is made up of customers that help other customers by sharing knowledge and exemplifying an engaging style of collaboration. To learn more, please visit our Expert Elite website.

Need installation help?

Start with some of our most frequented solutions to get help installing your software.

Ask the Community


Up & Ready Blog

Boldly Install, Configure and Deploy Autodesk Software.

AutodeskHelp Blog

Your one-stop shop for the latest solutions, breaking news, and behind the scenes access to the world of Autodesk support.

Connect with Us

Twitter

Pinterest

Blog

Youtube