Problem Connecting WAC Gateway to Itself

%3CLINGO-SUB%20id%3D%22lingo-sub-278070%22%20slang%3D%22en-US%22%3EProblem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278070%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20login%20to%20WAC%20without%20issue.%20I%20can%20connect%20to%20ANY%20server%20in%20my%20domain%20without%20issue...%20except%20for%20the%20WAC%20gateway%20server%20itself.%20When%20I%20try%2C%20I%20receive%20constant%20authentication%20prompts%20and%20the%20following%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3EConnecting%20to%20remote%20server%20wac01%20failed%20with%20the%20following%20error%20message%20%3A%20The%20WS-Management%20service%20cannot%20process%20the%20request.%20Cannot%20find%20the%20microsoft.sme.powershell%20session%20configuration%20in%20the%20WSMan%3A%20drive%20on%20the%20wac01%20computer.%20For%20more%20information%2C%20see%20the%20about_Remote_Troubleshooting%20Help%20topic.%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20other%20issues%20with%20this%20server%2C%20and%20I%20do%20not%20have%20any%20issues%20connecting%20from%20others%20using%20WinRM%20commands%20either.%20Any%20thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364191%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364191%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20i%20had%20to%20use%20UPN%20format%20as%20the%20username%20rather%20than%20Domain%5Cusername.%26nbsp%3B%20The%20fix%20mentioned%20coming%20in%20the%20next%20release%2C%20is%20it%20in%20the%201812%20preview%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20some%20situations%20i%20found%20removing%20the%20domain%20from%20the%20FQDN%20in%20the%20address%20also%20fixed%20the%20problem%20on%20some%20machines%20when%20connecting.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364023%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364023%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%26nbsp%3B%3CSPAN%3Etried%20providing%20my%20credentials%20with%20the%26nbsp%3B%3C%2FSPAN%3E%3CEM%3E%3CSTRONG%3EManage%20As%26nbsp%3B%3C%2FSTRONG%3E%3C%2FEM%3E%3CSPAN%3Eoption%20before%20I%20tried%20to%20connect.%20It%20didn't%20work...%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22Connecting%20to%20remote%20server%20mediapc%20failed%20with%20the%20following%20error%20message%20%3A%20The%20WS-Management%20service%20cannot%20process%20the%20request.%20Cannot%20find%20the%20microsoft.sme.powershell%20session%20configuration%20in%20the%20WSMan%3A%20drive%20on%20the%20mediapc%20computer.%20For%20more%20information%2C%20see%20the%20about_Remote_Troubleshooting%20Help%20topic.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328102%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328102%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20believe%20we%20found%20the%20root%20cause%20of%20this%20behavior.%20The%20fix%20should%20be%20available%20in%20the%20next%20Windows%20Admin%20Center%20release%2C%20currently%20planned%20for%20late%20February.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20meantime%2C%20as%20a%20workaround%2C%20try%20providing%20your%20credentials%20with%20the%20%3CEM%3E%3CSTRONG%3EManage%20As%3C%2FSTRONG%3E%3C%2FEM%3E%20option%20before%20you%20try%20to%20connect.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284292%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284292%22%20slang%3D%22en-US%22%3E%3CP%3EHmm%2C%20interesting.%20Let%20me%20check%20that%20and%20I'll%20report%20back.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281674%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281674%22%20slang%3D%22en-US%22%3EI%20had%20this%20same%20error%20this%20morning%20but%20it%20wasn't%20a%20WAC%20gateway%2C%20just%20a%20regular%20server.%20The%20remote%20registry%20service%20was%20stopped.%20After%20starting%20it%20I%20was%20able%20to%20connect.%20Hope%20that%20helps.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281219%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281219%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20response.%20Unfortunately%2C%20this%20had%20no%20effect%20on%20the%20problem%20I%20presented.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280565%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280565%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ETo%20rid%20out%20of%20constant%20authentication%20prompts%20you%20can%20try%20modifying%20internet%20settings%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EInternet%20properties-%20Securities-%20add%20the%20(WAC%20local%20host%20site%20or%20the%20website%20you%20used%20to%20access%26nbsp%3BWAC)%20in%20trusted%20site%20and%20set%20security%20level%20to%20low-%20close%20the%20browser%20and%20try%20again.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-279728%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-279728%22%20slang%3D%22en-US%22%3E%3CP%3EUnfortunately%2C%20no%20I%20haven't...%20I%20haven't%20found%20any%20documentation%20of%20others%20having%20this%20or%20how%20to%20resolve%20it.%20I%20came%20here%20hoping%20that%20someone%20might%20have%20come%20across%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278914%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20Connecting%20WAC%20Gateway%20to%20Itself%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278914%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Aaron%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20having%20the%20same%20issue.%20Have%20you%20discovered%20a%20solution%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I can login to WAC without issue. I can connect to ANY server in my domain without issue... except for the WAC gateway server itself. When I try, I receive constant authentication prompts and the following:

 

Connecting to remote server wac01 failed with the following error message : The WS-Management service cannot process the request. Cannot find the microsoft.sme.powershell session configuration in the WSMan: drive on the wac01 computer. For more information, see the about_Remote_Troubleshooting Help topic.

 

I have no other issues with this server, and I do not have any issues connecting from others using WinRM commands either. Any thoughts?

9 Replies
Highlighted

Hi Aaron,

 

I'm having the same issue. Have you discovered a solution?

Highlighted

Unfortunately, no I haven't... I haven't found any documentation of others having this or how to resolve it. I came here hoping that someone might have come across it.

Highlighted

To rid out of constant authentication prompts you can try modifying internet settings:

Internet properties- Securities- add the (WAC local host site or the website you used to access WAC) in trusted site and set security level to low- close the browser and try again.

Highlighted

Thanks for the response. Unfortunately, this had no effect on the problem I presented.

Highlighted
I had this same error this morning but it wasn't a WAC gateway, just a regular server. The remote registry service was stopped. After starting it I was able to connect. Hope that helps.
Highlighted

Hmm, interesting. Let me check that and I'll report back.

Highlighted

We believe we found the root cause of this behavior. The fix should be available in the next Windows Admin Center release, currently planned for late February.

 

In the meantime, as a workaround, try providing your credentials with the Manage As option before you try to connect.

Highlighted

I had tried providing my credentials with the Manage As option before I tried to connect. It didn't work...

 

"Connecting to remote server mediapc failed with the following error message : The WS-Management service cannot process the request. Cannot find the microsoft.sme.powershell session configuration in the WSMan: drive on the mediapc computer. For more information, see the about_Remote_Troubleshooting Help topic."

Highlighted

I found i had to use UPN format as the username rather than Domain\username.  The fix mentioned coming in the next release, is it in the 1812 preview?

 

Also some situations i found removing the domain from the FQDN in the address also fixed the problem on some machines when connecting.

 

Thanks