<html><body bgcolor="#FFFFFF"><div>For jaws do local installs instead of network installs of the program. Create a system environment variable with the name LSFOREHOST and variable that is the IP address of the license server on the computer u want jaws to run. </div><div>For zt create a generic user with read access to the zt folder map the folder on the computer want zt to run This should make the folder available to all users on the machine. If the server is not on the use the IP of the server instead of the UNC for zt server install and to map the folder. </div><div>Jeff<br><br>Sent from my iPhone</div><div><br>On Feb 21, 2011, at 11:40 AM, Al Puzzuoli <<a href="mailto:alpuzz@msu.edu">alpuzz@msu.edu</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div class="WordSection1"><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">At MSU, we are using server based licenses for most of our AT . Our primary network of labs spans the majority of campus. The labs are on their own network segment and the license servers work just fine. However, we are increasingly dealing with situations in which departments have set up their own labs. In these scenarios, I’m not finding many perfect solutions. We have enough concurrent licenses to go around, but no good way of distributing them.<o:p></o:p></span></p><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The zoomtext license server is a joke when it comes to security. It requires that a shared folder be exposed and read, and I think also write permissions be granted to everyone. Definitely not something I would want to open up for campus wide use. I know there is a dongle based version of Zoomtext, but that introduces its own set of problems. First of all, I don’t feel that we should have to spend any more money because we have already bought the number of licenses we need. Then there are the headaches associated with keeping track of the dongles.<o:p></o:p></span></p><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Jaws presents similar issues. I think the security is better on the Jaws license server, but I’m unsure as to whether it can be effectively shared between subnets. I suppose it might be possible to set up some firewall rules wherein the proper ports are opened to certain IP addresses or certain subnets? Has anyone done this?<o:p></o:p></span></p><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for any thoughts,<o:p></o:p></span></p><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p><p class="MsoPlainText">Al Puzzuoli<o:p></o:p></p><p class="MsoPlainText">Information Technologist <o:p></o:p></p><p class="MsoPlainText">Resource Center for Persons with Disabilities 517-884-1915 120 Bessey Hall East Lansing, MI 48824-1033 <a href="http://www.rcpd.msu.edu"><a href="http://www.rcpd.msu.edu">http://www.rcpd.msu.edu</a></a><o:p></o:p></p><p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Athen mailing list</span><br><span><a href="mailto:Athen@athenpro.org">Athen@athenpro.org</a></span><br><span><a href="http://athenpro.org/mailman/listinfo/athen_athenpro.org">http://athenpro.org/mailman/listinfo/athen_athenpro.org</a></span><br></div></blockquote></body></html>