Yes. Typically this is not a problem as far as performance is concerned. Administrators will find that running a Fax Client on the same machine as the Fax Server can make testing easier when required.

For large and/or long jobs, chiller and cloak, our dual-processor Linux boxes. For small jobs and day-to-day computing, stokes or cantor, both Suns.

From cantor and stokes, all Solaris machines and most other machines, lpr -Pprintername filename will print to the printer of your choice. For example, lpr -Pps myfile.txt The enscript command is useful for performing advanced printing techniques. For example, the following command will print myfile.txt in landscape mode, with two pages per printer page to the ps printer: enscript -2r -Pps myfile.

No, you can not. You must purchase at least 1 server license, which covers up to 5 users and only after that you can purchase additional client licenses.

A Server/Stand Alone license is required for any site using one or more copies of Caf?TimePro. A Client installation will not work without a networked licensed Server. For a single computer only a Server/Stand Alone license is required. For more than one computer a Server/Stand Alone license is required for one computer and the remainder must all be Client licenses.

The client programs communicate with the server program via a TCP/IP port. We recommend to use the default port number 1733@servername. All clients in the network which shall have access to the license daemon, must use the same port number. Client and server program can either run on two different machines, or on the same machine.

Yes, but you must modify the Server and Client using ResEdit. Contact Technical Support for instructions on doing this.

This may result in problems when both applications try to access the WIBU-BOX - you should disable the local subsystem on the network page of the WIBU-KEY Control Panel Applet. If there are time-out errors at the server, you can start the server using command START/HIGH WKSVW32.EXE with a higher priority.

Typically, SansGUI is installed on a hard drive of a computer or workstation. In some circumstances, especially with large clusters in laboratory settings, it may be desirable to install and maintain only one copy of SansGUI on a file server and access the software from networked computers. The following procedures describe the needed steps to set up SansGUI at both the file server and the remote access client sides.

If not, then enter the IP address of the WIBU-KEY server in the Server Search List on the Network page in the control panel applet.

Dr. Dobb’s Journal in its Linux and open source section is running an article by Emmett Dulaney with 50 Perl questions and answers. The focus is mainly on the knowledge of the language itself with questions like:

When you create the network installer, it develops an executable called mslsetup.exe. This executable directs the client software to point to NI Volume License Manager. If your license server, server's computer name, or server's computer ID has changed, simply use the Create Network Installer tool within NI Volume License Manager (Options?Create Network Installer) to develop a network installer that has the mslsetup.exe created for the new NI Volume License Manager server.

It should run fine on any Linux machine that has Java 1.4 or above installed. It might very well run on another flavor of Unix with Java correctly installed, but this has not been tested--contact us if you make it work!! The one caveat is that printing is not currently supported for Linux.

Obtain the CiteMaker UNIX distribution which is a compressed tar file. After uncompressing and untarring the distribution, examine the shell script install.sh. You will need to set a shell variable that specifies where you want the CiteMaker executables installed, and a shell variable that specifies the location of your fminit directory. Before installing CiteMaker make sure that you are not currently running FrameMaker.

You must store your keys unencrypted in order to do this. You are asked whether you want to store your keys encrypted during server installation. Choose "NO". Then create a script to start the handle server, and put that script in the same place as your other startup scripts. If you implement this after your initial installation, be sure to send the new sitebndl.zip file to the Handle System Administrator at hdladmin@cnri.reston.va.us.

Yes. You can install the server on the new machine, and then copy the *.dat, *.ini and *.conf files from the old server (remember to shut down both servers first). If the drive-names or paths are different on the two machines you then have to manualy correct the shares from the user manager.

If your system is a private system then anyone visiting your machine is unwelcome. Simply monitor and lookout for "established incoming" connections in the agent list panel. It is advisable to just monitor incoming traffic. The action you should take is to locate the visitor using our IP tracking tool by entering the IP address or the domain name in the VisualRoute input field.

A program might act as a server for interface A, and also as a client for interface B. This is easy. The program merely imports interface B like a normal client and exports interface A like a normal server. A program might want to provide a service, and also act as a client to other servers that provide the same service. In this case, the programmer must expend more effort. The problem is that the names of the server-side functions (manager routines) clash with the names of the client stubs.

The details vary, depending on exactly what you want to identify about the client, but it all comes down to handles. The server must receive a binding handle in order receive information about the client. If there is not a binding handle in the parameter list as defined in the IDL file, then use the [explicit_handle] attribute in the ACF file to add one when building the server.