Alex's Blog

Coffee, Code & more

Posted PowerShell

Here a quick ‘how to’ connect to a remote server via PowerShell that is not joined to a domain.

**

On remote server:

** 1. Make sure the Windows Remote Management (winrm) service is running

# Get the status of the winrm service
Get-Service winrm
# If it not running, start the service
Start-Service winrm
# Also set the service to start automatically (Delayed Start)
Set-Service "winrm" -StartupType Automatic
# Enable winrm 
winrm quickconfig
  1. Make sure your network connection type is private
# To see if it's set to private or not run this
Get-NetConnectionProfile
# To set it to Private, run this (as admin)
Set-NetConnectionProfile -NetworkCategory Private
  1. Enable PowerShell remoting
Enable-PSRemoting -Force

**

On local computer:

**

  1. Make sure the Windows Remote Management (winrm) service is running
# Get the status of the winrm service
Get-Service winrm
# If it not running, start the service
Start-Service winrm
# Also set the service to start automatically (Delayed Start)
Set-Service "winrm" -StartupType Automatic
  1. Add the ‘remote server’ to the trusted host list
# Add your 'remote server's' IP to the trusted host list
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "192.168.1.1" -Force
# Or if IPs are constantly changing, add ALL IPs (* is the wildcard)
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*" -Force
# Check and make sure the right value is in the trusted host list
Get-Item WSMan:\localhost\Client\TrustedHosts
# To clear the trusted host list, run this
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "" -Force

 

Connect to your remote server:

# If you are in CLI
Enter-PSSession -ComputerName 192.168.1.1 -Credential Get-Credential
# If you are in the ISE
$credential = Get-Credential
Enter-PSSession -ComputerName 192.168.1.1 -Credential $credential

If everything went right, you should see a prompt showing the remote PC IP

# e.g. like this:
[192.168.1.1]: PS C:\Users\Administrator>

 

 

 

Posted Linux

Now we have CentOS 7 minimal installed and the IP configured, first thing we want to do is upgrade ( update + enable obsoletes processing during updates)

yum update && yum upgrade

If you find the prompt for  ‘Do you want to install those blah blah’ annoying, do this:

yum -y update && yum -y upgrade

It is however always a good idea to check and see what is actually getting updated.

Next we want to install telnet:

yum install telnet -y

 

 

Posted Linux

Being new to Linux, settings things up in CentOS it’s pain in the arse :o) Here some things I learned. If you have more than a few months Linux experiences, there might be nothing new for you here…

IFCONFIG does not work…

Apparently ifconfig has been depreciated. You can still install the package if needed:

yum -y install net-tools

It’s new replacement is IP

ip a

If you want to learn more about it just use

ip help

Another way to setup IPs etc, I found handy are:

# List installed ethernet cards
nmcli d 

# Open NetworkManager 
nmtui

# Set static IP
# e.g. "nmtui edit eth0"
nmtui edit <connection>

# Restart Network service after setting IP as needed
service network restart

 

 

Posted FYI

MSFT is again giving away free ebooks.

If you interested, please go here.

Happy downloading :o)

Posted AWS, Networking, SonicWall

Today we are setting up a VPN between an onsite SonicWall and AWS.

  1. Log into your AWS account and navigate to your VPC
  2. vpn01Scroll down and navigate to VPN Connections -> Customer Gateways
  3. Click on Create Customer Gateway
  4. Name it, configure the routing and assign it the external IP address of your SonicWall (IP of the WAN interface)
[<img class="aligncenter size-full wp-image-348" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn02.png" alt="vpn02" width="715" height="344" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn02.png 715w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn02-300x144.png 300w" sizes="(max-width: 715px) 100vw, 715px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn02.png)   5. Navigate to **VPN Connections** -> **Virtual Private Gateways** and create a new Virtual Private Gateway and attach it to the VPC
  
[<img class="aligncenter size-full wp-image-349" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn03.png" alt="vpn03" width="592" height="165" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn03.png 592w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn03-300x84.png 300w" sizes="(max-width: 592px) 100vw, 592px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn03.png)   6. Navigate to **VPN Connections** -> **VPN Connections

** Create a new VPN Connection.

[<img class="aligncenter size-full wp-image-350" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn04.png" alt="vpn04" width="736" height="385" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn04.png 736w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn04-300x157.png 300w" sizes="(max-width: 736px) 100vw, 736px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn04.png)   7. Go to ‘Route Tables’ and add the private local route
  
[<img class="aligncenter size-full wp-image-352" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn05.png" alt="vpn05" width="821" height="375" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn05.png 821w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn05-300x137.png 300w" sizes="(max-width: 821px) 100vw, 821px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn05.png)   8. If all worked fine so far, go back to **VPN Connections** and download the Config File for the SonicWall. It has to the generic one as there is no specific one for SonicWall.
  
[<img class="aligncenter size-full wp-image-353" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn06.png" alt="vpn06" width="699" height="345" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn06.png 699w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn06-300x148.png 300w" sizes="(max-width: 699px) 100vw, 699px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn06.png)   9. You are done in AWS for now. **Take a coffee brake&#8230;** :o)  10. Log into your SonicWall and navigate to:
  
**VPN** -> **Settings** -> **VPN Policies** -> **Add&#8230;**  11. <table>
  <tr>
    <td>
      Setup a VPN:<br /> IPSec Primary Gatey: AWS Tunnel 1 IP<br /> Shared Secret, see downloaded generic documentation (open in word!)<br /> Local IKE: Ext IP from Sonicwall<br /> Peer IKE: Same as IPSec Gateway
    </td>
  </tr>
</table>

[<img class="aligncenter size-full wp-image-355" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn07.png" alt="vpn07" width="638" height="408" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn07.png 638w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn07-300x192.png 300w" sizes="(max-width: 638px) 100vw, 638px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn07.png)</li> 

  * Setup the proposal accordingly:
  
    [<img class="aligncenter size-full wp-image-356" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn08.png" alt="vpn08" width="623" height="476" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn08.png 623w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn08-300x229.png 300w" sizes="(max-width: 623px) 100vw, 623px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn08.png)
  * Setup the Advances settings accordingly:
  
    [<img class="aligncenter size-full wp-image-357" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn09.png" alt="vpn09" width="644" height="413" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn09.png 644w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn09-300x192.png 300w" sizes="(max-width: 644px) 100vw, 644px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn09.png)
  * Go to **VPN** -> **Advanced** and disable **NAT Traversal**
  
    [<img class="aligncenter size-full wp-image-358" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn10.png" alt="vpn10" width="402" height="169" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn10.png 402w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn10-300x126.png 300w" sizes="(max-width: 402px) 100vw, 402px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn10.png)
  * Go to **Network** -> **Routing** and configure a new router for the VPN.
  
    [<img class="aligncenter size-full wp-image-359" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn11.png" alt="vpn11" width="386" height="417" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn11.png 386w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn11-278x300.png 278w" sizes="(max-width: 386px) 100vw, 386px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn11.png)
  * Go to **Firewall **-> **Access Rules** and create a new rule for the AWS VPN
  
    (**VPN** -> **LAN** and **LAN** -> **VPN)**
  
    [<img class="aligncenter size-full wp-image-360" src="http://blog.vvittig.com/wp-content/uploads/2015/11/vpn12.png" alt="vpn12" width="347" height="343" srcset="https://blog.vvittig.com/wp-content/uploads/2015/11/vpn12.png 347w, https://blog.vvittig.com/wp-content/uploads/2015/11/vpn12-300x297.png 300w" sizes="(max-width: 347px) 100vw, 347px" />](http://blog.vvittig.com/wp-content/uploads/2015/11/vpn12.png)
  * Check in both AWS and SonicWall that the tunnel is up and check the firewalls. Once that is done start pinging from local to AWS and vice versa to confirm all is good. 
    All done :o)</li> </ol>