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.

You can check this whith our WkMacList when clicking the network icon. Of course, it must be ensured that a WIBU-KEY server process (WkSvMac) has been started.

This is necessary for a "trouble-free" operation. Is the WIBU-BOX locally detected on the concerning WIBU-KEY server? You can check this with our tool WkConfig.

You can check this with our tool WkMacList. The WIBU-BOX should be listed under the appropriate interface.

Please check this by double clicking the network icon on page "Contents" in the WIBU-KEY control panel applet. If this works, the drivers are correctly installed. In this case the problem is due to the configuration of the serverprocess or the server itself.

In case your hardware key is not reachable or it doesn't have the serial number tag on it, just go to Control Panel on the machine where it is plugged-in, double-click the WIBU-Key icon and the number will be shown as a subnode of the USB branch. An example of a serial number is "8-12345678". It always starts with a single number and a dash. The number in the beginning can be 6, 7, 8 or 9. And after the dash there must be 7 or 8 numbers.

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.

Clients and Servers are separate logical entities that work together over a network to accomplish a task. Many systems with very different architectures that are connected together are also called Client/Server.

There are usually 60-80 Virtual Servers configured on each physical server. The load on each physical server is closely monitored and load balancing is employed to insure that the resources on one server are not unfairly taxed by a single Virtual Server.

Our servers is located at Jaring Datacenter, Malaysia and Equinix Datacentre, Singapore. More information on our network on HERE

SingTel EXPAN's Data Centres are backed by SingTel's extensive and robust cable network and satellite infrastructure. SingTel's Internet Exchange (STiX) is Asia's largest Internet backbone, supplying more than 2.5 gigabits of bandwidth to Asia Pacific region. SingTel EXPAN's extensive Internet connectivity has direct connections to over 33 countries and more than 90 ISPs in the Asia Pacific region.

A gateway operates at the upper levels of the OSI model and translates information between two completely different network architectures or data formats.

SEER*Stat can operate in one of two modes, "local" and "client-server". In local mode, all processing and data are local to your PC environment; that is, your PC performs all calculations, and the program and data files are stored on the PC's hard drive, your local network, or a CD. In client-server mode, the SEER*Stat software installed on your PC is the client and contacts the SEER server via the Internet to access data and perform calculations. Internet Connection Not Required.