4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

SQL Server connection. [CLIENT: XXX.XXX.XXX.XXX]

The error occurs because the Virtual SQL Server is not properly registered with DNS or does not

Domain Name Service (DNS) is the backbone of Active Directory (AD) and the primary name resolution

mechanism for Windows. If DNS is not configured correctly, Windows authentication may fail.

To verify that DNS is correctly configured for the Virtual SQL Server, ensure that the following tests

are successful.

1. Ping the Virtual SQL Server. For example:

C:\>ping vqar13s11

Pinging vqar13s11.ad1.polyserve.com [99.11.13.181] with 32 bytes of data:

Reply from 99.11.13.181: bytes=32 time<1ms TTL=128

Ping statistics for 99.11.13.181:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

NOTE:

If the ping fails, make sure an A record is created in DNS for the hostname.

2. Ping the virtual SQL Server IP address. For example:

C:\>ping -a 99.11.13.181

Pinging vqar13s11.ad1.polyserve.com [99.11.13.181] with 32 bytes of data:

Reply from 99.11.13.181: bytes=32 time<1ms TTL=128

Ping statistics for 99.11.13.181:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

NOTE:

If the ping does not return the fully qualified hostname, make sure a PTR record is created

for the virtual IP.

3. Nslookup the Virtual SQL Server. For example:

C:\>nslookup vqar13s11

Server: qadc1.ad1.polyserve.com

Address: 99.11.0.31

Name: vqar13s11.ad1.polyserve.com

Address: 99.11.13.181

NOTE:

If the nslookup fails, make sure an A record is created in DNS for the hostname.

HP PolyServe Software for Microsoft SQL Server administration guide 115