To connect to our private network from a Windows client computer, you need to follow the following steps :
Are you sometimes having trouble to load your website or access your dedicated server, or are you getting lags using your server SSH or Remote Desktop?
Are you looking for a solution to see packet loss and latency between two networks?
MTR / WinMTR will help you to make your life easier. You can install MTR on any dedicated server or any desktop pcs to track your outgoing network easier.
To install the MTR on Linux based systems, you can use yum or apt-get to get it installed. To install MTR on your windows system, you can download WinMTR from here, and install it on your windows system.
CentOS : yum install mtr -y
Ubuntu, Debian : apt-get install mtr -y
The usage of mtr is very easy and simple, you only have to run the following command to see the results.
Instead of “hugeserver.com” you can put any other IP addresses or domain names to see the hops and the route your source server to your destination server.
If you want to see only the ip addresses and not the domain information ( rdns ) of them, you can click “n” during the program is running or simply use the following command
mtr -n hugeserver.com
You may change the packet size to something else with adding the package size after hostname or ip address.
mtr -n hugeserver.com 100
This tool can help you to determinate any packet loss between two network.
This is a notice of an active security alert which could pose a threat to your server with operating system of Microsoft Windows. Please see the alert below:
Yesterday, during Microsoft’s Patch Tuesday they announced a patch for a critical vulnerability in Windows Remote Desktop.
If exploited, the vulnerability would allow anyone to remotely run commands on your server.
This bug affects all versions of Windows (XP – 7/2008 R2) If you have a server or workstation running RDP please patch it now. There currently is no known exploit, but Microsoft believes there will be one in the next 30 days.
However, it is very likely there will be something sooner.
A temporary fix is to enable NLA (Network Layer Authentication). This would require the attacker to have valid login credentials, however if successfully exploited the remote commands would run as the SYSTEM user and not the user authenticated.
The patch is available from Windows Update and there are manual patches linked below.
Thank you for your review.