Problem with 2nd NIC and SQL Server

(SQL DBA posting for the network administrator)

Our two SQL Server servers also act and DNS servers. Both are running
Win2k3 with 2 NIC cards. When our network staff enabled the 2nd NIC
cards we started having problems connecting to our SQL instances with
Enterprise Manager (also Query Analyzer) from remote PCs.

If we connected to the server via terminal services and then ran EM/QA
from the server it worked for the local instances. None of our
applications lost connection only EM/QA. Trying to PING the servers
using the IP address also failed.

The 2nd NIC is on a private VLAN using a 10.x.x.x network. The 1st
NIC is on a different private VLAN using at 198.x.x.x network. The
propagate to DNS feature is disabled on the 2nd NIC, but it still
publishes that NIC address into the DNS.

The error message we got when trying to connect via EM was "SQL Server
does not exist or access denied" if I recall correctly. Both servers
are running SQL Server 2000 with named instances.

Hi,

I am may be wrong, but this sounds like it could be a SQL server name
problem.
dont work with the MS SQL server much but I remeber similar issuse adding a
second network card , and the instance of SQL suddenly renamed itself to a
string representation of the IP address of the second card. I dont mean the
host name of the server i mean the name of the sql server
you can get this by typing @name or @servername in the query console thing.


Mike.


"Randy K" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> (SQL DBA posting for the network administrator)
>
> Our two SQL Server servers also act and DNS servers. Both are running
> Win2k3 with 2 NIC cards. When our network staff enabled the 2nd NIC
> cards we started having problems connecting to our SQL instances with
> Enterprise Manager (also Query Analyzer) from remote PCs.
>
> If we connected to the server via terminal services and then ran EM/QA
> from the server it worked for the local instances. None of our
> applications lost connection only EM/QA. Trying to PING the servers
> using the IP address also failed.
>
> The 2nd NIC is on a private VLAN using a 10.x.x.x network. The 1st
> NIC is on a different private VLAN using at 198.x.x.x network. The
> propagate to DNS feature is disabled on the 2nd NIC, but it still
> publishes that NIC address into the DNS.
>
> The error message we got when trying to connect via EM was "SQL Server
> does not exist or access denied" if I recall correctly. Both servers
> are running SQL Server 2000 with named instances.
>

Get rid of the second Nic. All subnets get to the server by the one
original nic.

Dual nic machines are for PCs that act as firewalls, routers, and when Nic
teaming is performed. None of these are happening in this case.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Randy K" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> (SQL DBA posting for the network administrator)
>
> Our two SQL Server servers also act and DNS servers. Both are running
> Win2k3 with 2 NIC cards. When our network staff enabled the 2nd NIC
> cards we started having problems connecting to our SQL instances with
> Enterprise Manager (also Query Analyzer) from remote PCs.
>
> If we connected to the server via terminal services and then ran EM/QA
> from the server it worked for the local instances. None of our
> applications lost connection only EM/QA. Trying to PING the servers
> using the IP address also failed.
>
> The 2nd NIC is on a private VLAN using a 10.x.x.x network. The 1st
> NIC is on a different private VLAN using at 198.x.x.x network. The
> propagate to DNS feature is disabled on the 2nd NIC, but it still
> publishes that NIC address into the DNS.
>
> The error message we got when trying to connect via EM was "SQL Server
> does not exist or access denied" if I recall correctly. Both servers
> are running SQL Server 2000 with named instances.
>

We need the second NIC for backups. We have a SQL database with a TB
of RASTER data and growing.

On Thu, 27 Jul 2006 10:20:26 -0500, "Phillip Windell" <@.> wrote:

>Get rid of the second Nic. All subnets get to the server by the one
>original nic.
>
>Dual nic machines are for PCs that act as firewalls, routers, and when Nic
>teaming is performed. None of these are happening in this case.
>
>--
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>"Randy K" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> (SQL DBA posting for the network administrator)
>>
>> Our two SQL Server servers also act and DNS servers. Both are running
>> Win2k3 with 2 NIC cards. When our network staff enabled the 2nd NIC
>> cards we started having problems connecting to our SQL instances with
>> Enterprise Manager (also Query Analyzer) from remote PCs.
>>
>> If we connected to the server via terminal services and then ran EM/QA
>> from the server it worked for the local instances. None of our
>> applications lost connection only EM/QA. Trying to PING the servers
>> using the IP address also failed.
>>
>> The 2nd NIC is on a private VLAN using a 10.x.x.x network. The 1st
>> NIC is on a different private VLAN using at 198.x.x.x network. The
>> propagate to DNS feature is disabled on the 2nd NIC, but it still
>> publishes that NIC address into the DNS.
>>
>> The error message we got when trying to connect via EM was "SQL Server
>> does not exist or access denied" if I recall correctly. Both servers
>> are running SQL Server 2000 with named instances.
>>
>
>

"Randy K" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We need the second NIC for backups. We have a SQL database with a TB
> of RASTER data and growing.

On a switched network the backup will not cause as much trouble over the
normal LAN as you might be inclined to think. Generally it is not even
noticed.

But anyway, to use a second "network" for backing up requires:

1. The second nic on the server and the target have to be in the same subnet
together, but a different IP segment from the rest of the LAN.

2. The Target (machine receiving the data) must be accessed by the IP# of
the second "network" or by a fake name you create for it in WINS, DNS, HOST,
or LMHOST file (depending on what you choose to use) which would resolve to
the correct IP#.

For example:
SQL Server (being backed up)
Name = SQLSVR
Main Net = 192.168.5.7
Net #2 = 172.16.25.3

Storage Server (receiving the backup)
Name = StoreSVR
Fake Name = BackSVR
Main Net = 192.168.5.8
Net #2 = 172.16.25.4

Use WINS (or other means) to associate "BackSVR" with 172.16.25.4 on Net #2
Send the data to "BackSVR" (not StoreSVR)
Alternatively, the StoreSVR could just have one nic and live only on Net #2
and not be on the regular LAN at all.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------