Using QNAP TS-453U-RP Version 4.3.3.0188 with two NICs setup (two different LAN segment). Had not been able to add it to Veritas Backup Exec 16 as "File server or NDMP data server" to backup the shared folders in QNAP.
The issue was because the Sys Admin has hardened the QNAP security due to recent malwares attack (WannaCry) and other cyber security threats. He has limit the networks segments which can access the QNAP.
To resolved the issue, access to QNAP web interface --> CONTROL PANEL --> SECURITY --> SECURITY LEVEL. Added the network segment which requires to access the QNAP.
Tuesday, June 6, 2017
Wednesday, April 26, 2017
Can't Connect To Remote SQL Server
I have two SQL versions (SQL 2012 and SQL 2016) installed and running concurrently on a single server. After installing SQL 2016, had issue connecting to the newly created instant. Error "
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: SQL Network Interfaces, error: 28 - Server doesn't support strong text requested protocol) (Microsoft SQL Server, Error: -1)
Can't find much on the Net for the precise solution to this specific issue. Eventually after almost half a day googling, the problem was the network protocol (TCP/IP) was disabled by default. After enabling TCP/IP, the connection works like charm!
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: SQL Network Interfaces, error: 28 - Server doesn't support strong text requested protocol) (Microsoft SQL Server, Error: -1)
Can't find much on the Net for the precise solution to this specific issue. Eventually after almost half a day googling, the problem was the network protocol (TCP/IP) was disabled by default. After enabling TCP/IP, the connection works like charm!
Subscribe to:
Posts (Atom)