The network keyserver which is required by this program

The network keyserver, which is required by this program, didnot respond. Please check the network connection and try opening the program again. Hi, I am upgrading our DPA to The error messages on pop up windows as follows as: KeyAccess -- " The network keyserver, which is required by this program, didnot respond.

Please check the network connection and try opening the program again" " The setup was unable to automatically close all requested applications. Thanks in Advance. Log In Sign Up. Keep me logged in on this device Forgot your username or password? Don't have an account? Sign up for free!

What do you need help on? Cancel X. Topic Archived. Sign Up for free or Log In if you already have an account to be able to post messages, change how messages are displayed, and view media in posts.

Boards PC Dreamweaver program help. You have to be on the school network to use that program. Do I have to open a blank text file in dreamweaver for it to work? I am working in a public access Mac laboratory in Helsinki University.

I agree the Mac is "the most intuitive computer ever sold, but that's not saying much. So I see there is one glaring omission in a Macintosh network: the lack of multiuser perspective. Why should a network have the added complexity to allow workstations to be used by different people at different times, then? Well, think about the future. Many people will be carrying their own computer around all the time like pens and bags, but we will still want to use the better computers lying around us when we are at them.

I definitely would like floating-license-aware, network-aware and multiuser-multiworkstation-aware software but there is almost none. The settings files are in the workstation. Not good, when several people use the same Mac workstation. Solution 1: Keep the settings in a networked home folder. And those aliases should be allowed in the system folder, too. Appletalk doesn't recognise the concept of active user's home folder!

Unbelievably short-sightedly microcomputer oriented but true. So the alternative solution is to launch from your own settings files which means there is no fixed routine that the operator could set up for naive users. Or you can launch from templates storing an arbitrary and varying subset of all the settings concerning your document and your environment. The problem of operating system settings and resources being workstation-dependent and not user-dependent still remains.

If aliases were allowed inside the system folder it would help. Problem 2. The writable files which are shared by several users network installed programs the resources of which are modified run time; style libraries, user dictionaries; Netnews spool files are not safely sharable and in worst cases are hard coded by the software to be in the local system folder.

Solution 2: In people's minds, make it clear which is a program's data and code resources only touched by the maintenance, which is b common sharable data and which is c individual user settings. Keep all these in the network in different places and provide appropriate locking. With a lot of software you can't do that.

And even if you can, this strategy is not covered in the manual and you can never tell if it works safely or not, because multiuser conflicts typically occur very rarely. I have spent hundreds of hours during the past year debugging e. Canvas, Statview and various HyperCard stacks in this respect, mostly with no results: I still don't know which problems if any are related to this. Install suspicious software locally.

It will only increase my maintenance work fold. The Helsinki University owns dozens of different software packages and Mac workstations on the metropolitan network. Problem 3. The software you can only launch once with one serial number in the same network. Solution 3: Don't buy them. Buy programs which allow you to use floating license servers or some other sensible method of copy protection. I have a very smooth pay by use copy protection product idea, interested capital can contact me ;- We at the Helsinki University use LaunchBreak license server from the University of Michigan.

I accept this method of copy protection though, if a network installable multiuser version is available! Again the real problem is that there is no standard floating license server in the operating system.

Buy N packages of it. Install PageMaker in the network and put the Aldus-folder there too. Reinstall it N times in some workstation and save the resulting N pieces of PM 4. The Aldus folder may be in the network. PM asks its place when run first time, then it remembers.

We can never be sure that this wouldn't cause write conflicts in the networked Aldus folder but it seems to work. Burtan: be Reply to author.

Report message as abuse. Show original message. Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message. If so do you like the program? John Mearns. Humphreys writes:. Alex Morando. Kyle Barger. Anssi Porttikivi. Blair M. It has worked without major incident for a year now. Well, until we got 25 new machines. Our designers using Illustrator 3. KeyServer acted accordingly to the tearing out of hair by the designers.

Everybody was screaming at me for one reason or another including "How come we didn't have this problem until now" Well, you guys are now using the software much more than before. So, I was given the directive to buy more copies of Illustrator.