November 6, 2009 at 9:36 am
I have a strange problem. I have a test server configure with 2 ip addresses so a vendor can have a DNS entry assigned to a web site he is testing. The IP address that his site is using is on the same subnet (and physical server) as the SQL Server 2005 (sp3) instance he is connecting to (sql server instance ALPGASTEST01 on 166.99.95.9 and DNS for web site, cat-iso-test, on 166.99.95.26). The application tends to intermittently have issues connecting to the database. If I restart the MSSQL Server service then the issue goes away.
Is there something specific in the SQL configuration that I need when I have a server that has multiple IP addresses? The DNS entry is done via IP address according to my corporate NT guys.
Thanks in advance.
November 21, 2009 at 12:28 pm
Should be no issue with multiple IP addresses. I haven't seen problems with connectivity because of this. If they are timing out, I might check and be sure that it's not server load in some way.
November 21, 2009 at 12:48 pm
I have got a similar issue (not exactly the same) where my application team complained about 2 SQL servers having intermittent connection problems.
I made sure that have been changed their connection settings to the Server IP followed by the port no of the SQL server as per the recommendations on MSDN. I don't have the link to post it here, but it says it has some thing to do with service broker under some settings throws this type of error.
When they made changed to use the the IP,port# (ex : 192.117.12.168,2433). They have no issues since then.
If you have not tried this, you may test doing this.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply