Quantcast
Channel: Configuration & Scripting
Viewing all articles
Browse latest Browse all 780

My IIS server does not handle wsman request. My WSMAN request keeps going to Microsoft HTTPAPI/2.0

$
0
0

I have set up both winrm and wmi on the servers. They are both running on windows OS. One is a windows 7 and the other is a windows 2012 server. I used nodejs to test that the winrm is properly configured. I can get host information output on nodejs remotely from one server to another. I am facing the same origin issue when I try to go through a web browser. I have set up cors on the iis server but I am still getting the no access-control-allow-origin header. This is because the wsman request I am sending is going to Microsoft httpapi/2.0 every time I send the request using the http://ipaddress:portNumber/wsman in the xmlhttprequest ".open" method but if i remove the "/wsman" part then the request goes to the iis server and I get the access-control-allow-origin header which makes sense because I added it. However, I do not get the wsman response I want because I didn't specify the ApplicationName (/wsman). I am using the SOAP API to send these requests btw.

Thanks


Viewing all articles
Browse latest Browse all 780

Latest Images

Trending Articles



Latest Images