3.4.3 MxDB for SQL Server Installation and Administration Guide

Chapter 4: Troubleshooting 73

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.

4. Nslookup the Virtual SQL Server IP address. For example:

C:\>nslookup 99.11.13.181

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 a [PTR] record is created in DNS

for the virtual IP. Nslookup may require you to “set type=PTR”

and lookup the in-addr reverse form of the IP. For example:

C:\>nslookup

Default Server: qadc1.ad1.polyserve.com

Address: 99.11.0.31

> set type=PTR

> 181.13.11.99.in-addr.arpa

Server: qadc1.ad1.polyserve.com