The Windows runas command and the /netonly switch

This content is 16 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier today I needed to administer a Windows Server remotely, using a Microsoft Management Console (MMC) snap-in. Unfortunately, the computer I was using was in one domain and the remote server was in a workgroup, meaning that many of the MMC operations failed due to security issues. I tried running MMC as the administrator for the remote machine (using runas /user:remotecomputername\username mmc) but kept on getting a message that indicated an authentication failure:

RUNAS ERROR: Unable to run – mmc
1311: There are currently no logon servers available to service the logon request.

Then I found out about an obscure switch for the runas command – /netonly, used to indicate that the supplied credentials are for remote access only. By changing my command to:

runas /netonly /user:remotecomputername\username mmc

I was able to authenticate against the remote computer without needing the credentials to also be valid on the local computer, as described by Craig Andera.

3 thoughts on “The Windows runas command and the /netonly switch

  1. Hi,
    I have a vista machine in a workgroup, and a 2008 machine in a workgroup. Using this command on the vista machine, logging in with the 2008 credentials does not allow the use of remote mmc consoles to connect to 2008 successfully.

  2. I used this method to connect to SQL Server Analysis Serives from a local computer using EXCEL 2010. Same principle exactly. I posted what I did on my blog.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.