OK thanks for the reply. Another issue I have is with the seeminly unstable nature of the DLM license server software (we have it running on a Solaris 9 box), which I have to restart every fortnight or so. If I don't it becomes unresponsive and either does not accept client connections, or dies completely.. Compared to the FlexLM software prevoiusly used (which never needed restarting), it is a real headache. When we first started using DLM it would only last a few days before a restart was needed, so compuware gave me the disable_usage parameter to add to the config file. This improved the stability slightly. Does anyone know of any other ways to improve the stability? Thanks, Michael

Hi Michael, perhaps changing the server configuration may help. according to the DLMhelp.chm page "Server Configuration File" configuration file (config.xml) is located in the config directory of the Compuware License Service's installation directory. The server section of the configuration file contains parameters that define: the server’s timeout, license files, and port number. Other parameters/objects within the server section are optional. HIH, Uli

OK thanks Uli. I have tried this including restarting the license server and deleting the .compuware folder on my test client. It did not work unfortunately, the timeout is still 10 seconds for the client.

hoogmike said Hi, is there any way to change the default timeout of 10 seconds that is in the config file downloaded to a client the first time it connects to the license server? We have a large number of windows clients connecting to a UNIX license server so it is impractical to manually change each client's config file. Thanks, Michael

Hi Michael, I´m afraid you have to change each clients config file if you want to to change the client timeout. I´d agree that it is impractical to manually change aech clients conofig file. But why would you have to change it manually? From my experience the config file file is almost identical on every client system. So create a network resource and put the new config file on it. Now you can easliy do a copy - best practice during login - of this file. Hope it helps Thomas