Open SQL Server Configuration Manager
Ensure TCP/IP is enabled
2. View properties, some may be set to 1433
My machine has not been set up, is this:
The port number is 2104, you can also set a large number of the port number, set up after the SQL SERVER restart, others do not restart
Configure the firewall's advanced settings to C:\Program Files\Microsoft SQL Server\mssql10. Sqlexpress\mssql\binn\sqlservr.exe, "new rule" to "inbound rules."
Set the UDP port 1434 new rule to inbound rules.
Otherwise, the client will not be able to access the dynamic port used by TCP due to less than 1434 ports, if you just do the experiment, simply turn off the firewall, save a lot of time to set.
Another: ( if the client is running in Windows Virtual PC (XP), the TCP dynamic port cannot be used for remote connections when using shared network (NAT), even if the firewall at both ends of the service is turned off. Automatically assigned IP addresses and host hosts within a virtual machine are not in a single network segment. When you use this option, the virtual machine is not listed as a stand-alone computer on the network. It is recommended that you choose to use < network adapter name >. In both networks, TCP port 1433 or all of your settings can be successfully connected remotely. )
Check to see if SQL Server and Windows Authentication mode is turned on, at first I only have Windows Authentication mode, how to log on, and then use the new username to log on after blending mode.
If the remote connection is too slow, you can change the timeout
Note that these two steps should restart the SQL Server service!
If you want to log in with a username, you can also create a new user, security \ login \ New Login name
The correct setting should be the following:
OK, Telnet should be no problem!