Small Business Server 4.5 Release Notes (Part 2 of 2)

This article contains a portion of the Microsoft BackOffice Small Business Server 4.5 Release Notes that are included with the product. The Readme.doc file that resides on the BackOffice Small Business Server disc may not be viewable from Windows 95 or Windows 98 clients because there is no .doc file name extension association at the operating system level on these client systems.

Fax

Windows 95 and 98 Clients Unable to See a Fax Printer

If you have created a fax printer on Small Business Server and your Windows NT Workstation 4.0 clients are able to see it, but your Windows 95 and 98 clients are unable to see it, you should shorten the share name of the fax printer. The maximum share name length that can be seen by Windows 95 and 98 clients is between 6 and 12 characters, depending upon the character set being used.

To shorten the share name of a fax printer:

1. From Small Business Server, click Start, point to Settings, and then point to Printers.
2. Select the fax printer your clients are unable to see.
3. Right-click the fax printer, and then click Sharing.
4. Shorten the share name.
5. Click Close.

Configuring Fax Printer Properties

Fax Service uses the Windows NT printer properties pages to configure fax printer settings such as permissions, ports, and auditing. The following guidelines for these printer properties do not apply to fax printers.

• On the Scheduling page, it is strongly recommend that you not change the default setting of Always. In addition, Print directly to the printer should never be selected. Changing the scheduling settings may result in failure to send faxes.
• On the General page, the Separator Page button does not apply to fax printers. It should not be used for any fax printers.
• On the General page, the Print Processor button does not apply to fax printers. Changing the print processors may result in Windows 95/98 clients not being able to send a fax or the fax taking a long time to send.

Faxing From Outlook 2000

The following are some problems you may experience when faxing from Outlook 2000:

• The E-mail "Subject Line" was not sent
  
  When faxing an e-mail message from Outlook on a Windows NT client computer, the subject line will not be sent by Fax Service. If you want the subject line to appear on the fax, you must enable cover page for Fax Mail Transport. See the Small Business Server Online Guide for steps on how to add and configure the Fax Mail Transport for a Windows NT client computer.
• Sending Attachments from Outlook prompts you with the Fax Send Utility
  
  If you are sending a file attachment to a fax recipient in Outlook, you may be required to use the Fax Send Utility in order to send the attachment. This occurs when the attachment is a file type that uses DDE to print. In this case, if the application corresponding to the file type is open, the Fax Send Utility will appear. If the application is closed, the mail will be sent directly. The most common applications that use this file type are Office 97 and Office 2000 applications. You can identify other files types that use DDE to print by using the following steps:
  1. Double-click My Computer, click on the View menu, and then click Options.
  2. Select the File Types tab.
  3. Under Registered File Types, double-click the file type you are interested in (e.g. Microsoft Word Document).
  4. Under Actions, double-click print or print to.
  5. Look at the Use DDE checkbox. If this is selected, the file type uses DDE to print.
• Sending Attachments from Outlook on Windows 95/98 clients results in multiple calls
  
  If you are sending a file attachment to a fax recipient in Outlook from a Windows 95/98 client, Fax Service will place a separate call for each attachment.
• Fax Messages from Outlook are not being sent
  
  Failure to deliver fax messages from Outlook could leave the fax transport in an unstable state. If no fax messages can be sent from Outlook, you must close and log out of Outlook, or restart the computer in order to reset the fax transport. You may run into this problem when attempting to send large fax jobs (such as bitmaps) on a Windows 95/98 client with low memory, or when attempting to fax from an application by printing to the fax printer while Outlook delivers a job to the printer spooler.

Faxing From Office 2000

When faxing from Office 2000 applications, the preferred methods of faxing are:

• Use the Print command to print the document to a fax printer.
• Use the Send to mail recipient command to send the document via e-mail.

The following methods of faxing from Office 2000 are not supported:

• Using the Send to mail recipient as attachment option. Please see the section above on faxing attachments from Outlook 2000.
• Using the Send document to fax recipient option (and the associated wizard) from Word 2000. Sending a document with the wizard cover page could result in a truncated message and/or multiple fax calls to send the message.
• Using the Send to mail recipient option from Excel 2000. This will not format the outgoing message correctly.

Fax Send Utility Does Not Display Outlook Contacts When Used on the Small Business Server Computer

The Fax Send Utility uses the Windows Address Book and not the Outlook Address Book when used on the Small Business Server computer. In order to create a fax address in Outlook, you must add the Fax Address Book and the Personal Address Book to Outlook. You will then be able to create a fax address in Outlook that will be visible in the Windows Address Book.

To add Fax Address Book and Personal Address Book to Outlook:

1. Click Start, point to Settings, click Control Panel, and then double-click Mail.
2. Click Add.
3. Select the Personal Address Book and then click OK.
4. Click Add.
5. Select the Fax Address Book and then click OK.
6. Click OK to close.

To create a fax address in Outlook:

1. Open Outlook.
2. From the Tools menu, select Address Book.
3. From the File menu, select New Entry.
4. Select Personal Address Book from the Put this entry in the drop-down list.
5. Select Fax Address from the Select the Entry Type box and then click OK.
6. Enter the recipients' name and fax numbers and then click OK.
7. Close the Address Book.

Fax Client Installer Attempts to Find the Fax Server

During the installation of the client applications on a Windows NT Workstation client computer, the Fax Client will attempt to locate the Fax Server even if the Fax Server was not installed on the Small Business Server computer. The Fax Client installer will prompt for the name of the Fax Server. Click Cancel and Setup will continue to install the client applications.

Small Business Server Supports Fax over ISDN Through Eicon Technology DIVA ISDN Adapters

Small Business Server offers direct ISDN support for Eicon Technology DIVA ISDN adapters. This technology includes Dial-Up Networking via ISDN miniports, fax services, and modem sharing via ISDN modem emulation. The additional CAPI interface supports non-Microsoft and non-Eicon Technology ISDN applications.

Dial-Up Networking (RAS) can be used for dialing into a remote device. To support V.34+ clients, GSM clients, and ISDN with the same number, automatic protocol detection is available. RAS can also be used for dialing out to the Internet or to an Intranet. We recommend using the Proxy Server auto-dial functions.

Modem emulation can be used for fax communication over two B-channels simultaneously and supports all features from the Small Business Server embedded fax services. The DIVA ISDN adapter works as a fax group 3 device at up to 14.4 Kbps. ISDN modem emulation can support Small Business Server embedded modem sharing. Fax and modem sharing is based on different virtual modems and depends on the B-channel protocol.

The following virtual modems are available:

• Eicon ISDN Digital Modem (HDLC for 64 and 56 Kbps)
• Eicon ISDN V.120 Modem (V.120 for 64 and 56 Kbps)
• Eicon ISDN X.75 Modem (X.75 for 64 and 56 Kbps)
• Eicon ISDN V.110 Modem (Rate adaption up to 38.4 Kbps)
• Eicon ISDN analog Modem (V.34+ 33.6 Kbps POTS)
• Eicon ISDN Fax Modem (Class 1 and 2 up to 14.4 Kbps)

Small Business Server can use the Eicon Technology ISDN adapters DIVA Pro 2.0 and DIVA Server BRI-2M. These ISDN adapters are available for ISA and PCI bus systems with U- or S/T-interface to the ISDN network. The DIVA Pro 2.0 supports analog connections (Fax Group 3 or analog V.34+) over one B-channel at a time.

To install DIVA ISDN

For installation instructions, please read the Readme.doc file in the \Eicon folder on Microsoft BackOffice Small Business Server 4.5 Disc 3. If there is a former version installed, please remove this version. Run Uninstall from the Eicon ISDN Tools folder in the Programs menu.

Do not install the Eicon ISDN software version on Microsoft BackOffice Small Business Server 4.5 Disc 1 under the \Drvlib\Netcard\X86\Wan\Diwan folder.

The DIVA ISDN configuration is also available from the Small Business Server Console: Click on Tasks and then select DIVA Configuration. From DIVA Configuration, you can find the information you need for ISDN, RAS, Fax and Modem emulation.

"DIVA" and "DIVA Server BRI-2M" are trademarks of Eicon Technology Corporation.

Information on Eicon Technology products and services is available from the Eicon Technology Web site at http://www.eicon.com (http://www.eicon.com) .

ISDN information can be found at the Eicon Technology ISDN site at http://www.isdnzone.com (http://www.isdnzone.com) .

Modem Sharing

The Modem Sharing Service Cannot Share TAPI Devices That Do Not Have a Serial-port Interface

The Modem Sharing service can only share serial ports or TAPI devices that use serial ports. Therefore, it cannot share TAPI devices that do not use a serial port, such as ISDN adapters. ISDN modems may be shared, as with any other device that connects to a serial port.

Modem Detection May Fail on a Shared Port

Modem detection may fail on a shared port if the modem is in use by another client, or by another application on the server. Wait until the modem becomes available, and try again, or install the modem manually.

Have Clients Disconnect if a Modem on Small Business Server is Occupied for an Extended Time and the Modem Appears Inactive

Modem-sharing clients that connect to Small Business Server allocate a modem on the server for exclusive use. The modem remains allocated as long as the client's application keeps the connection open. Modem-sharing connections are not timed out. If the user does not disconnect from the server or close the communication application, the modem remains inaccessible to other users. A common scenario is a client running a communication application that waits for an incoming call. This allocates a modem exclusively for this purpose and no one can use the modem as long as the communication application is waiting for a call.

Instruct users to disconnect the modem-sharing connection or terminate the communication application when they have finished using the shared modem.

Client Setup

Do Not Run Setup Computer Wizard Disk on a BDC

A backup domain controller (BDC) cannot be configured as a Small Business Server client computer. Do not run a Setup Computer Wizard disk on a BDC.

A Windows NT Server computer that has been configured as a stand-alone server can be a Small Business Server client.

A BDC can be set up in a Small Business Server network with full functionality; it just cannot be automatically configured using the setup disk generated using the Setup Computer Wizard.

Windows 95/98 Client Computer with a 3Com 3C905b Network Interface Adapter Can't Access the Small Business Server Computer

Some versions of the Windows 95/98 driver for the 3Com 3C905b network interface card may not function correctly in 32-bit NDIS mode. If you have this network card in a client computer, and you cannot see the server following the network configuration, you need to use the 16-bit NDIS mode.

To change NDIS modes:

1. On the client computer, click Start, point to Settings, click on Control Panel, and then double-click Network.
2. Select the network interface card, and then click Properties.
3. Click the Driver Type tab.
4. Select Real Mode (16 bit) NDIS driver.
5. Restart the computer.

Small Business Server Client Setup May Install Incorrect Intel Network Interface Card

If you have an Intel 82558 network interface card installed on your client computer, Small Business Server Client Setup will detect and install it as an Intel 82557 network interface card, which does not work.

To install the correct network interface card on a client computer, follow these steps.

Note Install the Intel 82558 network interface card on your client computer before you run Setup from the disk created using the Set Up Computer Wizard.

1. Click Start, point to Settings, click Control Panel, and then double-click Network.
2. Select the Configuration tab, and then click Add.
3. Click Adapter, and then click Add.
4. Click Have Disk, and insert the disk containing the network adapter driver.
5. Click OK, and follow the on-screen instructions to complete the installation.

Other Notes

Web Publishing Wizard Is Unable to Post Web Pages

If Proxy Server Dynamic Packet Filtering has been enabled, the Web Publishing Wizard will be unable to publish web pages. The following error will commonly be encountered: This error occurs because the Web Publishing Wizard uses FTP to post web pages. Dynamic Packet Filtering will block FTP. In order to publish using the Web Publishing Wizard, you must open the FTP ports.

To open the ports used by FTP:

1. Click Start, point to Programs, point to Microsoft Proxy Server, and then click Microsoft Management Console.
2. Expand Internet Information Server.
3. Expand the name of your Small Business Server computer.
4. Right-click Web Proxy and then click Properties.
5. Under Shared services, click Security.
6. On the Security page, click Add.
7. Select Custom Filter and then set the following options:

       Protocol ID   TCP
       Direction	  both
       Local Port	  any
       Fixed Port	  20
       Local Host	  Default proxy external IP address
       Remote Host	  any host

8. Click OK, and then click Add.
9. Select Custom Filter and then set the following options:

       Protocol ID	  TCP
       Direction	  both
       Local Port	  any
       Fixed Port	  21
       Local Host	  Default proxy external IP address
       Remote Host	  any host

10. Click OK three times.

Uninstalling SQL Server 7.0 May Cause the Content Indexer to Fail

Before you uninstall SQL Server 7.0, verify two registry values. Any time you modify registry values manually, you should first back up your system as a protection against inadvertently corrupting a critical entry.

Caution You should not edit your registry unless it is absolutely necessary. If there is an error in your registry, your computer may become nonfunctional. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information on how to restore the system registry, see "Restoring the Registry" in the online Help for Regedit.exe or "Restoring a Registry Key" in the online Help for Regedt32.exe.

To back up the WindowsNT registry to a tape drive:

1. Click Start, point to Programs, point to Administrative Tools (Common), and then click Backup.
2. On the Operations menu, click Backup. The Backup Information box will be displayed.
3. Select Backup Local Registry.

Note If the Backup Local Registry checkbox is not available, the hard drive that contains the registry has not been selected prior to opening the Backup Information box.

To check the Windows registry:

1. Click Start, click Run, type regedit.exe, and then click OK.
2. Expand HKEY_LOCAL_MACHINE.
3. Expand SOFTWARE.
4. Expand Microsoft.
5. Expand Windows.
6. Expand CurrentVersion.
7. Click on SharedDlls.
8. Scroll down the list until you find SystemDrive:\Winnt.sbs\System32\Qperf.dll.
9. The value in Data should be 2 or greater. If not, double-click SystemDrive:\Winnt.sbs\System32\Qperf.dll, change the value in the Value data box, and then click OK.
10. Find SystemDrive:\Winnt.sbs\System32\Query.dll. It should be just below Qperf.dll.
11. The value in Data should be 2 or greater. If not, double-click SystemDrive:\Winnt.sbs\System32\query.dll, change the value in the Value data box, and then click OK.
12. Close Registry Editor.
13. Uninstall SQL Server.

VBScript Runtime Error When Browsing Directories and Files in Internet Service Manager (HTML)

When using Internet Service Manager (HTML) to browse directories and files, you may receive the following error: To correct this error, replace the file Jsbrwls.asp located in the \Winnt\System32\Inetsrv\Iisadmin\Jsbrowser\ folder of your Small Business Server computer with the updated file located in the \Ntoptpak\Language\Platform\Winnt.srv\ folder of Small Business Server Disc 2.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: