I had ADLM running on a Netware 4.11 fileserver running fine. This past weekend we upgrade the OS to Netware 5.0, we used Netwares utility to migrate the data and all has worked fine, except for the ADLM. Any idea's?
First let me remind you that the ADLM is specifically written for WIN9x, NT4, and Novell 3.12 and 4.x both with Netware Client 32. Any other OS is not supported including NW 5, and especially the tcp/ip version of NW5.
This version binds tcp in a different way than Microsoft's way of binding tcp and that causes most of your problems. If you are running NW5 with tcp/ip then you might get it to run by reinstalling the ADLM for ipx and
re-authorizing. Again, NW5 is not a supported platform.
With that said there are other things that could cause the license manager to fail. The biggest problem is the server code may have changed. This can be caused by any number of changes on the PC running the license
manager. An additional NIC being installed, a modem being installed, the IP address changing( needs to be static for tcp/ip ), or the host name of the PC changing.
To remedy this, uninstall the modem, set a static IP, remove all but 1 NIC and bind it to your protocol( either tcp/ip for WIN9x, NT installs, or ipx/spx for Novell installs ). Then re-authorize the ADLM for the new server
code and run it manually on first start.
There are only a few rules that need to be followed to insure that the ADLM runs as designed, breaking or bending these rules will break the ADLM.
PSG Product Support, Americas
WW Support & Services, Autodesk
Discussion Q&A: http://www.autodesk.com/discussion
Thats all well and good, but Netware 5 has been out at least 18 months, I
belive and they already have versions above 5 out. The real push (for
some) to move to NW-5 is the ability to run IP only and eliminate IPX.
We have always ran ADLM on an older Windows workstation (a 486-66 at
present) that is unsuitable for any other use, but this ties up another
network connection and deskspace. Luckily ADLM does not require much to
operate, just a stable PC.
it would great if Autodesk would put as much effort into Novell support as
they (appear to) have with Windows new releases.
We do a lot of testing on both Novell and Microsoft. We test with Novell 3.2
up to 5.01. The problem here is not the Novell support, but that Elan is a
very old tool now. That is why we are not supporting pure IP on Novell. We
are looking at newer license managers, but that will be in the future.
Hope this helps clear this up.
> Thats all well and good, but Netware 5 has been out at least 18 months, I
> belive and they already have versions above 5 out. The real push (for
> some) to move to NW-5 is the ability to run IP only and eliminate IPX.
> We have always ran ADLM on an older Windows workstation (a 486-66 at
> present) that is unsuitable for any other use, but this ties up another
> network connection and deskspace. Luckily ADLM does not require much to
> operate, just a stable PC.
> it would great if Autodesk would put as much effort into Novell support as
> they (appear to) have with Windows new releases.
thanks for the info and sorry for the delay in posting, i've been covered by
"real engineering work".
I am a network admin by default, so please excuse the lack of knowledge
sometimes. Our firm does what it takes to keep things going as smooth as
possible, but I would certainly try to use a Netware 5.0 license server when
it becomes available. One less workstation to keep alive.