SAPS

Up and Linked
Once I had the modem defined, I only had to configure Dial-Up Networking (DUN) to use the correct modem, and I was off and running. Well, sort of. I used SAPS to dial in to the Windows NT Magazine domain, the Windows NT Magazine Lab domain, and my Internet Service Provider (ISP). Two of the three connections worked fine. I had no problem with the Lab domain connection or my Internet account, but I couldn't maintain a connection to the Windows NT Magazine domain. The server hung up on the modem after a few seconds of connectivity.

I thought I might have a protocol-related problem. But SAPS can transport any protocol, because it fits into the network at a level where it operates independently of the LAN protocol. Technical support suggested I had a licensing problem. They thought the Windows NT Magazine domain had a SAPS server with the same licensing information. Yes, that's why I entered the SAPS licensing information multiple times­I tried various combinations of SpartaCom license keys.

All of this typing was to no avail. I never resolved the problem of dialing in to the Windows NT Magazine domain. SpartaCom's technical support was willing to go to any length to resolve the problem, but when I needed to run a network monitor to see what was going on, I realized I didn't have the time to invest to reach a solution. Don't let this experience deter you, though. I would have resolved the problem had I continued working on it. And remember that my other two test connections worked fine. The only word of caution I can give you is to try SAPS before you buy it (SpartaCom has trial versions available on its Web site).

Although I gave up on dialing in to the Windows NT Magazine domain, I continued to test SAPS by dialing in to the Windows NT Magazine Lab domain and the Internet using all the modems at my disposal. In all cases, SAPS provided connections with the same reliability and speed I got when I used the modems in a direct-connect environment.

SAPS for You?
SAPS is not a general-purpose solution for all your remote connectivity needs. SAPS does not let multiple clients share the same modem concurrently. SAPS is not a router, nor is it a proxy server.

However, SAPS does let you share a limited number of modems or high-speed connections (e.g., ISDN, X2, K56Flex) among a set of desktops. SAPS also works well with desktop fax solutions: You can configure the clients to access a fax modem via a SAPS port. And SAPS is an excellent solution if your desktop users need to occasionally dial in to a bulletin board system (BBS) or the Internet.

When I was reviewing SAPS, I was also testing proxy server products and I found another use for SAPS that is not immediately obvious. When you are using a proxy server, your client systems don't have real IP addresses on the Internet. Unfortunately, many software programs demand a real IP address to function properly--realtime audio/video conferencing programs (e.g., CUSeeMe and IPhone) are an obvious example. Because of the IP address problem, I found that SAPS makes an excellent complement to a proxy server. For example, when I am accessing generic Web sites and email from my clients, I can use the proxy server link. But when I want to use conferencing software, I can use SAPS to make a direct connection between my system and the Internet. SAPS provides a neat solution to a difficult problem.

I certainly regard SAPS as a good choice for port sharing in the NT environment. Once I worked through the minor licensing and configuration issues, SAPS gave me rock-solid performance. You can't help but like a product that does what it promises and does it well. SAPS clearly falls into that category.