Friday, January 10, 2014

Enable Ping on Windows Server 2012

This post will show you how to Enable Ping on Windows Server 2012

Ping is disabled by default and therefore must be allowed through the firewall before the host can be pinged.


Enable Ping in Windows Firewall

  • Right Click the Network icon in the task bar and select Open Network and Sharing Center

  • Network and Sharing Center: In the bottom left corner of the windows Click Windows Firewall

  • Windows Firewall: Click Advanced Settings


  • Windows Firewall with Advanced Security: Click Inbound Rules


  • Windows Firewall with Advanced Security: Right Click File and Printer Sharing (Echo Request - ICMPv4-In)


  • Windows Firewall with Advanced Security: Click Enable Rule


  • There will now be a green check mark next to the rule indicating that it is enabled.  Ping will now be allowed to the host
This concludes Enable Ping on Windows Server 2012.

I hope this was helpful and informative to you and I would appreciate any feedback you may have.


How to Install a Software Router on Windows Server 2012 Part 2

This post will be the final post on installing a Software Router on Windows Server 2012.  Here we will configure our static routes and test our configuration.

We left off on our previous post with the basic network configuration and installation of our Software Router on Windows Server 2012.  We will continue from our last post by launching the Getting Started Wizard to configure our router.



  • After clicking the link to the getting started wizard you will probably find that nothing happened and the notification cleared and went to a completed action.  So, we will just launch the router from the tools menu from here on out because there seems to be an issue launching the Wizard from the notification icon  

Initializing the Software Router in Windows Server 2012


  • Launch the Routing and Remote Access MMC by clicking on the Tools menu from Server Manager and Click Routing and Remote Access

  • Routing and Remote Access:  Right-click the Computer Name  and select Configure and Enable Routing and Remote Access
    • This will launch the wizard that previously failed to launch
  • Routing and Remote Access Server Setup Wizard: Click Next
  • Configuration: Select Custom Configuration and Click Next
  • Custom Configuration: Check the LAN routing box and Click Next
  • Completing the Routing and Remote Access Server Setup Wizard: Click Finish
    • This will launch a new window asking to start the routing service.  Click Start service

Configuring Routes from Routing and Remote Access in Windows Server 2012

After initializing the service you will see a green up arrow on the computer name and the router is ready to be configured.



Note: The Routing and Remote Access service is automatically set to a Startup Type of Automatic (Delayed Start) and can take up to 3 minutes to start after a reboot.

Before configuring routes know this one very important thing.  
The interface you select for the static route needs to be the interface that is connected directly to the destination network.

Our Networks are as follows:

  • Outside:
    • Name: Outside
    • IP: 10.100.205.12
    • SNM: 255.255.255.0
    • GW: 10.100.205.1
  • Inside 1:
    • Name: AZ VLAN
    • IP: 10.100.200.1
    • SNM: 255.255.255.0
    • GW: N/A
  • Inside 2:
    • Name: TX VLAN
    • IP: 10.100.201.1
    • SNM: 255.255.255.0
    • GW: N/A
  • Inside 3:
    • Name: FL VLAN
    • IP: 10.100.202.1
    • SNM: 255.255.255.0
    • GW: N/A

Setting the default route

The default route is the route taken if the router does not know how to find the network in question.  For example, for internet access to an IP of 205.168.22.123 this router will not have a static route configured and therefore does not know where to send the traffic.  So, we have to create a default route for all unknown networks.

  • Right Click IPv4 > Static Routes and Click New Static Route
  • Interface: Select the Outside Interface
  • Destination: 0.0.0.0
  • Network Mask: 0.0.0.0
  • Gateway: Set this to the Gateway of the Outside interface (10.100.205.1 in our example)

Setting the remaining static routes

The remaining static routes will tell our traffic how to find our other networks.  We will put in the network IP and subnet mask with the gateway being the IP address of the interface we are pointing the traffic at.




We are now ready to test communication between our hosts.  In server 2012 we will need to either disable the firewall on our hosts or enable ping before we can ping each host.  

Here is a screenshot of our successful tests:

This concludes installing and configuring a software router on Windows Server 2012.

I hope this was helpful and informative to you and I would appreciate any feedback you may have.

<< Install Router

How to Install a Software Router on Windows Server 2012 Part 1

This post will discuss how to setup a software based router in Windows Server 2012.

Software routers are great solutions for a lab environment where flexibility and quick configuration in your network is desired.  I have this router setup in my lab environment to route traffic without having to configure the hardware router any time a new network is created.

Note: Software routers are not recommended for Enterprise solutions and should only be used in labs or low budget environments.  The router system should not be domain joined and should be running the local firewall.  No other services should be installed on this Windows Server 2012 system.

In this lab we will be routing three inside networks through our software router.

The Windows Server 2012 system is setup with 4 NICs as follows:



  • Outside:
    • Name: Outside
    • IP: 10.100.205.12
    • SNM: 255.255.255.0
    • GW: 10.100.205.1
  • Inside 1:
    • Name: AZ VLAN
    • IP: 10.100.200.1
    • SNM: 255.255.255.0
    • GW: N/A
  • Inside 2:
    • Name: TX VLAN
    • IP: 10.100.201.1
    • SNM: 255.255.255.0
    • GW: N/A
  • Inside 3:
    • Name: FL VLAN
    • IP: 10.100.202.1
    • SNM: 255.255.255.0
    • GW: N/A

Two things to note with a software router
  1. The outside interface will aggregate all traffic outside of the router and will have a gateway of the next hop in the network.  This can be your public IP or the IP of another router on your network.
  2. All inside interfaces are the gateway for the subnets being configured and therefore should not have a gateway set.  We will configure static routes so the software router in Windows Server 2012 knows how to get to each network.

How to Install the Software Router in Windows Server 2012

Once the network cards are named and set with IP addresses, we can go ahead and install the software router.

  • Launch Server Manager and click on Add Roles and Features
  • Before you begin: Click Next
  • Select installation type: Select Role-based or feature-based installation and Click Next

  • Select destination server: Choose Select a server from the server pool and be sure the local server is highlighted in the Server Pool list box, then Click Next

  • Select server roles: Check the Remote Access check box. This will launch the Add features that are required for Remote Access? dialog box.  Click Add Features then Click Next
  • Select Features: Click Next
  • Remote Access: Click Next

  • Select role services:  Check the Routing check box.  
    • Note: You must leave DirectAccess and VPN (RAS) selected
  • Web Server Role (IIS): Click Next
  • Select role services:u Click Next
  • Confirm installation selections: Click Install
  • Installation progress: After the installation completes, Click Close
This completes the installation. You will notice a message icon in the Notification Bar after the installation completes.  Click on the flag icon, then the Open the Getting Started Wizard to begin configuring your router.