Installation & Licensing

[#1]

Help!

We are ADLM to license our seats over our LAN using TCP/IP, and on the
workstations that have now upgraded to Windows 2000 Professional, we are
getting the error message about not being able to reach the license server.

I've downloaded the updated ADESKSYS.DLL, but the instructions say not to
install it if the datetime stamp of the original isn't as per spec. Our
existing
ADESKSYS.DLL doesn't meet the spec; I tried the updated version anyway,
and Autocad just hangs up on the splash screen.

What can I do?

Thanks in advance for all suggestions,
-doug quebbeman
systems administrator
the estopinal group

[#2]

"Douglas H. Quebbeman" wrote in message
news:23D64096DC7147B2117DB431C12A7E3B@in.WebX.SaUCah8kaAW...
> Help!
>
> We are ADLM to license our seats over our LAN using TCP/IP, and on the
> workstations that have now upgraded to Windows 2000 Professional, we are
> getting the error message about not being able to reach the license
server.
>
> I've downloaded the updated ADESKSYS.DLL, but the instructions say not to
> install it if the datetime stamp of the original isn't as per spec. Our
existing
> ADESKSYS.DLL doesn't meet the spec; I tried the updated version anyway,
> and Autocad just hangs up on the splash screen.

Ok, I have been able to solve my own problem by reading the thread
"More ADT2 Win 2k network problems" by setting the environment
variable ACADSERVER to @MYSERVERNAME (where MYSERVERNAME
is the name of the server where ADLM is running). Either it was not required
to set this variable previously, or, the preconfigured install was setting
it for
installations on NT machines but not for installations on Win2k machines.

When I preconfigured the network install, I probably entered the server
name in lower case; however, I notice Win2k is upper-casing lots of names
that were formerly shown in all lower case.

I am most disturbed that no one at Autodesk has updated the instructions
contained in the text file pointed to by the link:

ftp://ftp-2.autodesk.com/pub/autocad2000/patches/sys_dll.txt

to include trying the environment variable fix first.

Thanks to the participants in the "More ADT2 Win 2k network problems"
thread for having thought sufficiently out loud to provide me with a clue.

regards,
-doug quebbeman
systems administrator
the estopinal group

[#3]

Doug,

The @ symbol issue is a requirement of the AEC products only, that is why it
is not mentioned in the document you quote below, which applies to AutoCAD.
There is a document in the pipeline for AEC products that explain this fix.

Jerry Milana,
Autodesk Product Support

"Douglas H. Quebbeman" wrote in message
news:51F501C94C94905A145B30D0BAE5F74B@in.WebX.SaUCah8kaAW...
> "Douglas H. Quebbeman" wrote in
message
> news:23D64096DC7147B2117DB431C12A7E3B@in.WebX.SaUCah8kaAW...
> > Help!
> >
> > We are ADLM to license our seats over our LAN using TCP/IP, and on the
> > workstations that have now upgraded to Windows 2000 Professional, we are
> > getting the error message about not being able to reach the license
> server.
> >
> > I've downloaded the updated ADESKSYS.DLL, but the instructions say not
to
> > install it if the datetime stamp of the original isn't as per spec. Our
> existing
> > ADESKSYS.DLL doesn't meet the spec; I tried the updated version anyway,
> > and Autocad just hangs up on the splash screen.
>
> Ok, I have been able to solve my own problem by reading the thread
> "More ADT2 Win 2k network problems" by setting the environment
> variable ACADSERVER to @MYSERVERNAME (where MYSERVERNAME
> is the name of the server where ADLM is running). Either it was not
required
> to set this variable previously, or, the preconfigured install was setting
> it for
> installations on NT machines but not for installations on Win2k machines.
>
> When I preconfigured the network install, I probably entered the server
> name in lower case; however, I notice Win2k is upper-casing lots of names
> that were formerly shown in all lower case.
>
> I am most disturbed that no one at Autodesk has updated the instructions
> contained in the text file pointed to by the link:
>
> ftp://ftp-2.autodesk.com/pub/autocad2000/patches/sys_dll.txt
>
> to include trying the environment variable fix first.
>
> Thanks to the participants in the "More ADT2 Win 2k network problems"
> thread for having thought sufficiently out loud to provide me with a clue.
>
> regards,
> -doug quebbeman
> systems administrator
> the estopinal group
>

[#4]

You saved my life! I was sure this couldn't be resolved, but this @
symbol did the trick!

Frank Bulk

"Douglas H. Quebbeman" wrote:
>
> "Douglas H. Quebbeman" wrote in message
> news:23D64096DC7147B2117DB431C12A7E3B@in.WebX.SaUCah8kaAW...
> > Help!
> >
> > We are ADLM to license our seats over our LAN using TCP/IP, and on the
> > workstations that have now upgraded to Windows 2000 Professional, we are
> > getting the error message about not being able to reach the license
> server.
> >
> > I've downloaded the updated ADESKSYS.DLL, but the instructions say not to
> > install it if the datetime stamp of the original isn't as per spec. Our
> existing
> > ADESKSYS.DLL doesn't meet the spec; I tried the updated version anyway,
> > and Autocad just hangs up on the splash screen.
>
> Ok, I have been able to solve my own problem by reading the thread
> "More ADT2 Win 2k network problems" by setting the environment
> variable ACADSERVER to @MYSERVERNAME (where MYSERVERNAME
> is the name of the server where ADLM is running). Either it was not required
> to set this variable previously, or, the preconfigured install was setting
> it for
> installations on NT machines but not for installations on Win2k machines.
>
> When I preconfigured the network install, I probably entered the server
> name in lower case; however, I notice Win2k is upper-casing lots of names
> that were formerly shown in all lower case.
>
> I am most disturbed that no one at Autodesk has updated the instructions
> contained in the text file pointed to by the link:
>
> ftp://ftp-2.autodesk.com/pub/autocad2000/patches/sys_dll.txt
>
> to include trying the environment variable fix first.
>
> Thanks to the participants in the "More ADT2 Win 2k network problems"
> thread for having thought sufficiently out loud to provide me with a clue.
>
> regards,
> -doug quebbeman
> systems administrator
> the estopinal group

--
Frank Bulk (bulkf@dordt.edu)