This page shows a flow chart describing how to set up the SafeDial+ with the SafeDial+ client using either the SafePort or a PCMCIA slot. Hover the mouse button or click on any of the boxes for more information.

SafeDial+ client functions

There are two version of the SafeDial+ client - the 16 bit version and the 32 bit version. The 32 bit version can ONLY be used when the SafeDial+ is in a PCMCIA slot AND when you are running Windows 9x or Windows Millennium. For example, if you are using Windows 98 and a SafePort you should use the 16 bit client - the 32 bit client will not recognise a SafeDial+ in a SafePort.

Both versions of the SafeDial+ client do the same thing - log you onto the SafeDial+ card using the password supplied with the key material loaded onto the SafeDial+, set the time and date on the card (the client takes the time and date from your PC) and also set the mode; either encrypt, clear or auto secure (only relevant in Commercial variants; UKG SafeDial+s can only operate in secure mode). These three things must be done before a call can be made or received using a SafeDial+ - if the SafeDial+ is removed from the SafePort or PCMCIA slot (which effectively means it has been powered off) then all this information is lost and must be re-entered. If you choose not to use the SafeDial+ client then there are other ways in which this information can be passed to the SafeDial+ prior to a call being made:
1) Using an initialisation string - this is done by manually entering the string in the advanced modem properties. In the example below the string $ubracal$mq0303251200z$uc has been used. This means:
$ubracal = logon with the password "racal". This is an example of the at$ub<password> command.
$mq0303251200z = set the time and date to 12:00 on 25th March 2003. This is an example of the at$mqyymmddhhmmz command.
$uc = sets to encrypt mode. The alternatives are at$uc (encrypt), at$ua (clear) or at$ua1 (auto).
Every time the SafeDial+ is initialised this string is sent to the it. The benefits of using this method is that you do not have to bother with the client any more. It is also easy to change the string if you change your password, key material validity dates etc. One possible drawback is that you have your password visible in clear text both here and in the modem log files. This is not a major issue though - if someone is able to view your modem log files then it means that your PC has already been compromised.

2) Using the SDSECURE.inf. This method is similar to the initialisation string method described above but instead of entering the information as a string it is actually included in the modem inf file (the sdsecure.inf file found in the/inf directory of the CD) used to install the SafeDial+. This method is really intended for RAS servers where you need to install a lot of SafeDial+s with identical settings. That is the main benefit here - that you can install multiple SafeDial+s without using the client and without bothering with initialisation strings. However, this is not really a recommended way of configuring the SafeDial+ - if you ever need to change any settings (for example if you changed your password) then you would have to uninstall the SafeDial+ and reinstall it.

SafeDial+ client versions

There are two versions of the SafeDial+ client for Windows - the 16 bit and the 32 bit version. The 16 bit version is designed for Windows 3.11, Windows NT and Windows 2000. The 32 bit version is designed for Windows 95/98 and Windows Millennium. At the time of writing Windows XP is not supported due to the fact that the Windows 2000 power saving fix effects Windows XP but Microsoft have not issued a patch for XP.. However, if you do wish to use Windows XP you should use the SafePort rather than PCMCIA which seems to work without any problems.

SafeDial+ 16 bit client version

If you are using the 16 bit client you should use the most recent version as shipped on the CD - this is version 2.07. The main difference with this version is that you can configure the speed of the COM port interface (See below). This is necessary when using 128K ISDN configuration. The 16 bit client only supports COM ports 1 to 4. If your SafeDial+ COM port is higher than this then you will not be able to use the client and you will have to use one of the other methods discussed in this document.

PCMCIA and SafePort

SafeDial+ should work OK in any type 2 PCMCIA slot. Some testing has been done with PCI/ISA to PCMCIA adapters (an adapter card that fits in a desktop PC) but at the moment we do not guarantee that any will work. You should be able to use the old (orange) SafePort without any problems but do be aware that the highest speed available on these SafePorts is 57600bps. The (blue) SafePort+ is now available (firmware version 4.4) which supports speeds up to 230400bps.

Windows 2000 Power Saving Fix

When using Windows 2000 (SP2 and earlier) and a PCMCIA client there is an important issue to be aware of - Windows 2000 will power off a PCMCIA modem when it is not in use - see Microsoft Knowledge Base article Q275042 (http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q275042 ) for more information and details of the fix. This is a problem with the SafeDial+ because even if you have logged on to the SafeDial+ (using the client or an initialisation string) Windows 2000 will power off the card and this information will be lost. So when you come to make a call it will fail because the information has been lost during power off. Follow the fix carefully as there are two parts to it - running an .exe and editing the registry. The fix turns power saving off for PCMCIA devices.

SafePort port speeds

As mentioned above there are different versions of the the SafePort - the orange, Racal SafePort (v3.1) and the blue Thales SafePort+ (v4.4). The hardware is essentially the same but the firmware has changed on the Thales SafePort+ to allow higher connection speeds (up to 230400bps). The manual included with the SafePort gives details on how to configure the unit using the *S command e.g. *S 115200,n,8,1 sets 115200 baud, no parity, 8 bit words and 1 stop bit. When doing this configuration what you are configuring is the RS232 serial port on the back of the SafePort that connects to your PC.

Driver installation

If you are using a PCMCIA slot the SafeDial+ will be automatically recognised as a SafeDial v34 when you put it into the PC. However, if you have the SafeDial+ in a SafePort it will not be detected and you need to add it manually using the Add modem wizard. In both cases you should use the MDMSD.inf file from the /inf directory of the CD. This means that when you use a PCMCIA slot you must allow Windows to recognise and install it as a SafeDial v34 and then go into Device Manager and use the "Update driver" facility. When the SafeDial+ is in a SafePort you can just choose the "Have disk" option and specify the MDMSD.inf file.
It is important that you use the correct driver file with the SafeDial+ or you can get unpredictable behaviour.

Return to the start page...