Solved

SQL Job authentication on dual-NIC VM

Posted on 2014-02-10
6
291 Views
Last Modified: 2014-02-21
I have a Server 2012 R2 VM running SQL 2012. The VM has two NICs, one is NAT to a local domain controller, the other is bridged so I can access the VM from outside the NAT network.

With only the NAT NIC attached, my SQL jobs run fine, with job owners authenticating to the local domain controller.
With both the NAT and bridged NICs attached, my SQL jobs fail with error code 0x54b (The specified domain either does not exist or could not be contacted) SQLSTATE 42000 Error 15404. It appears as though SQL favors the Bridged adapter for authentication when both bridged and NAT adapters are present.

Does anyone know of a way to tell SQL to always authenticate on the NAT adapter, even if the bridged adapter is present?
0
Comment
Question by:athemelis
  • 3
  • 2
6 Comments
 
LVL 38

Expert Comment

by:Jim P.
ID: 39849880
In the SQL Server Configuration manager is the Named Pipes protocol turned on? If it is turn it off.

And then look at your routing (route print from DOS) and see what the metric is for the NAT adapter compared to the bridged NICs.
0
 

Author Comment

by:athemelis
ID: 39850075
Thank you for the information. In the SQL Server Configuration Manager, I found the following:
- SQL Native Client 11.0 Configuration (32 bit): disabled
- SQL Server Network Configuration: enabled
- SQL Native Client 11.0 Configuration: enabled

I have disabled the bottom two above, is that correct?

route print shows the following output. Please let me know what I should do:

C:\Users\admin>route print
===========================================================================
Interface List
 16...00 0c 29 dd 29 cd ......Intel(R) 82574L Gigabit Network Connection #2
 12...00 0c 29 dd 29 c3 ......Intel(R) 82574L Gigabit Network Connection
  1...........................Software Loopback Interface 1
 14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 15...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.116.2    192.168.116.4    266
          0.0.0.0          0.0.0.0      10.11.200.1     10.11.202.69     10
      10.11.200.0    255.255.252.0         On-link      10.11.202.69    266
     10.11.202.69  255.255.255.255         On-link      10.11.202.69    266
    10.11.203.255  255.255.255.255         On-link      10.11.202.69    266
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
    192.168.116.0    255.255.255.0         On-link     192.168.116.4    266
    192.168.116.4  255.255.255.255         On-link     192.168.116.4    266
  192.168.116.255  255.255.255.255         On-link     192.168.116.4    266
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link     192.168.116.4    266
        224.0.0.0        240.0.0.0         On-link      10.11.202.69    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link     192.168.116.4    266
  255.255.255.255  255.255.255.255         On-link      10.11.202.69    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0    192.168.116.2  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 12    266 fe80::/64                On-link
 16    266 fe80::/64                On-link
 15    266 fe80::5efe:192.168.116.4/128
                                    On-link
 16    266 fe80::50a6:6b89:c1ad:ee54/128
                                    On-link
 12    266 fe80::7de7:ea7:2829:a29/128
                                    On-link
  1    306 ff00::/8                 On-link
 12    266 ff00::/8                 On-link
 16    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
0
 
LVL 38

Expert Comment

by:Jim P.
ID: 39850206
This is the SQL 2005 configuration manager, but the 2008 has a similar locations and looks.
SQL ConfigYou want to turn off the Named Pipes like I show in the image.

The native clients are fine being enabled.
0
 

Accepted Solution

by:
athemelis earned 0 total points
ID: 39862687
I was able to resolve the problem using the following article:

http://technet.microsoft.com/en-us/library/cc732472%28v=ws.10%29.aspx

Open the Network Connections folder and view available connections.

Press ALT to display the menu bar, and then on the Advanced menu, click Advanced Settings. The Advanced Settings dialog box opens.

In the Advanced Settings dialog box, on the Adapters and Bindings tab, in the Connections list, click the connection that you want to modify. If you wish to change the order in which your connections are tried, click the up or down arrow buttons to rearrange the order.
0
 

Author Closing Comment

by:athemelis
ID: 39876313
It resolved the problem, I hope it benefits others as well.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question