Actually I have visited a lot of customers that did not want to run the NLM
for Elan. They used a Windows 95 box that was put in a corner that it ran
just fine. Not something I would recommend, but it did work.
Netware 5.1 can run as pure IP. We have it running in our LAB and it works
GREAT, so yes it does exist and Flex runs fine on it. The idea would be to
not use a workstation that someone actually sits at and uses, but to setup a
Windows 2000 or NT 4 box just for the license manager. This works fine with
"ljb" wrote in message
> firstname.lastname@example.org wrote:
> >Hi Guys,
> >You can run Flex on a Novell TCP/IP network. You would have to do it at
> >local workstation, but it does work. There is no NLM so you can not put
> >on the actual Netware server. Globetrotter actually had an NLM a while
> >back, but stopped supporting it.
> No such thing really as a "Novell TCP/IP network". The issue is the
> platform for running the Autodesk licensing server itself. The network
> itself is irrelevant.
> We can't run it on a workstation because people turn their workstations
> off at night, and anyway interactive Windows boxes are too unreliable
> for this and they need to be rebooted too often.
> I don't blame Autodesk for not supporting Novell since FlexLM doesn't
> support it. But how about considering supporting some of the other server
> platforms which FlexLM does support? Put in my vote for Linux.
It appears that you have a different EULA than I.
End-User License Agreement for Microsoft Desktop Operating Systems
Microsoft(r) Window NT(r) Workstation Version 4.0
Maximum Number of Processors:2
My item 1 is
Software Installation and Use. You may only install and use one copy of the SOFTWARE
PRODUCT on the COMPUTER.
Network Services. Except as otherwise provided below, if the SOFTWARE PRODUCT
documentation indicates that the SOFTWARE PRODUCT includes functionality that enables the
COMPUTER to share resources over a network with other computers or workstations, any
number of computers or workstation may access or other wise utilize the basic network
services of SOFTWARE PRODUCT on the COMPUTER. The basic network services are more fully
described in the printed materials accompanying the SOFTWARE PRODUCT and include file and
print services and peer Web services.
Windows NT Workstation Network Services. If the SOFTWARE PRODUCT is Windows NT
Workstation, a maximum of ten (10) inbound peer connections may simultaneously access or
otherwise utilize the basic network services of the SOFTWARE PRODUCT or COMPUTER. The
ten-connection maximum includes any indirect connections made through software or hardware
that pools or aggregates connections.
Item 3 would seem to be a "gotcha". It clearly states 10 inbound peer connections. My
argument is over the term connections. The MS license logging service doesn't count udp
as a connection. It can't, because there are no connections when using udp, it is a
connectionless protocol. If you use tcp then the case would be different. In fact it
would appear that globetrotter added udp as a supported protocol in V3 to handle similar
unix situations. From the FlexLM documentation:
When using UDP, there is no limit to the number of end users per vendor daemon process,
because they can share a single socket in the vendor daemon (UDP has other drawbacks, and
TCP is preferred).
"ljb" wrote in message
> jmartin@^nospam^fsb-ae.com wrote:
> >Could you please quote me the paragraph(s) where the MS EULA says that a workstation
> >cannot be used for network services? Or where it has to have someone actually working
> Cannot be used *only* for network services, I think said.
> This from the Microsoft Windows NT Workstation EULA, item 1:
> | You may install the SOFTWARE PRODUCT on a single computer
> | ("Workstation Computer") for use as interactive workstation
> | software, but not as server software.
> Seems pretty clear to me.
> Notwithstanding this:
> | However, you may permit a maximum of ten (10) computers to connect to the
> | Workstation Computer to access and use services of the SOFTWARE PRODUCT,
> | such as file and print services and peer web services.
> Which says that in addition to interactive use, up to 10 computers can
> connect over the network.
> So how about it... will we be able to get FlexLM on Linux serving
> AutoCAD licenses and all stay nice and software-legal?
We are looking at another licensing manager software to handle many licensing issues. You should check out Sassafras NetWorking software at http://www.keyserver.com.au. They allow you to license almost any software and it works with Novell and Linx. Give it a look because it is cheaper than setting up a NT/2000 server just to do license management.
>It appears that you have a different EULA than I.
>End-User License Agreement for Microsoft Desktop Operating Systems
>Microsoft(r) Window NT(r) Workstation Version 4.0
I stand corrected, sort of. It turns out there are at least 2 different NT
licenses. The OEM version ("for sale only with a new computer"), which you
quoted, does not have the "for use as interactive..." restriction, which is
in the full version. Why the more expensive "full" version should be more
restricted then the low-cost OEM bundled version is beyond me.
>Item 3 would seem to be a "gotcha". It clearly states 10 inbound peer connections. My...
Actually, it isn't clear at all that the 10 inbound connections limit
applies to anything but those services which are included in NT itself,
such as peer web server, SMB networking, and printing:
"However, you may permit a maximum of ten (10) computers to connect to the
Workstation Computer to access and use services of the SOFTWARE PRODUCT..."
One could read this as meaning that an add-on service, such as FlexLM,
would not at all be included in this restriction.
In spite of all the above, it would still be much better to be able to run
it on a real server, including non-Windows servers.