SQL Server on a different IP

May 19, 2010 at 07:26:27
Specs: Windows Server 2003
I'm rather new when it comes to dedicated servers, as I just started using one for a project I have with a few buddies of mine. We're going to have a SQL server set up and the dedicated server allows for a range of 5 IPs to be used. For example, let's say the default Port ends in *.*.*.120 and I'd like outside computers to connect to the SQL server via *.*.*.121, how might I designate the SQL server to listen on that IP instead of the default one? If I didn't explain this right, I apologize.

See More: SQL Server on a different IP

Report •

#1
May 19, 2010 at 08:13:31
I am confused, IP addresses are not ports. It kind'a sounds like you want to do load balancing, where the network traffic is split evenly across your Ethernet Connections; is this correct?

Report •

#2
May 19, 2010 at 08:48:54
To be honest, I couldn't tell you. I'm simply the paper pusher in the project we all have and I have literally no experience in any kind of server field. But, to explain how I connect to the dedicated server, it's through the remote desktop connection. I put in the IP address(*.*.*.120) to connect, of course. Now, from what I understand, the dedicated server has 4 more additional static IPs that it can use to host servers and such. As of right now, if we connect to the SQL server from an outside computer, we have to use the default IP, which is *.*.*.120, how could I change it to where we have to outside computers connect to it via *.*.*.121. If that's load balancing as you said, how would I perform that?

Report •

#3
May 19, 2010 at 09:01:46
Hopefully that "default ip" is to your router/firewall not the actual server. If it is you need a sql/security consultant to come in and advise you. Your server would have already been exploited.

If you want multiple accesses to the server, none of which require multiple public ips, there are a number of secure ways of accomplishing this;

1. vpn router/firewall. You create a secure vpn link to the router by using the vpn routes client software which then gives you a ip address in the same subnet as the sql server so you can access like you do on the lan.

2. web front end. This allows you to go to a public web page where you would logon/authenicate to then gain access to the backend sql server.

3. vpn/firewall to an internal terminal server which would allow you to authenicate to the domain and access SQL


Report •

Related Solutions

#4
May 19, 2010 at 11:16:34
As stated above. I hope you do not have your SQL server in the DMZ because you are just setting your self up to be hacked.

I recommend that if you are not familiar with Networking and Network Security that you contract this job out to someone who is.

____________________________

Ok the disclaimer aside, to use a different static IP you simply change it on the TCP/IP stack for the NIC that is connected to the WAN.

Assign the IP address
To set a static IP address:

1. Open Windows Start menu.
2. Open Control Panel.
3. Classic view: Open Network Connections
Category view: Select Network and Internet Connections, and then Network Connections.
4. Double-click on your active LAN or Internet connection.
5. Click Properties.
This opens the Local Area Connections Properties window.
6. In the General tab, highlight the Internet Protocol (TCP/IP) item, and click Properties.
This opens the Internet Protocol (TCP/IP) Properties window.
7. In the General tab, click Use the following IP address, and enter:
* IP address. The static IP address you want to assign to this computer.
* Subnet mask. Subnet mask used by your router.
* Default gateway. IP address of your router's default gateway.
8. In Use the following DNS server addresses, enter all the IP addressses for the DNS servers your router uses.
9. Click OK.
Then:
10. Click OK to close each window.
11. Restart your computer.
12. Then, check your IP address again, to make sure that the changes were applied.


Report •

#5
June 9, 2010 at 23:34:42
If you do not have the private scheme and just only the public
IPs the answer is simple. Allocate the same public IP to the
server. Connect to SQL server using that IP. It is nothing.

You are confusing with the IPs i feel.

If you have private IP scheme what you have to do is, if you do
have a firewall allocate two private IP addresses to the same
NIC of the server and do NAT in the firewall/Router and
connect to SQL server using that IP.

Feel free to conatct me if you need any help.

cmmfahim at gmail dot com


Report •

Ask Question