February 25, 2015 at 6:38 pm
Hey all,
I have setup DNS aliasing a multitude of times on stand alone machines as well as clusters. With the latter, you have to set all ports to 1433 (under IPALL) which isn't an issue as they all have their own IP. I've used this article to set it up with issue: http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx
So what do you do in scenario where it's a single machine with multiple instances? I'm failing to discover how to set the IP per instance here. By manually changing "IP1" (which is the server's IP), I was able to get the instance to listen on that IP, but I wasn't able to get connections outside of this machine to connect. Regardless, I don't think this is the proper way to change the IP per instance is it? In a clustered setup, you see IPX through IPY, which includes each clustered instance's IP. In this setup, multiple instances on a single machine, how do you change the IP?
I went into the NIC properties and added the additional IP's I have set aside for these instances and when going back into the TCP/IP settings per instance, I still have the default IP1 through IP5.
This article: http://blogs.msdn.com/b/sqlblog/archive/2009/07/17/how-to-configure-sql-server-to-listen-on-different-ports-on-different-ip-addresses.aspx has me a bit worried. Jump to "Case 3: You add an additional IP address on the system:" ... is this accurate? I had to have the IP's associated with the NIC at time of install???
Any help would be most helpful.
Thanks
February 26, 2015 at 5:53 am
Did you already read this?
-- EDIT ---
Disregard, it seems it's the same URL you posted above.
February 26, 2015 at 8:48 am
So what I've done is this ...
- Added the IP's to the NIC
- Disabled ListenAll
- Changed IP1 to the IP in question
- Set port to 1433
- Set Enabled to Yes
- Restarted SQL
I can connect to the instances locally by name, IP, and alias.
Remotely I can connect by IP and alias, and can only connect to one of the three instances by servername\instance name.
I then followed this: http://kevine323.blogspot.com/2013/08/setting-up-aliases-on-sql-server-with.html to the T. Sadly only one of the three instances will start up at a time being that I had to remove both ::1 and 127.0.0.1 from the IP list. The other two won't even come online at this point.
I've rolled everything back and am looking for help at this time as I'm not sure where to go from here.
Any thoughts?
February 26, 2015 at 11:07 am
Was able to fix it by adding new IP's (via registry) and binding both server ip + instance ip.
All is well.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply