Not able to telnet 1433 | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Not able to telnet 1433

Hi I am having a Win 2003 machine on which SQL 2000 Ent Edition os installed.
The problem is that I am not able to telnet its own IP on port 1433.
The port is the default. It has not been changed.
It has been mentioned properly in Server Network Utility & Client Network Utility.
It is not seen in the Errorlog too unlike other SQL machines. I read an article where it says 1433 should be mentioned in registry…
HKLM/Software/Microsoft/MSSQLServer/MSSQLServer/SuperSocketNetLib/TCP/TCPDynamicPorts Port 1433 is already there in the mentioned key in the registry. What else could be the problem? Regards
Hi,<br />BOL says about remote access Option :<br />ensure you have set RPC to Accept Remore Connection :<br />Under Remote server connections, select or clear the Allow other SQL Servers to connect remotely to this SQL Server using RPC check box<br /><br />or <br />sp_configure ‘remote access’, 1<br /><br />and then try to connect it ! what error it thraws !<br /><br /><img src=’/community/emoticons/emotion-1.gif’ alt=’:)‘ /><br />Regards<br /><br />Hemantgiri S. Goswami<br />[email protected]<br />"Humans don’t have Caliber to PASS TIME , Time it self Pass or Fail Humans" – by Hemantgiri S. Goswami<br />
Check what is the port sQL Server is lisetening to, I guess there is a change in Windows 2003 and I have same problem. As we change SQL port number and do not use 1433 as default. KBA;en-us;842242 for reference and worth checking Hemant’s reference. Satya SKJ
Contributing Editor & Forums Moderator
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Why would you want to telnet into port 1433? Is there another problem you are having with the actual SQL server installation? MeanOldDBA
[email protected] When life gives you a lemon, fire the DBA.
assuming that you are using telnet to try to check that basic connectivity is working, is the port in a LISTENING state when you run netstat -a? Cheers
Hi all, i recently has the same issue, this is due to Windows 2003 not supporting SQL 2000 without sp3 or later.
You need to install SP3 or later to get this solve. AKTHAR