connecting over internal IP to sql2005 box

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

connecting over internal IP to sql2005 box

Author

Topic

mike123
Master Smack Fu Yak Hacker

1462 Posts

Posted - 2007-07-31 : 06:52:29

Hi,

I have 2 boxes, 1 webserver and 1 db server, both behind a firewall. For the past few years I have been connecting from the webserver to the db server using a public IP. I have 2 NIC's in the DB server so I now want to connect locally to reduce our companies bandwidth charges, and hopefully make things a tiny bit faster too. I'm not sure if it will make a difference, but should be interesting.

I'm having problems setting this up tho, what steps do I need to take to make sure it works properly?

When I check my DB servers IP configuration I get 2 NICs'

One configured as an external IP, the other configued as
169.xxx.xx.xxx

I am trying to connect using the 169.xxx.xx.xx Is this the correct approach? I am getting TimeOut Errors as seen below

I looked in my SQL configuration and its set to allow remote connections however, and since I was connecting over a public IP before, this seems contridicting.

Any help is much appreciated.

Thanks once again!!! :)
mike123

System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

ValterBorges
Master Smack Fu Yak Hacker

1429 Posts

Posted - 2007-07-31 : 07:15:10

http://support.microsoft.com/kb/914277

mike123
Master Smack Fu Yak Hacker

1462 Posts

Posted - 2007-07-31 : 07:44:07

Hi,

thanks for this article. I just followed all the steps and all my settings appear to be correct, my installation was already set to "local and remote connections", so I dont think this is the problem.

I'm wondering since I have 2 NIC's do I specifically have to set SQLServer to listen on this new IP address?

ValterBorges
Master Smack Fu Yak Hacker

1429 Posts

Posted - 2007-08-02 : 17:27:36

You could try redirecting the traffic from the 169.xxxx to 127.0.0.1 and see if it works. I just recently ran across porttunnel software by steelbytes.com that runs as a service and redirects tcp/ip port traffic.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources