Quantcast
Channel: VMware Communities : Unanswered Discussions - Workstation Pro
Viewing all articles
Browse latest Browse all 11358

Unexpected behaviour of WinAPI function WinHttpGetIEProxyConfigForCurrentUser on virtual machine on VMware® Workstation

$
0
0

Hi,

 

I met problem. WinAPI function returns different result on in Windows working on real hardware and on VMware® Workstation. I use version 9.0.1.

I tested on host OS: Windows 7 Ultimate SP1 32 and 64 bit as well.

 

I tested using following console application:

 

#include <windows.h>

#include <winhttp.h>

 

#include <iostream>

 

#pragma comment( lib, "Winhttp.lib" )

 

int _tmain(int argc, _TCHAR* argv[])

{

    WINHTTP_CURRENT_USER_IE_PROXY_CONFIG ie_proxy_cfg;

    BOOL res = WinHttpGetIEProxyConfigForCurrentUser(&ie_proxy_cfg);

 

    std::cout << "res: " << res << " fAutoDetect: " << ie_proxy_cfg.fAutoDetect << std::endl;

 

    return 0;

}

 

 

As result I have got different values for the field fAutoDetect and so different output on real hardware and on virtual machine:

I know, that value of this field is relate to the selection of the check-box "Automatically detect settings" of the dialog box "Local Are Network (LAN) Settings" called from the Internet Option dialog.

I have the same settings. This check-box is checked in both cases.

Lan_Settings.png

And I've tested with IE 9 and IE 11.

 

real hardware:

res: 1 fAutoDetect: 1

 

virtual machine:

res: 1 fAutoDetect: 0

 

My questions:

Is it as designed functionality or bug? I suggested that VMWare tools do something here, don't it?

If it is as designed then another question: is it configurable?

 

Thanks in advance for the answer,


Viewing all articles
Browse latest Browse all 11358

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>