How to change default RDP or Remote Desktop Port on Windows Server

Nowadays, the biggest concern on internet is Security. We to secure the Remote server we usually change the RDP port number. The default RDP port is 3389.

here is the way to do it:

1. First we will login to the Remote Server then open registry by typing regedit on the Run box. Then click on Ok.

2. When the Registry Editor opens up, expand HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server > WinStations > RDP-Tcp > then double-click on “PortNumber” in the window on the right.

3. With the PortNumber registry key open, select “Decimal” on the right side of the window and then type your desired port number under “Value data” on the left.

4. Click OK and then close the Registry Editor.

5. Since we’ve changed the default port that Remote Desktop uses, we’ll need to configure Windows Firewall to accept incoming connections on that port.  Go to the Start screen, search for “Windows Firewall” and click on it.

6. When Windows Firewall opens, click “Advanced Settings” on the left side of the window.  Then right-click on “Inbound Rules” and choose “New Rule.”

7. The “New Inbound Rule Wizard” will pop up, select Port and click next.  On the next screen, make sure TCP is selected and then enter the port number you chose earlier, and then click next.  Click next two more times because the default values on the next couple pages will be fine.  On the last page, select a name for this new rule, such as “Custom RDP port,” and then click finish.

8. Your computer should now be accessible on your local network, just specify either the IP address of the machine or the name of it, followed by a colon and the port number you have mentioned in registry.

Advertisements

Installing and configuration of SNMP on VMWARE Esxi 5.1

This is our first post on VMWARE Vsphere.

Today, we will discuss how to install SNMP on Esxi 5.1. To install SNMP on Esxi, we need to login to the Shell of Esxi. Esxi is a baremetal hypervisor, so we need to connect to the shell directly first. Then we run some commands to install SNMP.

Enabling Local ESXi Shell Access
You can enable the ESXi Shell from the direct console or from the vSphere Client.
If you have access to the direct console, you can enable the ESXi Shell from there.
To enable the ESXi Shell in the direct console

1. At the direct console of the ESXi host, press F2 and provide credentials when prompted.

2. Scroll to Troubleshooting Options and press Enter.

3. Choose Enable ESXi Shell and press Enter.
On the left, Enable ESXi Shell changes to Disable ESXi Shell. On the right, ESXi Shell is Disabled changes to ESXi Shell is Enabled.

4. Press Esc until you return to the main direct console screen.

If you do not have access to the direct console, you can enable the ESXi Shell from the vSphere Client.
To enable the local or remote ESXi Shell from the vSphere Client

1. Select the host, click the Configuration tab, and click Security Profile in the Software panel.

2. In the Services section, click Properties.

3. Select ESXi Shell and click Options.

4. Change the ESXi Shell options.
To change the Startup policy across reboots, click Start and stop with host and reboot the host.
To temporarily start or stop the service, click the Start or Stop button.

5. Click OK.

Now, the esxi shel is enabled. We can use ssh, I mean putty or any other ssh client as well to configure SNMP.

Using the Local ESXi Shell

After you enable the ESXi Shell in the direct console, you can use it from main direct console screen or remotely through a serial port.

To use the local ESXi Shell

1. At the main direct console screen, press Alt-F1 to open a virtual console window to the host.

2. Provide credentials when prompted.When you type the password, characters are not displayed on the console.
3. Enter shell commands to perform management tasks.

4. To log out, type exit in the shell.
5. To return to the direct console, type Alt-F2.

Now, we are ready to configure SNMP on Esxi.

# Configure SNMP Communities

Type esxcli system snmp set –communities com1.

Replace com1 with the community name you want to set. Each time you specify a community with this command, the settings you specify overwrite the previous configuration. To specify multiple communities, separate the community names with a comma.

For example, to set the communities public and internal on a host, you might type esxcli system snmp set -communities public,internal.

#Configure the SNMP Agent to Send SNMP v1 or v2c Traps

1. Type esxcli system snmp set –targets target_address@port/community.

Replace target_address, port, and community with the address of the target system, the port number to send the traps to, and the community name, respectively. Each time you specify a target with this command, the settings you specify overwrite all previously specified settings. To specify multiple targets, separate them with a comma.

For example, to send SNMP traps from the host host.example.com to port 162 on target.example.com using the public community, type esxcli system snmp set –targets target.example.com@162/public.

2. (Optional) If the SNMP agent is not enabled, enable it by typing esxcli system snmp set –enable true.

3. (Optional) Send a test trap to verify that the agent is configured correctly by typing esxcli system snmp test.
The agent sends a warmStart trap to the configured target.

When you configure the ESXi SNMP agent for SNMP v3, the agent supports sending informs as well as traps. SNMP v3 also provides stronger security than v1 or v2c, including key authentication and encryption.

# Configure the SNMP Agent for GETs

1. Type esxcli system snmp set –port port.
Replace port with the port for the SNMP agent to use for listening for polling requests.

2. (Optional) If the SNMP agent is not enabled, enable it by typing esxcli system snmp set –enable true.

Start or Stop Iptables Firewall on Debian Linux

Debmintux

I have been given the task at work of configuring the firewalls for a client with a large network and various servers. The system has a lot of security implemented which requires specific control of users, subnetworks, and who has access rights to certain network and internet resources.

Configuring a single computer is relatively easy, and you can find many guides on the net, but I was curious to see that on some Ubuntu/Debian based forums and blogs, people were treating iptables as a service which it most certainly isn’t. There appears to be some confusion between Debian, Redhat, and derivatives (Ubuntu, Fedora, CentOS etc).

Difference between Redhat and Debian
Redhat, Fedora, CentOS do have a script in /etc/init.d which allows you to {save|stop} the iptables configuration, and I believe some people were mistakenly trying to apply it to Debian based systems. That’s not to say that you couldn’t create…

View original post 337 more words

How to Configure WiFi Hotspot in Windows 7 Using Command Prompt

A WiFi hotspot is a Wireless hub which offers a network access to various devices over a wireless medium using routers. It requires a particular software which gives the ability to host a Hotspot in our computer. In order to reduce the difficulty, it’s better to establish a WiFi Hotspot using Command Prompt.

Read the below steps clearly and start your own WiFi Hotspot.

Step 1:

  • Select Command Prompt(Admin) in your computer.
  • Command: Windows key( ) + X

Step 2:

  • Check whether your computer is supported for Hosted network or not. Type the following command in Command Prompt.
  • Command : netsh wlan show drivers

If the result is “YES” then proceed to Step 3 or else download the required drivers from your vendor website.

Configuring the Hosted network connection:

Step 1:

  • Type “netsh wlan set hostednetwork mode=allow ssid=yourname key=yourpassword” (enter the command without the quotations).
  • Note: In this example, I have used my own user Name and Password. You can use your own parameters for SSID and KEY and Password must be greater than 8 digits.

You have successfully established the Network Connection.

Step 2:

  • Start your hosted network.
  • Command : netsh wlan start hostednetwork

If your Command Prompt says ” your hosted network couldn’t be started ” then make sure to turn on the “WiFi” and also enable the Wireless Adapter 🙂

When there is no error:

Sharing your Wireless Network Adapter

Step 1:

  • Go to control Panel -> Network and Internet and select Network and Sharing Center.

Step 2:

  • There you can see your newly created network under the original network connection.

Step 3:

  • Select “Change adapter settings” in the left side column of Network and Sharing Center.

Step 4:

  • Right click on your Wireless Network Adapter and select properties. Select the tab “Sharing“. Check the option “Allow other network users to connect through this internet’s connection” option. Mention your newly created hosted network name.

Step 5:

  • Check whether your hosted network has shared the network access or not from the Network Sharing and Center.

  • Wahoooo!! You have successfully turned on your WiFi Hotspot. Now you can surf internet from any device using the Hotspot.
  • Here i’m going to connect my Mobile using the configured WiFi Hotspot.

  • To stop the hosted network, type the command ” netsh wlan stop hostednetwork” in command prompt.

Do you think typing a command for starting/Stopping the WiFi Hotspot is a time dependent?

OK, i’m going to show you one trick so that you can Start/Stop your WiFi Hotspot in a single click.

Step 1:

  • Desktop -> Right click -> New -> Shortcut.

Step 2:

  • Type the command ” C:\Windows\System32\netsh.exe wlan start hostednetwork ” on the shortcut and click on Next.

Rename it as “Start WiFi” and click finish.

Stop WiFi:

  • Type the command ” C:\Windows\System32\netsh.exe wlan stop hostednetwork ” on the Shortcut and Rename it as “Stop Wi-Fi” and finish.

You are done with creating your WiFi Hotspot. You can now use the new shortcuts whenever you wish to use your Wifi Hotspot.

How to install Windows security Essential on Windows Server 2012

Today, I will provide you simple steps to install Windows Security Essential on Windows server 2012. It is basically not compatible with Win server 2012. Windows Security Essential is a free anti-virus that will scan your computer (Basically we do not rely on freeware for production servers, but you might use it).

Steps below:

  1. Download a copy of MSE(Microsoft Security Essential) from Microsoft: http://windows.microsoft.com/en-us/windows/security-essentials-all-versions
  2. Right Click on the “mseinstall.exe”.
  3. Click on Properties.
  4. Click on the “Compatibility”-tab.
  5. Locate the “Compatibility mode”-section.
  6. Check “Run this program in compatibility mode for:”.
  7. Select From the (now active) dropdown menu “Windows 7″.
  8. Open a Command Prompt as Administrator.
  9. cd to your Downloads folder (ie. cd C:\Users\%username%\Downloads).
  10. Run “mseinstall /disableoslimit” and follow the installer prompts to install MSE on your Windows Server 2012.