Installation & Licensing

Reply
*Domínguez, José Israel Camper
Message 1 of 3 (76 Views)

Mechanical Network Problem.

76 Views, 2 Replies
05-23-2000 06:15 PM
Hi.

We reinstalled the adlm at the server, an IBM netfinity 5500, but the
mechanical client still can't get the authorization. After that, we
installed mechanical client at the adlm server but it didn't work
either.

At the adlm.log appears:
(EDITED FOR SECURITY)

Even though we set the ACADSERVER environment variable, the mechanical
client did'nt work at none of the machines; the variable
was settled like @system00.

They are using different protocols in the network:
DLC Protocol
NetBEUI protocol
NWLink IPX/SPX Compatible Transport
NWLink NetBIOS
TCP/IP Protocol

The machine is DHCP Server and PDC.

Also, the start time and the zombie timeout are 180 seconds and
verbosity is 9.

Thanks.
*milana, jerry
Message 2 of 3 (76 Views)

Re: Mechanical Network Problem.

05-26-2000 11:46 AM in reply to: *Domínguez, José Israel Camper
The first thing to do is make sure that TCP/IP is the primary protocol of
the AdLM server and all workstations. If your protocols are prioritized in
the order you list them in this posting, this will cause a problem. After
you have adjusted protocol priority, reapply your operating system service
pack. Then try again.

Please do nor post your messages multiple times any more.

Jerry Milana,
Autodesk Product Support

"J.I. Campero" wrote in message
news:392C2398.2653DFEC@dasoftmx.com...
>
> Hi.
> We reinstalled the adlm at the server, an IBM netfinity 5500, but the
> mechanical client still can't get the authorization. After that, we
> installed
> mechanical client at the adlm server but it didn't work either.
> At the adlm.log appears:
> 00-May-23 16:37:52: MX00238@system00 [0]: system00 lastping=959096255
> (UP).
> 00-May-23 16:37:52: MX00238@system00 [0]: RECV #1 RQ w.
> 00-May-23 16:37:52: MX00238@system00 [0]: Keydir set to E:\ADLM\KEY.
> 00-May-23 16:37:52: MX00238@system00 [0]: SEND #1 RP w SAR L 0
> TL 163.
> 00-May-23 16:37:52: MX00238@system00 [0]: -------------- LISTEN
> --------------.
> 00-May-23 16:37:52: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:37:52: MX00238@system00 [0]: Packet from 10.91.1.1 (Local).
>
> 00-May-23 16:37:52: MX00238@system00 [0]: RECV #1 RQ w.
> 00-May-23 16:37:52: MX00238@system00 [0]: Keydir set to E:\ADLM\KEY.
> 00-May-23 16:37:52: MX00238@system00 [0]: SEND #1 RP w SAR L 0
> TL 163.
> 00-May-23 16:37:52: MX00238@system00 [0]: -------------- LISTEN
> --------------.
> 00-May-23 16:37:52: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:37:52: MX00238@system00 [0]: Packet from 10.91.1.1 (Local).
>
> 00-May-23 16:37:52: MX00238@system00 [0]: RECV #1 RQ w.
> 00-May-23 16:37:52: MX00238@system00 [0]: Keydir set to E:\ADLM\KEY.
> 00-May-23 16:37:52: MX00238@system00 [0]: SEND #1 RP w SAR L 0
> TL 163.
> 00-May-23 16:38:09: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:38:19: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:38:29: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:38:39: MX00238@system00 [0]: BURY_ZOMBIES: Start.
> 00-May-23 16:38:39: MX00238@system00 [0]: BURY_ZOMBIES: Done.
> 00-May-23 16:38:49: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:38:59: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:39:09: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:39:19: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:39:29: MX00238@system00 [0]: bury_zombies: Too soon for
> next cleanup.
> 00-May-23 16:39:39: MX00238@system00 [0]: BURY_ZOMBIES: Start.
> 00-May-23 16:39:39: MX00238@system00 [0]: BURY_ZOMBIES: Done.
> Even though we set the ACADSERVER environment variable, the mechanical
> client did'nt work at none of the machines; the variable
> was settled like @system00.
> They are using different protocols in the network:
> DLC Protocol
> NetBEUI protocol
> NWLink IPX/SPX Compatible Transport
> NWLink NetBIOS
> TCP/IP Protocol
>
> The machine is DHCP Server and PDC.
>
> Also, the start time and the zombie timeout are 180 seconds and
> verbosity
> is 9.
> Thanks.
*milana, jerry
Message 3 of 3 (76 Views)

Re: Mechanical Network Problem.

06-16-2000 12:10 PM in reply to: *Domínguez, José Israel Camper
Jose,

As I have replied to your message on this site before, TCP/IP should be the
primary protocol of your AutoCAD systems and license server, if your
protocol priorities are set in the order of the list stated in this message,
problems are expected.
Also, please do not post parts of your log file on the news group, as it is
possible to expose undesired information about your network. In this case
the log information you include is not sufficient to analyze what may be
going wrong anyway. Try setting TCP/IP as your primary protocol, if that
does not help, I suggest you contact your MDT dealer. They can contact
Autodesk Product Support directly who will provide instructions on how to
create a log file with sufficient data for analysis and forward the log to
Autodesk.

Jerry Milana,
Autodesk Product Support

"José Israel Campero Domínguez" wrote in message
news:392B2D14.951F27B7@dasoftmx.com...
> Hi.
>
> We reinstalled the adlm at the server, an IBM netfinity 5500, but the
> mechanical client still can't get the authorization. After that, we
> installed mechanical client at the adlm server but it didn't work
> either.
>
> At the adlm.log appears:
>

>
> Even though we set the ACADSERVER environment variable, the mechanical
> client did'nt work at none of the machines; the variable
> was settled like @system00.
>
> They are using different protocols in the network:
> DLC Protocol
> NetBEUI protocol
> NWLink IPX/SPX Compatible Transport
> NWLink NetBIOS
> TCP/IP Protocol
>
> The machine is DHCP Server and PDC.
>
> Also, the start time and the zombie timeout are 180 seconds and
> verbosity is 9.
>
> 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