Knowledge Base

Scheduled RASDIAL Fails To Connect to Windows NT RAS Server

Article ID: 147711

Article Last Modified on 11/1/2006

APPLIES TO

This article was previously published under Q147711

SYMPTOMS

When you use the Windows NT Scheduler Service and schedule RASDIAL.EXE to automatically connect to a Windows NT Remote Access Service (RAS) server, the following symptoms occur if you do not specify a user account for the RASDIAL command:
  • The Windows NT RAS server disconnects the Windows NT RAS client during authentication.
  • If you schedule the RASDIAL command to run interactively (with the /INTERACTIVE switch) in the MS-DOS Command Prompt (CMD.EXE), the CMD window stops responding (hangs).
  • The system that scheduled the RASDIAL command may become unstable and you may not be able to start new applications.

CAUSE

When you do not specify a user account in RASDIAL, RASDIAL uses the current user name and password. By default, the Scheduler service logs on with the System account. Therefore, if you do not change the "Log On As" account for the Scheduler service and you do not specify a user name and password on the RASDIAL command line, the scheduled RASDIAL command uses the System account when it attempts to connect to the Windows NT RAS server. If the System account is used, the symptoms mentioned above occurs.

RESOLUTION

To correct this problem, do one of the following:
  • Enter a user name and password as parameters on the RASDIAL command line in the following format:

    RASDIAL <Entry Name> <User Name> <Password>

    The user name you specify must have RAS dial-in permission on the RAS server.

    -or-
  • Change the "Log On As" account for the Scheduler service to an account other than the System account. The account that you select must have RAS dial-in permission on the Windows NT RAS server.

Additional query words: prodnt

Keywords: kbnetwork KB147711


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.