"Access Denied" When You Run AT Command on Remote Computer

Last reviewed: November 13, 1997
Article ID: Q151308
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

When you run AT on a remote computer, it can result in an "access denied" error.

CAUSE

This error condition occurs because you do not have the correct access privileges. Administrative privileges are required for remote AT activity.

MORE INFORMATION

Assume a user issues an AT command on a remote computer. For example, from computer A, UserA issues the command

   <AT \\computerB 18:00 /interactive "notepad">

This has the following two results:

  1. ComputerA will try to establish an IPC$ connection to ComputerB, using the account UserA. The Server Message Block (SMB) command is <C session setup & X, and C tree connect & X, Share = \\computerB\IPC$>. UserA must have administrative privileges, otherwise the attempt results in an "access denied" error.

  2. Schedule will start up on ComputerB using the account you specified with the Schedule service in the Services tool in Control Panel. By default, it uses the System account.


Additional query words: AT
Keywords : ntnetserv NTSrvWkst kbnetwork
Version : 3.5 3.51
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 13, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.