It is an honor to be featured in Gartner 2019 Magic Quadrant for Datacenter Backup and Recovery Solutions. Gartner’s MQ sets a high standard and earning a place on their grid is a great affirmation that Acronis is delivering on our mission to protect all data, apps, and systems.
SQL problem unable to see port 1433
Dear Team,
I have installed windows server 2008 R2 and SQL Enterprize Server 2008 R2 on my server.
But there is some problem ...when i run the following command.
netstat -a -n , i am not able to see the SQL port 1433 as listening.
The connections are enabled on the firewall end.
What can be the possible reson how can i switch on the Port 1433 , is there something wrong in SQL installation.
Thanks & Regards
Pranav IT
I have installed windows server 2008 R2 and SQL Enterprize Server 2008 R2 on my server.
But there is some problem ...when i run the following command.
netstat -a -n , i am not able to see the SQL port 1433 as listening.
The connections are enabled on the firewall end.
What can be the possible reson how can i switch on the Port 1433 , is there something wrong in SQL installation.
Thanks & Regards
Pranav IT
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
If you have installed a named instance, the port is usually different from 1433, and defined dynamically, as the article the above link points to mentions. In that case you either need to fix the port, and provide it with each connection if different from 1433, or let SQL Browser manage the port negotiation. SQL Browser uses 1434/udp for that, and is asked for ports of a specific instance.
The problem is you did not configured the network protocols in the SQL server configuration manager tool you can find under the program group in the start menu.
You should enable TCP/IP and Named Pipes since AFAIK those are not enabled by default.
You'll have to restart the SQL server service in order for you to see the port.
You should enable TCP/IP and Named Pipes since AFAIK those are not enabled by default.
You'll have to restart the SQL server service in order for you to see the port.
Okay I will recheck, can I remove the Enterpize 2008 R2 edition and put the Standard edition for SQL 2008 will it soilve the problem.
How can the SQL browser manage the Port negotiation, can any body help i dont want to uninstall the server.
Changing from Enterprise to Standard will not change anything in regard of protocols and ports.
Start your SQL Server Configuration Manager, go into SQL Server Network Configuration, Protocol for ..., and check if TCP is enabled. Then look into the TCP properties of that entry, tab IP Addresses. You should have either Dynamic TCP Ports set with the port number, or TCP Port. The latter is a static setting.
SQL Browser will work as long as you make sure the service named the same is running.
Start your SQL Server Configuration Manager, go into SQL Server Network Configuration, Protocol for ..., and check if TCP is enabled. Then look into the TCP properties of that entry, tab IP Addresses. You should have either Dynamic TCP Ports set with the port number, or TCP Port. The latter is a static setting.
SQL Browser will work as long as you make sure the service named the same is running.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial