tag:blogger.com,1999:blog-2496415891665263000.post9030724881001732060..comments2023-10-12T13:08:57.828+02:00Comments on For the Love of Software: Nano Server on AWS: Step by StepHesham A. Aminhttp://www.blogger.com/profile/00063404912692423973noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-2496415891665263000.post-28610507602285304512018-02-18T11:30:32.646+02:002018-02-18T11:30:32.646+02:00@Peshawar Air Services
I used the public IP addres...@Peshawar Air Services<br />I used the public IP address to connect to the instance. You can find it in the EC2 instance details in the AWS console.Hesham A. Aminhttps://www.blogger.com/profile/00063404912692423973noreply@blogger.comtag:blogger.com,1999:blog-2496415891665263000.post-21945997157337340852018-02-17T06:35:32.901+02:002018-02-17T06:35:32.901+02:00where to get computer namewhere to get computer nameShahzadKhanhttps://www.blogger.com/profile/00620991150750804224noreply@blogger.comtag:blogger.com,1999:blog-2496415891665263000.post-22678063380167180442017-07-16T20:59:12.271+02:002017-07-16T20:59:12.271+02:00Not sure why anybody would even want to use IIS gi...Not sure why anybody would even want to use IIS given a choice or IIS on a Nano Server but I would recommend just following the relatively clear and comprehensive AWS documentation. <br /><br />Sorry to say there's nothing "great" or "marvelous" or a "great addition" about regurgitating some AWS material. I really wish people would reserve praise for praiseworthy contributions, not a copy-paste job. Unknownhttps://www.blogger.com/profile/03192734588840536479noreply@blogger.comtag:blogger.com,1999:blog-2496415891665263000.post-9585260967283545992017-05-13T22:29:33.244+02:002017-05-13T22:29:33.244+02:00This comment has been removed by a blog administrator.Anonymoushttps://www.blogger.com/profile/00248296275628982891noreply@blogger.comtag:blogger.com,1999:blog-2496415891665263000.post-68448080387866423452017-03-23T12:05:26.804+02:002017-03-23T12:05:26.804+02:00@Anonymous
These are some troubleshooting steps:
-...@Anonymous<br />These are some troubleshooting steps:<br />-Make sure you're using the public IP not the internal IP?<br />-try "telnet xxx.xxx.xxx.xxx 5985" and observe the result<br />-Double check your security group setting.<br />-Make sure the problem is not with your corporate firewall.Hesham A. Aminhttps://www.blogger.com/profile/00063404912692423973noreply@blogger.comtag:blogger.com,1999:blog-2496415891665263000.post-48000896408872020372017-03-22T18:12:27.332+02:002017-03-22T18:12:27.332+02:00I followed your instructions but when attempting t...I followed your instructions but when attempting to connect to the Nano Server instance, I get the following error:<br /><br />PS C:\> Enter-PSSession -ComputerName $ip -Credential "~\Administrator"<br />Enter-PSSession : Connecting to remote server xxx.xxx.xxx.xxx failed with the following error message : WinRM <br />cannot complete the operation. Verify that the specified computer name is valid, that the computer is <br />accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access <br />from this computer. By default, the WinRM firewall exception for public profiles limits access to remote <br />computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.<br />At line:1 char:1<br />+ Enter-PSSession -ComputerName $ip -Credential "~\Administrator"<br />+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br /> + CategoryInfo : InvalidArgument: (xxx.xxx.xxx.xxx:String) [Enter-PSSession], PSRemotingTransportExc <br /> eption<br /> + FullyQualifiedErrorId : CreateRemoteRunspaceFailed<br /><br /><br />I've checked it is in the trustedhosts.<br /><br />PS C:\> Get-Item WSMan:\localhost\Client\TrustedHosts<br /><br /><br /> WSManConfig: Microsoft.WSMan.Management\WSMan::localhost\Client<br /><br />Type Name SourceOfValue Value <br />---- ---- ------------- ----- <br />System.String TrustedHosts xxx.xxx.xxx.xxx <br /><br />And PINGing the server results in timeout:<br /><br />PS C:\> ping $ip<br /><br />Pinging xxx.xxx.xxx.xxx with 32 bytes of data:<br />Request timed out.<br />Request timed out.<br />Request timed out.<br />Request timed out.<br /><br />Ping statistics for xxx.xxx.xxx.xxx:<br /> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),<br /><br />NOTE: I have masked my IP address in the statements above.<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2496415891665263000.post-67297289683497157502016-11-10T16:06:49.976+02:002016-11-10T16:06:49.976+02:00The AMI id differs from a region to another. The r...The AMI id differs from a region to another. The region I used is Frankfurt. and the image name was "Microsoft Windows Server 2016 Base Nano" with description: "Microsoft Windows 2016 Datacenter Edition Nano. [English]".Hesham A. Aminhttps://www.blogger.com/profile/00063404912692423973noreply@blogger.comtag:blogger.com,1999:blog-2496415891665263000.post-74657305460594227172016-11-10T07:52:13.107+02:002016-11-10T07:52:13.107+02:00Thanks for your post. I tried to replicate unsuces...Thanks for your post. I tried to replicate unsucessfully. I did exactly as specified but still I could not connect to the server using WinRM.<br /><br />The differences I noted were that I could not find the AMI with that id (ami-e4e61f8b) and could not find a 'Datacenter Edition' of Nano.Fletcher Bushhttps://www.blogger.com/profile/05480814802430275260noreply@blogger.com