Installation & Licensing

Reply
*Rauda, Pedro Arenas
Message 1 of 4 (95 Views)

Mecanical Network Installation Support!!!

95 Views, 3 Replies
05-19-2000 12:58 PM
I installed a network version of Mechanical Desktop 4.0, and the ADLM is

working OK, but when I installed a client, the next message appears:

FATAL ERROR: Security system (hardware lock or network license) is
not functioning or is improperly installed.

I set the ACADSERVER and it still is not working.

If I attach a hardware lock it works, but asks for the authorization
code.

This machine is running Windows 98, and it has previusly installed a
stand alone license. I uninstalled it, re-boot the machine, and
installed MDT from the deploymente directory.

I checked the log file, and it appears that the machine requested for
the service, but the server didn't answer.

The Win98 machine is part of a different domain than the server's, but
it has an common account.

What can I do?

The server is runing NT 4.0.

Thanks
*Martin, Jason
Message 2 of 4 (95 Views)

Re: Mecanical Network Installation Support!!!

05-19-2000 12:58 PM in reply to: *Rauda, Pedro Arenas
Is this the first client that's tried to use the ADLM? If so are you sure
that it's working okay? Try installing to another client (if possible).

If other clients can get licenses then make sure that you can ping the adlm
machine by netbios name from the client machine. If TCP/IP doesn't work
then neither will ADLM.

Domain really shouldn't matter as authenication isn't required to grant the
license. Is there a router anywhere between the two machines? Could it be
blocking the authentication?

Sorry these are very generic questions but I need some more details to try
and help.

jason martin
frankfurt-short-bruza

"Pedro Arenas Rauda" wrote in message
news:39259CCC.4B3D5686@dasoftmx.com...
> I installed a network version of Mechanical Desktop 4.0, and the ADLM is
>
> working OK, but when I installed a client, the next message appears:
>
> FATAL ERROR: Security system (hardware lock or network license) is
> not functioning or is improperly installed.
>
> I set the ACADSERVER and it still is not working.
>
> If I attach a hardware lock it works, but asks for the authorization
> code.
>
> This machine is running Windows 98, and it has previusly installed a
> stand alone license. I uninstalled it, re-boot the machine, and
> installed MDT from the deploymente directory.
>
> I checked the log file, and it appears that the machine requested for
> the service, but the server didn't answer.
>
> The Win98 machine is part of a different domain than the server's, but
> it has an common account.
>
> What can I do?
>
> The server is runing NT 4.0.
>
> Thanks
>
*Rauda, Pedro Arenas
Message 3 of 4 (95 Views)

Re:

05-19-2000 01:50 PM in reply to: *Rauda, Pedro Arenas
Hello Jason:

TCP/IP is working fine because the ping test was successfull between the client
and ADLM. Not possible the test in another machine because the contact between
the network admin and me is by telephone.

But, there is a Sysco router between the two machines.

Thanks.

Jason Martin wrote:

> Is this the first client that's tried to use the ADLM? If so are you sure
> that it's working okay? Try installing to another client (if possible).
>
> If other clients can get licenses then make sure that you can ping the adlm
> machine by netbios name from the client machine. If TCP/IP doesn't work
> then neither will ADLM.
>
> Domain really shouldn't matter as authenication isn't required to grant the
> license. Is there a router anywhere between the two machines? Could it be
> blocking the authentication?
>
> Sorry these are very generic questions but I need some more details to try
> and help.
>
> jason martin
> frankfurt-short-bruza
>
> "Pedro Arenas Rauda" wrote in message
> news:39259CCC.4B3D5686@dasoftmx.com...
> > I installed a network version of Mechanical Desktop 4.0, and the ADLM is
> >
> > working OK, but when I installed a client, the next message appears:
> >
> > FATAL ERROR: Security system (hardware lock or network license) is
> > not functioning or is improperly installed.
> >
> > I set the ACADSERVER and it still is not working.
> >
> > If I attach a hardware lock it works, but asks for the authorization
> > code.
> >
> > This machine is running Windows 98, and it has previusly installed a
> > stand alone license. I uninstalled it, re-boot the machine, and
> > installed MDT from the deploymente directory.
> >
> > I checked the log file, and it appears that the machine requested for
> > the service, but the server didn't answer.
> >
> > The Win98 machine is part of a different domain than the server's, but
> > it has an common account.
> >
> > What can I do?
> >
> > The server is runing NT 4.0.
> >
> > Thanks
> >
*milana, jerry
Message 4 of 4 (95 Views)

Re:

05-19-2000 02:39 PM in reply to: *Rauda, Pedro Arenas
Jason,

Thanks for jumping in on this one. I would like to clear up a couple of
points you made:

You should not ping by netbios name, ping should be used with the hostname
of the system. By definition, these are different and by implementation,
usually are, at least case. The netbios name is forced to upper case when
you enter it. When you set up TCP/IP on a Windows system it places the
netbios name, translated to lower case in the hostname field. It is
possible to over ride this and create a hostname completely different from
the netbios name and many people do. In some cases, Windows will create a
hostname that varies by more than case. For example, if the netbios name
contains an underscore (_) it will be translated to a dash (-) in the
hostname field to remain compliant to TCP/IP naming conventions. Since the
hostname value is case sensitive, this is a common point of administration
error. For example, if a system's hostname is "paradise" and ACADSERVER is
set to "@PARADISE" it is very likely that either AutoCAD will not start at
all or will start up slowly and fail occasionally.

Authentication occurs internally at the AdLM server, that function can not
be blocked at a router. What can be blocked is the heart beat between
AutoCAD and AdLM. This heartbeat occurs on udp port 1422 and some routers
are configured to filter such traffic. If a router is filtering udp 1422 in
one or both directions, attempts to start AutoCAD on the remote side of the
router from the AdLM server will fail.

Mr. Rauda,

Please do not post your messages multiple times. This violates the rules of
this discussion forum and most other organizations forums and lists.
Multiple, duplicate posts will most often delay the time frame of a
response, not enhance it. This is because forum participants who are
associated with the sponsoring organization (like myself in this case) will
not jump on the thread until forum moderators have deleted all but one copy
of the posting. This is done to avoid list congestion and assure logical,
contiguous threads. In this case I made an exception because I wanted to
clarify the reply Jason kindly posted. I have asked our moderators to
delete your organization duplicate postings and to be careful not to delete
the copy this thread has started off of.

In addition to the points above, what entry in your log file makes you
think:
> I checked the log file, and it appears that the machine requested for
> the service, but the server didn't answer.?

Also, stop AdLM and set the log file verbosity to 9 then restart AdLM and
wait at least three minutes. Then try to start AutoCAD a couple of times.
Then look in your log file for the hostname of the system trying to start
AutoCAD. If you do not see the hostname, the request is never getting to
the AdLM server, if you do see the hostname, it is likely to tell you why
AdLM is not granting a license.

Jerry Milana,
Autodesk Product Support

"Jason Martin" wrote in message
news:ef0b003.0@WebX.SaUCah8kaAW...
> Is this the first client that's tried to use the ADLM? If so are you sure
> that it's working okay? Try installing to another client (if possible).
>
> If other clients can get licenses then make sure that you can ping the
adlm
> machine by netbios name from the client machine. If TCP/IP doesn't work
> then neither will ADLM.
>
> Domain really shouldn't matter as authenication isn't required to grant
the
> license. Is there a router anywhere between the two machines? Could it
be
> blocking the authentication?
>
> Sorry these are very generic questions but I need some more details to try
> and help.
>
> jason martin
> frankfurt-short-bruza
>
> "Pedro Arenas Rauda" wrote in message
> news:39259CCC.4B3D5686@dasoftmx.com...
> > I installed a network version of Mechanical Desktop 4.0, and the ADLM is
> >
> > working OK, but when I installed a client, the next message appears:
> >
> > FATAL ERROR: Security system (hardware lock or network license) is
> > not functioning or is improperly installed.
> >
> > I set the ACADSERVER and it still is not working.
> >
> > If I attach a hardware lock it works, but asks for the authorization
> > code.
> >
> > This machine is running Windows 98, and it has previusly installed a
> > stand alone license. I uninstalled it, re-boot the machine, and
> > installed MDT from the deploymente directory.
> >
> > I checked the log file, and it appears that the machine requested for
> > the service, but the server didn't answer.
> >
> > The Win98 machine is part of a different domain than the server's, but
> > it has an common account.
> >
> > What can I do?
> >
> > The server is runing NT 4.0.
> >
> > Thanks
> >
>

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