Dual NIC SQL connection problem

goodvibes
goodvibes used Ask the Experts™
on
I am preparing our Hyper-V SQL server for migration to a new Hyper-V CSV cluster. It has 2 VNICS one to our LAN, one to a SAN LUN. I have since virtualised the SAN LUN and placed it locally on the Hyper-V server in preparation for the move. However when I disable the internal SAN NIC none of our SQL clients (IIS7 etc.) can connect to the server. They connect using \\servername\instancename.  I have to get rid of the NIC, it's not needed in the Cluster environment. The SAN has no routes, only the LAN does. All the other servers can ping each other whether the SAN NIC is disabled or not. I've tried various combinations of enabling IP protocols in SQL server config, no luck. The only thing that matters is that SAN NIC.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Metehan OzculluSQL Service Manager

Commented:
looks like routing table on the server is a bit mixed. is there a gateway defined for SAN LUN nic. if so clear it. if you need that gateway you can add it as a persistent route later. if you send me the output of "route print" command, I can give more details.

Author

Commented:
I don't have any routes on the SQL box, but I've attached the route print. I've also attached  a netstat -a for when the SAN NIC is enabled and disabled.
routes-SQL-VM.txt
sql-no-SAN-NIC.txt
sql-SAN-NIC.txt

Author

Commented:
A bit more info.... these are the IP connections from the registry for our Instance. There are quite a few for IP v6 which must have been enabled when we installed, but is now disabled.
IPn-setup-for-SQL.txt
Starting with Angular 5

Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.

Metehan OzculluSQL Service Manager

Commented:
did you try to disable firewall on the server for a trial?

Author

Commented:
Yep, tried all that
One last request for a solution on this, I've increased the points. I'm about to re-build a new SQL VM to solve the issue if no answers in the next day or so. I've tried every trick in the book (well, the web actually) and clients still cannot connect when the old SAN 10.10.. NIC doesn't exist on the moved VM.

Author

Commented:
I'm closing this question as I had to move forward, I couldn't solve it so I have created a new VM without the offending VLAN and migrated our dbs across to it.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial