Installation & Licensing

[#1]

I have had the license manager running on a NetWare server for almost 3
years. Recently I have begun having problems with the license manger.
Changes to the server would include changing from NetWare 4.11 and service
packs to NetWare 5.0 and service packs to NetWare 5.1 and service packs.

Users will all of a sudden receive that error message that the hardware
lock is not found. I trie to query the license mananger and it is not
found. Looking at the server, adskelmd.nlm still appears to be running. I
unload and reload the NLM and all is back to normal. Any ideas why the
license manager keeps losing its connection?

I have also recently had trouble loading the license manager when the
server is restarted. License manager unable to load, hit any key to
continue. I can then manually load the NLM and it will work.

Any help would be appreciated.

adskelmd.nlm 9/25/1998 292,404 bytes
--
David Patnaude, MCSE, MCP+I, CNA 5
dpatnaude@tamsconsultants.com

To reply by e-mail, remove clothes.

[#2]

Are you by chance running tcp/ip on the nw server? If so this is not supported by the
adlm. It will sometimes work, but it's not supported. Even if you are running tcp/ip and
ipx/spx it "tends" not to work reliably. I've not tested it on nw5 but I've heard that if
you go back to ipx/spx only on the nw server the adlm will function correctly.

hth

jason martin
frankfurt-short-bruza

"David Patnaude" wrote in message
news:903372BA0dmpziplink@198.102.112.35...
> I have had the license manager running on a NetWare server for almost 3
> years. Recently I have begun having problems with the license manger.
> Changes to the server would include changing from NetWare 4.11 and service
> packs to NetWare 5.0 and service packs to NetWare 5.1 and service packs.
>
(snip)
> David Patnaude, MCSE, MCP+I, CNA 5
> dpatnaude@tamsconsultants.com
>
> To reply by e-mail, remove clothes.

[#3]

jmartin@^nospam^fsb-ae.com (jason martin) wrote in
:

>Are you by chance running tcp/ip on the nw server? If so this is not
>supported by the adlm. It will sometimes work, but it's not supported.
>Even if you are running tcp/ip and ipx/spx it "tends" not to work
>reliably. I've not tested it on nw5 but I've heard that if you go back
>to ipx/spx only on the nw server the adlm will function correctly.
>
>hth
>
>jason martin
>frankfurt-short-bruza
>
>"David Patnaude" wrote in
>message news:903372BA0dmpziplink@198.102.112.35...
>> I have had the license manager running on a NetWare server for almost
>> 3 years. Recently I have begun having problems with the license
>> manger. Changes to the server would include changing from NetWare 4.11
>> and service packs to NetWare 5.0 and service packs to NetWare 5.1 and
>> service packs.
>>
>(snip)
>> David Patnaude, MCSE, MCP+I, CNA 5
>> dpatnaude@tamsconsultants.com
>>
>> To reply by e-mail, remove clothes.
>
>

We are running both IPX and TCP/IP on the server. We are using TCP/IP for
the servers to communicate with each other over the WAN. I'll have to check
with the corporate office to see if we can change that setup.

Thanks,
--
David Patnaude, MCSE, MCP+I, CNA 5
dpatnaude@tamsconsultants.com

To reply by e-mail, remove clothes.

[#4]

David,

The behavior you describe is often encountered when Netware Servers are
marginal in RAM resources. Netware is going to give the file system
priority to system memory resources. As for the errors encountered during
reboot, they can often be resolved by moving the adlm startup string in the
Autoexec.ncf up or down the list.

jerry milana

"David Patnaude" wrote in message
news:90337769Bdmpziplink@198.102.112.35...
> jmartin@^nospam^fsb-ae.com (jason martin) wrote in
> :
>
> >Are you by chance running tcp/ip on the nw server? If so this is not
> >supported by the adlm. It will sometimes work, but it's not supported.
> >Even if you are running tcp/ip and ipx/spx it "tends" not to work
> >reliably. I've not tested it on nw5 but I've heard that if you go back
> >to ipx/spx only on the nw server the adlm will function correctly.
> >
> >hth
> >
> >jason martin
> >frankfurt-short-bruza
> >
> >"David Patnaude" wrote in
> >message news:903372BA0dmpziplink@198.102.112.35...
> >> I have had the license manager running on a NetWare server for almost
> >> 3 years. Recently I have begun having problems with the license
> >> manger. Changes to the server would include changing from NetWare 4.11
> >> and service packs to NetWare 5.0 and service packs to NetWare 5.1 and
> >> service packs.
> >>
> >(snip)
> >> David Patnaude, MCSE, MCP+I, CNA 5
> >> dpatnaude@tamsconsultants.com
> >>
> >> To reply by e-mail, remove clothes.
> >
> >
>
> We are running both IPX and TCP/IP on the server. We are using TCP/IP for
> the servers to communicate with each other over the WAN. I'll have to
check
> with the corporate office to see if we can change that setup.
>
> Thanks,
> --
> David Patnaude, MCSE, MCP+I, CNA 5
> dpatnaude@tamsconsultants.com
>
> To reply by e-mail, remove clothes.

[#5]

milanaj@autodesk.com (jerry milana) wrote in
<6059EA819B2D43214955A4CD9C53D0B8@in.WebX.SaUCah8kaAW>:

>David,
>
>The behavior you describe is often encountered when Netware Servers are
>marginal in RAM resources. Netware is going to give the file system
>priority to system memory resources. As for the errors encountered
>during reboot, they can often be resolved by moving the adlm startup
>string in the Autoexec.ncf up or down the list.
>
>jerry milana
>
>

Jerry,

I have tried moving it up and down the list in the autoexec.ncf file
without success. The server has 768 MB of RAM and is not being hit that
hard to run low on resources.
--
David Patnaude, MCSE, MCP+I, CNA 5
dpatnaude@tamsconsultants.com

To reply by e-mail, remove clothes.