I'm trying to set up an environment to compile workbench, to test the change.Īny help? Is there another way to create this server instance? Or just a workaround? I really don't know if this is a bug or is just a consequence of the logic used for domain login. This is explained in the API reference (). It should be call with a SEC_WINNT_AUTH_IDENTITY_EX or SEC_WINNT_AUTH_IDENTITY in the pAuthInfo parameter, on the first call (line 322 in wmi.cpp). I don't know much about DCOM programming, but I think that the problem is in CoSetProxyBlanket. HRESULT hr = _services->ExecQuery(L"WQL", converted_query, WBEM_FLAG_FORWARD_ONLY, NULL, &enumerator) Wmi_result = module->call_function("wmiQuery", arguments) I suppose it is an exception rised from line: The exception becomes an error message in WindowsManagementPage::enter in new_server_instance_wizard.cpp (from frontend/common). I've found the error message in the WmiServices::query method in wmi.cpp (from backend/wbprivate/workbench). I've looked at the workbench source code (for 5.2.42). It is clear that the second authentication information is wrong. So the server sends a "Fault" response, telling access is denied (the status is nca_s_fault_access_denied). The authentication is performed in a previous AUTH3 packet with as the domain name and the local username in the username field. In the second socket (the one opened by the endpoint mapper), I can see the IWbemServices Request (with the WQL query in the payload). In this first authentication, is used for the domain name and the previously entered is sent. The request message (RemoteCreateInstance) is accepted and the second socket (used in RPC) is opened. The session is opened correctly: I can see the correct authentication Using \ for the authentication, I can see the DCERPC transaction. I've analyzed the problem with wireshark. If I use \ in the username field, I get the message: "Could not set up connection: WMI query execution failed with this error: access denied". If I use in the username field, I get the message: "Could not set up connection: Could not connect to target machine"Īlso, I can see the authentication failure in the security log in the server machine * Used the administrator account for all this tests. * Remote WMI tested and working: wmic works well with any query (using /node, /user and /password switches) The problem appears setting up remote management. * The connection to the database is created fine. The test environment is composed of two windows xp: I'm trying to create a new server instance in workbench, using windows native remote management, with no success.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |