If you had recently installed CentOS on a VirtualBox and unable to connect to the internet, this simple step would come in handy for you to get your OS connected to the internet. Steps: Using a Bridged Adapter or NAT (Network Address Translation) would achieve the same result. Difference between the two options is: [quote style=”boxed”]NAT: This enables the guest machine to access the Internet, but via a private IP address that cannot be seen from the host or the rest of your physical network.
Hi Systems Administrator’s out there, today I will dive into the DHCP world of Windows Server 2012. The followings are now supported with Windows Server 2012 DHCP role: – DHCP Server Failover – Policy-Based Assign – Now supports PowerShell For the purpose of this post, I will focus on the basic installation and configuration of DHCP and will deal with the Failover functionality in later post. OK, enough of the talking and let’s get into the menu of the day “DHCP Fries with milkshake” 🙂 Setup: Installing the DHCP role – Start the Server Manager – Click Add Roles and Features from the Manage Menu – On Add Roles and Features wizard begins and click Next – Select the Role-based or feature-based installation option and click Next – If you have more than one server managed via the server manager console, then select the desired server you’d like to install DHCP on – From the Roles lists, check the DHCP Server role, click Add Features on the popup windows – Click Next – Select additional features you desire or leave as default and click Next – Keep in mind ‘Things to note’ and click Next – Confirm information on summary page and click Install – After install is completed, click Close Post Deployment – Click on the warning icon and then click on ‘Complete DHCP Configuration’ – On DHCP Post-Install wizard, click Next – On Authorization, select a domain user account that has permissions to create objects in the Net Services container in Active directory (For security lock-down) or simply use a domain admin account and click Next – Confirm on summary page that the security groups had been created and Authorizing DHCP server role done.
I will be showing us how to install and configure a Windows Server 2012 VPN connection. This post would focus on simple basic setup for a test environment with a single NIC on the Internal network behind a firewall. Steps: – Start the Server Manager – Click Add Roles and Features from the Manage Menu – On Add Roles and Features wizard begins and click Next – Select the Role-based or feature-based installation option and click Next – If you have more than one server managed via the server manager console, then select the desired server you’d like to install Routing and Remote Access on – From the Roles lists select Remote Access, click Add Features on the popup window – Click Next – No additional features required at this point, click Next – Have a quick read on what DirectAccess & RRAS VPN is, then click Next – Select DirectAccess and VPN (RAS), click Next – Click Next after reading this if you care 🙂 – Accept default selections and click Next – Review the confirmation page and click Install to begin – When installation is completed, click Close Go to Page2: Post deployment and configuration