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.

It's usually best to try and connect to one geographically close, even though that may not be the best. You can always ask when you get on irc. You need to connect to a server connected to the IRCNet to join the regulars on #DeepPurple. Here's a list of servers avaliable for connection: This is, by no means, a comprehensive list, but merely a start. Connect to one of these servers and join the channel #DeepPurple

To enable communication between the OpenHand server and the OpenHand client, the client first needs a network connection. Typically, laptops and PDAs have one of the following: the means to communicate with a phone to enable this connection, either via Infra Red or increasingly Bluetooth (link to www.bluetooth.com), which is either built into devices (such as the later HP iPAQ's) or available as an expansion card (as with many of the Palm devices).

A common mistake when starting the client is to give the wrong server host name. The last synergyc command line option (Unix) or the "Server Host Name" edit field (Windows) should be the host name (or IP address) of the server not the client's host name.

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.

Open a web browser and goto http://insors.internet2.edu. Enter your username and password. Once logged in, click on the Manual Bridge button. For hostname use ag1.v19.uthscsa.edu and for audio/video ports for the desired room, you can find those ports here.

mysql -h cgi -u username -p username -- where "username" is your username (without the quotes).

If the client is a Windows 3.xx operating system, the client PC's machine name is not defined in the TCP/IP Host file. In Netscape Navigator, set the 'SOCKS Host' to the IP of the Server PC and set 'port' to 1080. Remember to leave all other proxy entries in blank; or If indeed you are using Windows 3.xx, search for the Host definition or Host file associated with your TCP/IP package and enter your client PC host name (machine name) and this client PC's IP address.

Web Client and Web Server both have their TCP agent embeded inside Web client and Web server. So they can connect directly to a node.

TCP is already integrated in Web Server and Web Client. Just connect the Web Server/ Web Client directly to the node.

Due to the security features of the Java programming language, a java applet can only make a network connection to the same machine that the Java resides on. This cannot be worked around. Check out Sun's Java FAQ (http://java.sun.com/sfaq) question #8 for details.

Access to the new VCCS student email system is by web browser only. We recommend that you use the latest version of Internet Explorer.

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.

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.

Yes. The synergy network protocol is platform neutral so synergy doesn't care what operating systems are running on the server and clients.