This project has moved. For the latest updates, please go here.

Connect-As doesn't seem to work correctly.


I use File=>Connect As... to connect to a server in a different domain. The initial connection seems to work and I can see the Namespaces tree. However; attempting to enumerate classes for ANY of the namespaces always results in an Access is denied error.

I can write my own WMI script, connect and enumerate classes using the same user without any issues.


vinpa wrote Mar 19, 2015 at 10:08 PM

Hey gcpeters, can you connect to the server in remote domain using the NetBIOS name from wbemtest? After the initial connection, I get the path to the objects from WMI itself instead of constructing it myself and the path in WMI is stored with the NetBIOS name, so if the server in remote domain is not reachable via NetBIOS name, it would likely be the reason why you're unable to connect.

PNovikov wrote Dec 13, 2016 at 11:11 AM

I've just tested it and yeah - node should be resolvable through NetBIOS. But there's, for example, a networks for testing purposes and so on, where this is a normal behavior. Besides, it's pretty strange that you're allowing to connect to node through IP.

IMHO it would be nice to have at least an option to change this behavior...