Microsoft KB Archive/224465

= Using America Online with BackOffice Small Business Server =

Article ID: 224465

Article Last Modified on 12/3/2003

-

APPLIES TO


 * Microsoft BackOffice Server 4.0
 * Microsoft BackOffice Server 4.5
 * Microsoft BackOffice Small Business Server 4.0
 * Microsoft BackOffice Small Business Server 4.0a
 * Microsoft BackOffice Small Business Server 4.5

-



This article was previously published under Q224465



SUMMARY
In America Online (AOL) version 3.0 and later, you can run streaming audio programs, browsers, Internet Relay Chat (IRC) clients, and Winsock-compatible software. To accomplish this in Microsoft Windows 95 and Microsoft Windows 98, you can install a virtual device driver using the Network tool in Control Panel.

This virtual device driver enables Winsock programs to run. The Windows 95 and Windows 98 Winsock dynamic-link libraries (DLLs) included with AOL software do not function in Microsoft Windows NT; they are dependent on the virtual device driver. The AOL 16-bit Winsock stack does work, but only with 16-bit programs.



MORE INFORMATION
When you start the AOL client, the program checks for a Winsock.dll file that may be loaded in memory. If this DLL is not loaded, the AOL version of the Winsock.dll file is loaded from the Winsock folder located in the main installation folder. This file works only with AOL, and only when the client software is logged on. This means that Winsock functionality works only if the AOL client is running and authenticated on the network.

You cannot use AOL as your Internet service provider (ISP) with BackOffice Small Business Server (SBS) because AOL does not provide a Point-to-Point Protocol (PPP) connection, which most ISPs do provide. Instead, it emulates the packets in AOL standard format (ASF). The packets are then converted by AOL's proprietary proxy systems for use on an IP-based network. For a PPP connection to work, the client program must be running and authenticated.

Because SBS is a Windows NT-based operating system, the AOL client does not install the AOL adapter (the virtual device driver that provides loopback functionality and emulation for Winsock-based programs) for compatibility reasons. Only 16-bit Winsock programs work in Windows NT with AOL.

There is no way to force AOL to dial when there is Winsock activity. This is because AOL loads the AOL Winsock only when the client is running, and when it attempts authentication on the AOL network. This means the AOL client does not automatically connect to the AOL network at specified intervals or upon detected network activity destined for a remote network.

There is functionality in AOL to automatically connect and retrieve e-mail. This functionality is called autoAOL and it does not work with Winsock programs.

Microsoft Exchange Server is a full-featured groupware messaging server. It is capable of handling many modes of transport for e-mail and calendar messages. One of the features of Exchange Server is the ability to use Remote Access Service (RAS) to remotely connect to an ISP to retrieve e-mail, using commands such as ETRN, SBSETRN, or DEQUEUE. Because Exchange Server uses the RAS phonebook entry, this functionality does not work with the AOL client software.

Using Another ISP with AOL
AOL has a "bring your own access" option. Instead of using the AOL proprietary packet-switching network, this option lets you make a connection using TCP/IP over the Internet into the gateway. This option is less expensive than standard access and helps offset the price of a full ISP, which provides PPP functionality and RAS capability.

To connect to AOL through a local ISP:
 * 1) Configure AOL to use TCP/IP as the primary protocol.
 * 2) Configure RAS to connect to a local ISP.
 * 3) After you make an ISP connection, you can start the AOL client, which uses the existing network connection to connect to AOL.

NOTE: This also works in Windows NT. This is an ideal configuration because Exchange Server uses the RAS phonebook entry for the ISP and you can still use the AOL client software.

Browsing Software
If you type an URL in AOL, AOL uses Microsoft Internet Explorer as the core rendering engine. AOL connects to the AOL proxy servers to speed up loading of the Web page (because the page may be cached on the AOL proxy servers). If you start a browser without the AOL client loaded and authenticated, the Web page is not loaded. If you authenticate the client computer on the AOL network and then start a Winsock-compatible browser, the AOL proxy servers are not used. Instead, the browser goes directly to the Internet through the AOL Internet gateway.

The SBSETRN and ETRN Commands with AOL
Because AOL does not offer e-mail services to customers beyond its proprietary client, the SBSETRN and ETRN commands do not function with AOL software. To use the ETRN command, a local ISP is required.

Microsoft Outlook with AOL
AOL no longer supports the Messaging Application Programming Interface (MAPI) Beta mail stack that was developed when AOL 3.0 Beta was released. Therefore, Outlook is not able to retrieve AOL mail.

AOL with POP3 and SMTP
AOL does not support POP3 clients. AOL does support Simple Mail Transfer Protocol (SMTP) through its e-mail servers, but only for Winsock programs originating from the internal proxy IP addresses that are assigned to client workstations after they sign on to the AOL network.

AOL with SBS Modem Sharing
If you install and enable the Modem Sharing client on a workstation and you attempt to run AOL, the modem port is detected (by the automatic detection process), but only if the shared modem port is on COM1-COM4. If there are four COM ports on a workstation and the shared network modem port is COM5, AOL software does not recognize it. The AOL client functions normally (as if the modem were connected locally) if the COM port is COM1-COM4.

AOL with Microsoft Proxy Client
If both the Proxy client and a local modem are installed, AOL functions properly by using the local modem. Attempting to use AOL with the Proxy by selecting TCP/IP as the logon transport in AOL does not work. For this option to work properly, you must open the AOL port (port 5190) for both the inbound and outbound TCP on the Proxy. The Proxy client does not affect the performance of the Modem Sharing client software.

AOL with Microsoft Proxy Server
Proxy Server requires a RAS phonebook entry, a dedicated TCP/IP connection to the Internet, or a Winsock layer that can automatically dial and perform authentication by detecting Winsock activity. Because AOL does not provide this functionality, Proxy Server does not work with AOL.

