Configuring MS SQL Server for Remote Access

A Microsoft SQL instance cannot be accessed remotely through ODBC, Visual Studio, or SQL Server Management Studio connection.

(applies to MS SQL 2005, 2008, 2008 R2, and 2012)

The Windows firewall is usually the culprit in these scenarios. Open TCP port 1433 for the service itself, and 1434 if you need to use the SQL Browser service.

Open cliconfg from a RUN prompt and make sure TCP/IP is an enabled protocol.
For SQL 2005/2008/2008 R2: Check the Services tool, Start > Administrative Tools > Services, to see that the service named SQL Server (MSSQLSERVER) is started.

For MS SQL 2012: Use the Windows key or hover over the left lower corner of the desktop and select Administrative Tools, then Services to see that the service named SQL Server (MSSQLSERVER) is started.

Ensure that you are using the correct credentials to authenticate. The default SQL administrator account is named sa.
Use netstat –an from the command prompt to verify that the server is listening for SQL traffic on the correct ports.
If the server is not listening for SQL traffic on the correct ports, use SQL Server Configuration Manager to change the ports.
For MS SQL 2005/2008/2008 R2, go to Start > All Programs > Microsoft SQL Server 2005 (or 2008/2008 R2) > Configuration Tools > SQL Server Configuration Manager.
For MS SQL 2012: Use the Windows key or hover over the left lower corner of the desktop and select All Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager.

Open the + next to SQL Server Network Configuration.
Right-click TCP/IP and select Properties.
Select IP Addresses.
All TCP ports mentioned on all interfaces should be 1433. Change this to reflect the correct port number and restart the SQL services.
If you are using named instances when installing SQL, giving you the ability to host multiple SQL versions or service types, you will have to specify the name of the SQL instance when connecting rather than just using the server’s name or IP. If you have created a named instance, you will need to access it by appending the name to the server’s name or IP, following a backslash (e.g.\SQLINSTANCENAME or SQLSERVERNAME\SQLINSTANCENAME).

How to change Windows Server 2012 network profile

On Windows Server 2008 if you wanted to change your network profile, it was possible using the GUI. On Windows Server 2012 things are “little” different. You have to use PowerShell if you want to change network profile from private to public or viceversa.


Set-NetConnectionProfile [-Name <string[]>] [-InterfaceAlias <string[]>] [-InterfaceIndex <uint32[]>]
[-IPv4Connectivity <IPv4Connectivity[]> {Disconnected | NoTraffic | Subnet | LocalNetwork | Internet}]
[-IPv6Connectivity <IPv6Connectivity[]> {Disconnected | NoTraffic | Subnet | LocalNetwork | Internet}]
[-NetworkCategory {Public | Private | DomainAuthenticated}] [-CimSession <CimSession[]>]
[-ThrottleLimit ] [-AsJob] [-PassThru] [-WhatIf] [-Confirm] []

Set-NetConnectionProfile -InputObject <CimInstance#MSFT_NetConnectionProfile[]> [-NetworkCategory
{Public | Private | DomainAuthenticated}] [-CimSession <CimSession[]>] [-ThrottleLimit ]
[-AsJob] [-PassThru] [-WhatIf] [-Confirm] []


Set-NetConnectionProfile -InterfaceAlias InternalNet -NetworkCategory Private

InternalNet in this case is the interface Alias.

If you want to see what profile is applied to your network or want to see the interface alias run this command


Install VMware Tools on Debian 7

Install some dependencies

# apt-get install gcc make

Update Kernel Headers

# apt-get update && apt-get install linux-headers-$(uname -r)

Now mount the vmware tools iso on the VM and begin the installation.

# mount /dev/cdrom /mnt/

# cp /mnt/VMwareTools-9.4.0-1280544.tar.gz /usr/local/src/

Untar the installer
# cd /usr/local/src/
# tar -xvf VMwareTools-9.4.0-1280544.tar.gz

Run the installer with -d option to accept defaults
/usr/local/src/vmware-tools-distrib/ -d

NetRouteView: Tool to modify Windows Routing

I have two network cards with different Internet speed on each one. With this tool im able to select what nic/route to use depending on the destination of my packets.

If somehow you screwed up the routing tables, a reboot would automatically fix it because the changes that you made with NetRouteView is only temporary and not persistent.

NetRouteView is a GUI alternative to the standard route utility (Route.exe) of Windows operating system. It displays the list of all routes on your current network, including the destination, mask, gateway, interface IP address, metric value, type, protocol, age (in seconds), interface name, and the MAC address.
NetRouteView also allows you to easily add new routes, as well as to remove or modify existing static routes

Download from: