Topics from the Microsoft SQL Server Protocols team - Netlibs, TDS, SQL Browser, etc.
Ever get a GNE? Ever wonder why SQL Discovery doesn't seem to be consistent? Ever get trapped by Window's firewall? Confused about VIA? Then, this is the blog site for you to watch.
This blog is run by the SQL Server protocols component team. This is the team responsible for the networking in SQL Server. This includes Discovery (SSRP), TDS, SOAP, transports like TCP, Named Pipes, and VIA. In this blog we hope to proactively answer many of the recurring issues that we see our customers running into. We should be able to tell you how to do some of the more subtle configurations and how to diagnose issues you're running into more efficiently (We've added TONS of diagnostics in SQL Server 2005). We'll show you how to use them.
Thanks and hopefully you'll find this useful!
The SQL Server Protocols team
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights
I am facing the TimeOut Expired issue. As given, I tried "telnet 126.96.36.199 1433" after replacing the IP address and I get an error 'Connect failed' when tried remotely and 'Connection to host lost' when tried locally on the server.
What do I need to do? Everything was working fine until last week.
I am having problems with connecting to an SQL server via telnet. I was getting the connection failed, but resolved that by adding port to TCP in SQL server config. However now the connection just times out without asking for user name or password. It does this locally and remotely.