Microsoft Knowledge Base

• Microsoft Windows NT Server version 3.5
• Microsoft LAN Manager version 2.2c
• Microsoft Network Client for MS-DOS, version 3.0

SYMPTOMS

In order for applications to start the UDP services in LAN Manager version 2.2c (both MS-DOS and OS/2 versions) or Network Client for MS-DOS, the applications must use the Microsoft TCP/IP protocol and read the SERVICES file. The SERVICES file allows the application to find assigned UDP ports, and it is included in the Windows NT Server version 3.5 CD. However, the applications are not able to read the entire SERVICES file.

CAUSE

There is an incorrect entry in the SERVICES file included on the Windows NT Server version 3.5 CD. If a space is detected for the service name in the SERVICES file, the parser stops reading the file. The SERVICES file includes the following:

   erlogin         888/tcp         # Login and environment
   passing kpop    1109/tcp        # Pop with Kerberos

WORKAROUND

To work around this problem, use a text editor to modify the SERVICES file so that it reads:

   erlogin         888/tcp         # Login and environment passing
   kpop            1109/tcp        # Pop with Kerberos

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.