XFOR: Using the Broker Simulator to Authenticate Mail Services (163866)



The information in this article applies to:

  • Microsoft Commercial Internet System 1.0

This article was previously published under Q163866
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SUMMARY

By default, the Broker Simulator will not authenticate Mail services via DPA (or any other use requiring the Member_Name_SVC token). This article documents how to modify the Broker Simulator so it can authenticate Mail services.

MORE INFORMATION

The modifications that need to be made are in two of the .csv (Comma Separated Value) files, which are installed as part of the Broker Simulator. These files are Icpdb.csv and Tokendb.csv.

In Tokendb.csv, add the following line:

5843,Member_Name_SVC

In Icpdb.csv, modify the line for the Broker account that you are using to include the following data:

Member_Name_SVC:7

(NOTE: Most Broker Simulator installations use the Birds broker account by default. If you are not certain which account you used, you can find out by opening the Broker Administration tool, and clicking the Broker ID tab.)

The following registry key must also be changed:
   HKLM\System\CurrentControlSet\Services\Pop3Svc\Parameters
				
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

By default, the following registry key should read NTLM. Modify the key so it reads DPA and NTLM.
   NTAuthenticationProviders
				
When these steps are completed, stop and restart the Simulator service, the Broker service, and the POP3 service. (This can also be done by restarting the computer, which will also show you any event errors if there are any.)

DPA authentication should now work (server side). Remember that you must be using a DPA enabled client (Athena) as well.

Modification Type:MajorLast Reviewed:9/30/2003
Keywords:KB163866