Error:
TITLE: Connect to Server
------------------------------
Cannot connect to FRACKAGLSNR.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or was not
accessible. Verify that the instance name is correct and that SQL Server is
configured to allow remote connections. (provider: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error:
53)
Listner IP: 192.168.1.240
Step1: Check ping IP of listener
C:\Users\dba>ping 192.168.1.240
Pinging 192.168.1.240 with 32 bytes of data:
Reply from 192.168.1.240: bytes=32 time<1ms TTL=128
Reply from 192.168.1.240: bytes=32 time<1ms TTL=128
Reply from 192.168.1.240: bytes=32 time<1ms TTL=128
Reply from 192.168.1.240: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.1.240:
Packets: Sent = 4, Received =
4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms,
Average = 0ms
Step2: check nslookup with listener
name
C:\Users\dba>nslookup FRACKAGLSNR
Server: UnKnown
Address: 192.168.1.200
Name: FERACKAGLSNR.NTRY.COM
Address: 192.168.0.249
Here it is giving different IP because 192.168.0.249 is mapped with FRACKAGLSNR
Issue Fix: create PTR record for
192.168.1.240 with listenername.
Step3: nslookup FRACKAGLSNR
C:\Windows\system32>nslookup FERACKAGLNR
Server: UnKnown
Address: 192.168.1.200
Name: FRACKAGLNR .NTRY.COM
Address: 192.168.1.240
No comments:
Post a Comment