September 28, 2016 at 1:23 pm
Hi,
I just setup a lab with 3 VM's( 1 domain server, 2 SQL nodes ).
WMware workstation 12
windows 2012R2 DataCenter
SQL Server 2016 dev
My 3 VM's have they own private VM network, nothing else.
I enabled TC/IP, Name pipe and Share Memory.
Everything seems to be working fine except when i try to connect with SSMS,sqlcmd,etc from 1 node to another.
SSMS from and to current node work great, no issues there.
I had to put timout to 0 so that it does not timeout.
I checked and Checked my settings, I probably overlooking something everytime, but what?!? , can someone point me in a direction...
Networking is not my best subject....
I can ping from each node no problem and no delays...
------------------------
Pinging SQL6.MyDomain6.com [192.168.4.121] with 32 bytes of data:
Reply from 192.168.4.121: bytes=32 time<1ms TTL=128
Reply from 192.168.4.121: bytes=32 time<1ms TTL=128
...
------------------------
when I connect using SSMS, it can takes from 5 to 10 min.:w00t::w00t::w00t:
------------------------
C:\Windows\system32>sqlcmd -S sql6
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Unable to complete logi
n process due to delay in opening server connection.
-----------------------
Alex
September 28, 2016 at 1:46 pm
You describe the SQL servers as nodes, are they clustered?
If so, what sort of clustering?
Otherwise, if they're two stand-alone instances of SQL, check that the Windows Firewall is either off (only if this is a lab and not connected to the internet), or configured to allow TCP port 1433 in.
September 28, 2016 at 1:57 pm
sorry bad habit of calling them nodes.
Yes they are 2 separate instances on 2 vm servers. Server 1: SQL5 and Server 2: SQL6
Yes I disabled all the security features on all 3 servers.
September 28, 2016 at 2:08 pm
Have you tried connecting by IP instead of the name?
Presuming this is all internal to the VMware (IE, the network these three are on does not connect to the wide-world) and they're all on the same domain using the domain controller (your 3rd server) as the DNS, it should work fairly quick.
September 28, 2016 at 3:11 pm
yes, I tried name and IP same result.
October 3, 2016 at 1:42 pm
ok , I was the error code 13...
1 of the servers still had the firewall active...
Thanks all
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply