none
Problem to connect

    Question

  • Hi,

    How to resolve this

    but relevant database is existing within the server and there is "RDP Port : 33333" existing to the server.


    Many Thanks & Best Regards, Hua Min

    Monday, February 27, 2017 8:12 AM

Answers

  • 1. Does it mean both server and client should be open on UDP 1434 in any firewall?

    That depends a little on what firewall you have. Windows firewall only cares about incoming traffic, why it only matters on the server.

    For a firewall that also monitors outgoing traffic, you may also have to make configuration, but outgoing traffic is usually configured in terms of which destination and port a certain program may access. You don't open outgoing ports. (Which is good, because you rarely know these port numbers.)

    2. Here are the lines I've got

    2017-03-17 14:24:16.540     spid12s     Server is listening on [ 'any' <ipv6> 61240].
    2017-03-17 14:24:16.540     spid12s     Server is listening on [ 'any' <ipv4> 61240].

    So this server is listening on port 61240 and not 33333 as you tried with. Try conneting with WIN-0NGDCBCTNKP,61240.

    • Marked as answer by HuaMin Chen Tuesday, March 28, 2017 9:42 AM
    Sunday, March 26, 2017 3:01 PM

All replies

  • Monday, February 27, 2017 8:22 AM
    Moderator
  • Hi,

    Try adding the port number along with the server/instance. Like 10.123.12.23\isdev,1433

    You can find the port number in the configuration manager and several other places, refer here https://sqlandme.com/2013/05/01/sql-server-finding-tcp-port-number-sql-instance-is-listening-on/

    Monday, February 27, 2017 8:31 AM
  • Any other advice to this issue below?


    Many Thanks & Best Regards, Hua Min

    Monday, February 27, 2017 9:32 AM
  • 1. Make sure SQL Server Service is running
    2. If a named instance, make sure SQL Server browser service is running
    3. Make sure SQL Server is configured to allow remote connections
    4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
    5. Test server connectivity with PING from the client machine
    6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine.  For example
    a. TELNET <server-name> 1433
    b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
    7. Check firewall settings if step 5 or 6 connectivity test fails

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Monday, February 27, 2017 9:39 AM
    Answerer
  • Connection timeout on pre-Login often means SQL Server is to busy to handle the login request. Check CPU workload of SQL Server.

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Monday, February 27, 2017 9:41 AM
    Moderator
  • Sorry, I still get this

     

    Many Thanks & Best Regards, Hua Min

    Tuesday, February 28, 2017 5:13 AM
  • Hi HuaMin,

    Are you able to connect to the target SQL Server with same connection string using SQL Server Management Studio?

    Firstly, please check that if your DNS record is wrong, for more details about checking DNS, see:https://gallery.technet.microsoft.com/Check-DNS-Server-and-DNS-887ef37b.

    Also I would recommend you check if your SQL Server is listening on static port 33333 in SQL Server Configuration Manager,  then enter “IP, port number” or “machinename, port number” in Server Name textbox and check if it is successful.

    Thanks,
    Lydia Zhang


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.



    Tuesday, February 28, 2017 6:03 AM
    Moderator
  • Hi,

    I think this is your first installation of SQL where you install the SQL with Windows Authentication, after installation you are trying to connect with sa.

    if I am correct then please login with windows Authentication 

    1. right click on Server propertise

    2. select Security

    3. Check the server authentication (if the Option is in Window Authentication  Mode then change to SQL Server second option and save and restart the SQL Services.

    Then you connect with sa if you know the password orelse change the password for sa and connect.

    Hope this solve your issue.

    Many Thanks.


    Afzalkhan

    Tuesday, February 28, 2017 6:21 AM
  • I do enable port 33333, on the server, by creating Inbound/outbound rule on Firewall, but I still get

    TITLE: Connect to Server
    ------------------------------
    
    Cannot connect to 182.173.77.208,33333.
    
    ------------------------------
    ADDITIONAL INFORMATION:
    
    Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=0; handshake=15010;  (Microsoft SQL Server, Error: -2)
    
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
    
    ------------------------------
    
    The wait operation timed out
    
    ------------------------------
    BUTTONS:
    
    OK
    ------------------------------
    


    when I put
    182.173.77.208,33333
    in SSMS to connect.

    Many Thanks & Best Regards, Hua Min

    Tuesday, February 28, 2017 7:23 AM
  • Hi HuaMin,

    Looks like that your SQL Server is busy. Is your SQL Server getting enough of the server’s memory? And is there any possibility that you can restart your SQL Server Service?

    Regards,
    Lydia Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, February 28, 2017 9:35 AM
    Moderator
  • No, but at the same time, within the server, I was able to connect to that, by putting SERVERNAME\DBNAME, using one other SSMS session.

    Many Thanks & Best Regards, Hua Min



    • Edited by HuaMin Chen Tuesday, February 28, 2017 10:03 AM
    Tuesday, February 28, 2017 9:59 AM
  • Hi HuaMin,

    What do you mean that use other SSMS session? You use local SSMS to connect to SQL Server? Have you checked the SQL Server memory and DNS record?

    Regards,
    Lydia Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, March 01, 2017 9:11 AM
    Moderator
  • Hi,

    Yes, I use SSMS within the server and am able to connect to that by "Server_name\DB_name", and can connect to that fine. But why the problem arise, with "server IP, 33333"?


    Many Thanks & Best Regards, Hua Min


    • Edited by HuaMin Chen Thursday, March 02, 2017 3:10 AM
    Thursday, March 02, 2017 3:09 AM
  • Hi,

    Any help?


    Many Thanks & Best Regards, Hua Min

    Friday, March 03, 2017 4:05 AM
  • Hi HuaMin,

    In your original post, do you connect to remote SQL Server from Visual Studio? If so, how about using "ServerName\Instance Name" as ServerName in Visual Studio?

    Also do you check the memory of SQL Server as follows and DNS record? Please also post the screenshot about your configured port in SQL Server Configuration Manager.


    Thanks,
    Lydia Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 06, 2017 9:29 AM
    Moderator
  • Thanks. Where to get DNS record within SQL server? Here is what I get

    What do you want to see, within SS configuration manager?

    Many Thanks & Best Regards, Hua Min

    Monday, March 06, 2017 3:16 PM
  • Hi HuaMin,

    Please review my previous post about checking DNS. Also we need to check your configured TCP/IP port in SQL Server Configuration Manager.

    Thanks,
    Lydia Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, March 07, 2017 8:26 AM
    Moderator
  • Sorry, I cannot get into this.

    Many Thanks & Best Regards, Hua Min

    Tuesday, March 07, 2017 8:52 AM
  • Hi HuaMin,

    Remove dot from the link.

    https://gallery.technet.microsoft.com/Check-DNS-Server-and-DNS-887ef37b

    Regards,
    Lydia Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, March 07, 2017 8:57 AM
    Moderator
  • Hi,
    Is it to check DNS ONLY IF there is on DNS server? I do not have any DNS server to my current SQL server setup.


    Many Thanks & Best Regards, Hua Min

    Tuesday, March 07, 2017 2:15 PM
  • Hi,

    Any other help?


    Many Thanks & Best Regards, Hua Min

    Tuesday, March 21, 2017 3:28 AM
  • Hi HuaMin,

    This blog describes details that how DNS affects connection to SQL Server. In your client machine, run the following commands under command windows and share us the result.
    1) ping -a HostName (and Hostname.domianname.com)
    2) Ping -a IPAddress ( If this only returns HostName, but not FQDN, it usually means no DNS entry was found for the host that you install SQL Server)
    3) nslookup
              > HostName. domianname.com
              > HostName. domianname.com
              > IPAddress
              > IPAddress

    In addition, please share us TCP/IP port configuration in SQL Server Configuration Manager. Also follow the steps in this official article as Olaf’s post to troubleshoot this connection problem and share us result of your scenario in each step.

    Thanks,
    Lydia Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.



    Friday, March 24, 2017 3:36 AM
    Moderator
  • Hi,
    Here are what I've got

    C:\Users\Peter>ping -a my-friend.co
    
    Pinging my-friend.co [182.173.77.208] with 32 bytes of data:
    Reply from 182.173.77.208: bytes=32 time=3ms TTL=123
    Reply from 182.173.77.208: bytes=32 time=1ms TTL=123
    Reply from 182.173.77.208: bytes=32 time=5ms TTL=123
    
    Ping statistics for 182.173.77.208:
        Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 5ms, Average = 3ms
    Control-C
    ^C
    C:\Users\Peter>nslookup my-friend.co
    Server:  ns78.net-yan.com
    Address:  210.3.59.78
    
    Non-authoritative answer:
    Name:    my-friend.co
    Address:  182.173.77.208



    Many Thanks & Best Regards, Hua Min

    Friday, March 24, 2017 4:10 AM
  • Hi HuaMin,

    From your screenshot, there is no problem with DNS.

    What is the result using "HostName\instance name" to connect to your SQL Server?

    In addition, please share us TCP/IP port configuration in SQL Server Configuration Manager. Also follow the steps in this official article as Olaf’s post to troubleshoot this connection problem and share us result of your scenario in each step.

    Thanks,
    Lydia Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Friday, March 24, 2017 6:33 AM
    Moderator
  • Hi,

    I'm able to connect to

    my-friend.co\Instance_name

    within SS management studio, on relevant server, while I’ve got this problem (from outside Desktop).

    TITLE: Connect to Server
    
    ------------------------------
    
    Cannot connect to my-friend.co\SS2012EXPR.
    
    ------------------------------
    
    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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
    
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
    
    ------------------------------
    
    BUTTONS:
    
    OK
    
    

    What TCP/IP details I need to show to you below?




    Many Thanks & Best Regards, Hua Min

    Friday, March 24, 2017 8:28 AM
  • Having reviewed this thread, I have two questions:

    1) Have you checked that the browser is running?
    2) Is 33333 actually the port that SQL Server is listening on?

    It seems that something is listening on port 33333, but it may not be SQL Server.

    Friday, March 24, 2017 10:37 PM
  • Hi,

    1. What do you mean by 'browser is running'?

    2. I do connect to the server through port 33333.


    Many Thanks & Best Regards, Hua Min

    Friday, March 24, 2017 11:14 PM
  • 1. What do you mean by 'browser is running'?

    The SQL Browser service. When you specify an instance on the form SERVER\INSTANCE, the client API connects to UDP port 1434 and the browser service returns the port number to use. Thus, to be able to connect by instance name, the Browser service must be running and UDP 1434 must be open in anyfire wall. (Note that UDP is a different protocol from TCP, which is the protocol used for the communication to SQL Server.)

    2. I do connect to the server through port 33333.

    How do you know that this is the port? Can you run xp_readerrorlog for the server in question and post the first 50 lines?

    Saturday, March 25, 2017 10:05 AM
  • Hi,

    1. Does it mean both server and client should be open on UDP 1434 in any firewall?

    2. Here are the lines I've got

    2017-03-17 14:23:59.980	Server	Microsoft SQL Server 2012 - 11.0.2218.0 (X64) 
    	Jun 12 2012 13:05:25 
    	Copyright (c) Microsoft Corporation
    	Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
    
    2017-03-17 14:23:59.980	Server	(c) Microsoft Corporation.
    2017-03-17 14:23:59.980	Server	All rights reserved.
    2017-03-17 14:23:59.980	Server	Server process ID is 1988.
    2017-03-17 14:23:59.980	Server	System Manufacturer: 'Parallels Software International Inc.', System Model: 'Parallels Virtual Platform'.
    2017-03-17 14:23:59.990	Server	Authentication mode is MIXED.
    2017-03-17 14:24:00.000	Server	Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL11.SS2012EXPR\MSSQL\Log\ERRORLOG'.
    2017-03-17 14:24:00.000	Server	The service account is 'NT Service\MSSQL$SS2012EXPR'. This is an informational message; no user action is required.
    2017-03-17 14:24:00.000	Server	Registry startup parameters: 
    	 -d c:\Program Files\Microsoft SQL Server\MSSQL11.SS2012EXPR\MSSQL\DATA\master.mdf
    	 -e c:\Program Files\Microsoft SQL Server\MSSQL11.SS2012EXPR\MSSQL\Log\ERRORLOG
    	 -l c:\Program Files\Microsoft SQL Server\MSSQL11.SS2012EXPR\MSSQL\DATA\mastlog.ldf
    2017-03-17 14:24:00.000	Server	Command Line Startup Parameters:
    	 -s "SS2012EXPR"
    2017-03-17 14:24:07.020	Server	SQL Server detected 1 sockets with 1 cores per socket and 1 logical processors per socket, 1 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2017-03-17 14:24:07.020	Server	SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2017-03-17 14:24:07.020	Server	Detected 4095 MB of RAM. This is an informational message; no user action is required.
    2017-03-17 14:24:07.030	Server	Using conventional memory in the memory manager.
    2017-03-17 14:24:10.090	Server	This instance of SQL Server last reported using a process ID of 2004 at 17/3/2017 14:22:58 (local) 17/3/2017 6:22:58 (UTC). This is an informational message only; no user action is required.
    2017-03-17 14:24:10.130	Server	Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2017-03-17 14:24:10.190	Server	Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2017-03-17 14:24:10.370	Server	Software Usage Metrics is disabled.
    2017-03-17 14:24:10.530	Server	CLR version v4.0.30319 loaded.
    2017-03-17 14:24:10.630	spid8s	Starting up database 'master'.
    2017-03-17 14:24:10.890	spid8s	1 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
    2017-03-17 14:24:10.920	spid8s	0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
    2017-03-17 14:24:12.370	Server	Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2017-03-17 14:24:13.040	spid8s	SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2017-03-17 14:24:13.070	spid8s	SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2017-03-17 14:24:14.850	spid8s	SQL Trace ID 1 was started by login "sa".
    2017-03-17 14:24:15.180	spid8s	Server name is 'WIN-0NGDCBCTNKP\SS2012EXPR'. This is an informational message only. No user action is required.
    2017-03-17 14:24:16.130	spid12s	A self-generated certificate was successfully loaded for encryption.
    2017-03-17 14:24:16.540	spid12s	Server is listening on [ 'any' <ipv6> 61240].
    2017-03-17 14:24:16.540	spid12s	Server is listening on [ 'any' <ipv4> 61240].
    2017-03-17 14:24:16.550	spid12s	Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SS2012EXPR ].
    2017-03-17 14:24:16.550	spid12s	Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SS2012EXPR\sql\query ].
    2017-03-17 14:24:16.550	spid12s	Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
    2017-03-17 14:24:16.570	Server	SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
    2017-03-17 14:24:16.570	spid12s	SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2017-03-17 14:24:16.610	Server	The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-0NGDCBCTNKP.my-friend.co:SS2012EXPR ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
    2017-03-17 14:24:16.610	Server	The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/WIN-0NGDCBCTNKP.my-friend.co:61240 ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
    2017-03-17 14:24:21.380	Logon	Error: 18456, Severity: 14, State: 38.
    2017-03-17 14:24:21.380	Logon	Login failed for user 'NT SERVICE\ReportServer$SS2012EXPR'. Reason: Failed to open the explicitly specified database 'ReportServer$SS2012EXPR'. [CLIENT: <local machine>]
    2017-03-17 14:24:33.260	Logon	Error: 18456, Severity: 14, State: 38.
    2017-03-17 14:24:33.260	Logon	Login failed for user 'NT SERVICE\ReportServer$SS2012EXPR'. Reason: Failed to open the explicitly specified database 'ReportServer$SS2012EXPR'. [CLIENT: <local machine>]
    2017-03-17 14:24:39.450	Logon	Error: 18456, Severity: 14, State: 38.
    2017-03-17 14:24:39.450	Logon	Login failed for user 'NT SERVICE\ReportServer$SS2012EXPR'. Reason: Failed to open the explicitly specified database 'ReportServer$SS2012EXPR'. [CLIENT: <local machine>]
    2017-03-17 14:24:47.150	spid8s	Starting up database 'msdb'.
    2017-03-17 14:24:47.180	spid9s	Starting up database 'mssqlsystemresource'.
    2017-03-17 14:24:47.660	spid9s	The resource database build version is 11.00.2218. This is an informational message only. No user action is required.
    2017-03-17 14:24:49.150	spid9s	Recovery completed for database mssqlsystemresource (database ID 32767) in 1 second(s) (analysis 353 ms, redo 0 ms, undo 678 ms.) This is an informational message only. No user action is required.
    2017-03-17 14:24:50.450	spid9s	Starting up database 'model'.
    2017-03-17 14:24:51.760	spid9s	Clearing tempdb database.
    2017-03-17 14:24:54.490	spid9s	Starting up database 'tempdb'.


    Many Thanks & Best Regards, Hua Min


    Sunday, March 26, 2017 2:21 PM
  • 1. Does it mean both server and client should be open on UDP 1434 in any firewall?

    That depends a little on what firewall you have. Windows firewall only cares about incoming traffic, why it only matters on the server.

    For a firewall that also monitors outgoing traffic, you may also have to make configuration, but outgoing traffic is usually configured in terms of which destination and port a certain program may access. You don't open outgoing ports. (Which is good, because you rarely know these port numbers.)

    2. Here are the lines I've got

    2017-03-17 14:24:16.540     spid12s     Server is listening on [ 'any' <ipv6> 61240].
    2017-03-17 14:24:16.540     spid12s     Server is listening on [ 'any' <ipv4> 61240].

    So this server is listening on port 61240 and not 33333 as you tried with. Try conneting with WIN-0NGDCBCTNKP,61240.

    • Marked as answer by HuaMin Chen Tuesday, March 28, 2017 9:42 AM
    Sunday, March 26, 2017 3:01 PM
  • Oh, by the way:

    2017-03-17 14:23:59.980     Server     Microsoft SQL Server 2012 -

    11.0.2218.0 (X64)

         Jun 12 2012 13:05:25      Copyright (c) Microsoft Corporation

    Seems like this instance is a bit behind with regards to service packs. You should apply SP3 on this instance.

    Sunday, March 26, 2017 3:02 PM
  • Hi,
    >> Try conneting with WIN-0NGDCBCTNKP,61240.

    Do I put such on SSMS, within client machine?

    Many Thanks & Best Regards, Hua Min

    Sunday, March 26, 2017 3:27 PM
  • Try conneting with WIN-0NGDCBCTNKP,61240.

    Do I put such on SSMS, within client machine?

    As I said, use this string to connect the instance you're having problem with. Whether you use SSMS, SQLCMD or a client application.

    Sunday, March 26, 2017 4:24 PM
  • Hi,

    1. I create Inbound UDP rule to pass port 61240, on both client and server
    2. Create line on host file, to server WIN-0NGDCBCTNKP, but I still get such problem

    TITLE: Connect to Server
    ------------------------------
    
    Cannot connect to WIN-0NGDCBCTNKP,61240.
    
    ------------------------------
    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: TCP Provider, error: 0 - The wait operation timed out.) (Microsoft SQL Server, Error: 258)
    
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=258&LinkId=20476
    
    ------------------------------
    
    The wait operation timed out
    
    ------------------------------
    BUTTONS:
    
    OK
    ------------------------------
    


    Many Thanks & Best Regards, Hua Min

    Monday, March 27, 2017 2:23 AM
  • I don't much about your network, but I see little point in opening UDP port 61240. SQL Server listsens on TCP ports, not UDP.

    As for WIN-0NGDCBCTNKP this is the name of the server from which you posted the errorlog file.

    Monday, March 27, 2017 7:29 AM