Microsoft KB Archive/912030

= WinRM does not respond to an authentication challenge by sending credentials on a Windows Server 2003 R2-based computer =

Article ID: 912030

Article Last Modified on 5/8/2007

-

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

-





SYMPTOMS
Consider 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  http:// /wsman

 The remote server responds by sending a http 302 status code to http:// /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.



WORKAROUND
To 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:// /wsman:

winrm  -machine:  -prefix:wsman/



STATUS
This behavior is by design.

