Home

WAC 1806/1807 preview - the remote name could not be resolved 'aka.ms' on server 2016

%3CLINGO-SUB%20id%3D%22lingo-sub-221865%22%20slang%3D%22en-US%22%3EWAC%201806%2F1807%20preview%20-%20the%20remote%20name%20could%20not%20be%20resolved%20'aka.ms'%20on%20server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-221865%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20installed%20WAC%201806%20preview%20on%20a%202016%20server.%20In%20Chrome%20when%20I%20go%20to%20Settings%20-%20Extensions%20I%20get%20a%20popup%20saying%20%3A%20The%20remote%20name%20could%20not%20be%20resolved%3A'aka.ms'.%3C%2FP%3E%3CP%3EThe%20feed%20address%20is%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fsme-extension-feed%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fsme-extension-feed%3C%2FA%3E%20and%20if%20I%20open%20the%20page%20in%20Chrome%20it%20works%2C%20it%20is%20redirected%20here%20%3CA%20href%3D%22https%3A%2F%2Fmsft-sme.myget.org%2FF%2Fwindows-admin-center-feed%2Fapi%2Fv2%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsft-sme.myget.org%2FF%2Fwindows-admin-center-feed%2Fapi%2Fv2%3C%2FA%3E%20and%20I%20get%20an%20xml%20file.%3C%2FP%3E%3CP%3EThe%20server%20is%20accessing%20the%20Internet%20through%20a%20proxy.%3CBR%20%2F%3EI%20have%20the%20same%20problem%20from%20the%20WAC%20gateway%20or%20from%20any%20other%20clients%20connecting%20to%20it.%3C%2FP%3E%3CP%3EThe%20strange%20thing%20is%20that%20I%20have%20installed%20the%20same%20WAC%20version%20on%20my%20laptop%20(accessing%20the%20internet%20through%20the%20same%20proxy)%20and%20it%20is%20working%2C%20I%20get%20a%20list%20of%20available%20extensions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F38598i99718062A536FA8B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22wac1807-akams.png%22%20title%3D%22wac1807-akams.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20also%20upgraded%20to%201807%20and%20it's%20the%20same%20problem.%3C%2FP%3E%3CP%3EAny%20idea%20%3F%3CBR%20%2F%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276734%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%201806%2F1807%20preview%20-%20the%20remote%20name%20could%20not%20be%20resolved%20'aka.ms'%20on%20server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276734%22%20slang%3D%22en-US%22%3EThanks%20a%20lot%20%2C%20I%20will%20try%20and%20let%20u%20know.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276732%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%201806%2F1807%20preview%20-%20the%20remote%20name%20could%20not%20be%20resolved%20'aka.ms'%20on%20server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276732%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3ETo%20solve%20this%20I%20exported%20the%20proxy%20registry%20settings%20from%20my%20user%20and%20imported%20them%20into%20the%20Network%20Service%20user.%3C%2FP%3E%3CP%3EHere%20is%20what%20I%20have%20done%20%3A%3C%2FP%3E%3CP%3E1.%20Make%20sure%20your%20user%20is%20configured%20with%20the%20proxy%20and%20that%20you%20can%20access%20the%20internet.%3C%2FP%3E%3CP%3E2.%20Export%20the%20key%26nbsp%3B%3CFONT%3EHKEY_CURRENT_USER%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CInternet%20Settings%5CConnections%20to%20a%20reg%20file.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E3.%20Modify%20the%20reg%20file%20so%20that%20the%20key%20is%20%3A%26nbsp%3BHKEY_USERS%5CS-1-5-20%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CInternet%20Settings%5CConnections%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E4.%20Import%20the%20reg%20file%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E5.%20Restart%20the%20Windows%20Admin%20Center%20service%20(ServerManaementGateway)%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3EDone%20!%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EI%20hope%20this%20will%20help%20you%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3EMarc%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276731%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%201806%2F1807%20preview%20-%20the%20remote%20name%20could%20not%20be%20resolved%20'aka.ms'%20on%20server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276731%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20U%20explain%20%2C%20how%20did%20you%20fixed%20it%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-223615%22%20slang%3D%22en-US%22%3ERe%3A%20WAC%201806%2F1807%20preview%20-%20the%20remote%20name%20could%20not%20be%20resolved%20'aka.ms'%20on%20server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-223615%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20I%20found%20the%20solution%3B%20I%20had%20to%20set%20the%20proxy%20in%20the%20registry%20for%20the%20Network%20Service%20(S-1-5-20).%3C%2FP%3E%3CP%3ENow%20everything%20is%20ok.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMarc%3C%2FP%3E%3C%2FLINGO-BODY%3E
Marc Vanderhaegen
Contributor

I have installed WAC 1806 preview on a 2016 server. In Chrome when I go to Settings - Extensions I get a popup saying : The remote name could not be resolved:'aka.ms'.

The feed address is http://aka.ms/sme-extension-feed and if I open the page in Chrome it works, it is redirected here https://msft-sme.myget.org/F/windows-admin-center-feed/api/v2 and I get an xml file.

The server is accessing the Internet through a proxy.
I have the same problem from the WAC gateway or from any other clients connecting to it.

The strange thing is that I have installed the same WAC version on my laptop (accessing the internet through the same proxy) and it is working, I get a list of available extensions.

 

wac1807-akams.png

 

I have also upgraded to 1807 and it's the same problem.

Any idea ?
Thanks.

4 Replies

Ok, I found the solution; I had to set the proxy in the registry for the Network Service (S-1-5-20).

Now everything is ok.

 

Marc

Can U explain , how did you fixed it??

Hello,

To solve this I exported the proxy registry settings from my user and imported them into the Network Service user.

Here is what I have done :

1. Make sure your user is configured with the proxy and that you can access the internet.

2. Export the key HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections to a reg file.

3. Modify the reg file so that the key is : HKEY_USERS\S-1-5-20\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections

4. Import the reg file

5. Restart the Windows Admin Center service (ServerManaementGateway)

Done !

 

I hope this will help you

Marc

 

 

Thanks a lot , I will try and let u know.
Related Conversations