WinRM does not respond to an authentication challenge by sending credentials on a Windows Server 2003 R2-based computer (912030)
The information in this article applies to:
- Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
- Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Enterprise x64 Edition
- Microsoft Windows Server 2003 R2 Standard x64 Edition
- Microsoft Windows Server 2003 R2 Datacenter x64 Edition
SYMPTOMSConsider the following scenario: - You send a request from a Microsoft Windows Server 2003 R2-based computer to a remote server by using the Windows Remote Management (WinRM) command-line tool. (WinRM is the Microsoft implementation of the WS-Management protocol.)
For example, you type the following request: winrm operation http://Server_Name/wsman - The remote server responds by sending a http 302 status code to http://Server_Name/wsman/. A trailing slash is included at the end of the requested URL.
- The WS-Management protocol repeats the request to the redirected URL.
- The remote server responds by sending a 401 authentication challenge.
In this scenario, WinRM does not respond to the authentication challenge by sending credentials. WORKAROUNDTo work around this behavior, use the -prefix switch with the WinRM command to add a trailing slash (/) to the URL. For example, type the following command to add a trailing slash (/) to http:// Server_Name/wsman: winrm operation -machine:Server_Name -prefix:wsman/ ResourceURI STATUS
This behavior is by design.REFERENCESFor more information about the WS-Management protocol, visit the following Microsoft Web site: For more information about WinRM, visit the following Microsoft Web site:
Modification Type: | Minor | Last Reviewed: | 2/17/2006 |
---|
Keywords: | kbwinservsetup kbtshoot kbprb KB912030 kbAudITPRO |
---|
|