14,494 questions
What error message do you get?
Did you start the browser service?
How do you connect? By instance name or port?
Unable to connect remotely to new SQLServer 2022 Express
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 89%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBV%3C/text%3E%3C/svg%3E)
Bob Vitter
201
Reputation points
I setup a VM (VMWare) to test SQL Server 2022
I used SQL Server Config Mgr to allow remote access and set the port
I can connect to the instance locally from SSMS and and connect to other instances (2019) from this VM
but I can't connect remotely to this instance from this VM or a physical PC
The VM and PC are in the same domain and I am using the domain Admin user id
SQL Server Other
Accepted answer
-
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator2023-05-05T21:34:09.8966667+00:00 -
Bob Vitter 201 Reputation points
2023-05-05T23:27:58.6166667+00:00 Starting the Browser worked - thank you
-
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator
2023-05-06T08:35:46.6966667+00:00 Great to hear that there was a simple solution!
I converted my comment to an Answer in case you like to accept it as such.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 41%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Thirthaprasad S G 31 Reputation points2024-11-26T06:42:28.2633333+00:00 MS SQL Server 2022 Developer Edition. With local SSMS it is working fine.
- Network TCP connection with 1433 enabled (For Localhost and IP Address)
- Firewall incoming connections for 1433 port enabled on both systems
- "Allow Remote Connections" enabled for the SQL instance
- SQL Server and SQL Server Browser services are Running
But it doesn't allow Local / Remote Telnet or Remote connection to the instance with the usual error: Network related / instance specific (Below screenshot)
What else is required to enable Remote connections
Please note as mentioned above, even the telnet to localhost with 1433 port doesn't work.
Can the experts throw some light on this peculiar issue, anything specific to version 2022 missing...?!
Thanks
Sign in to comment -
4 additional answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 3%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Michael 5 Reputation points2023-09-11T19:58:49.0633333+00:00 By default SQLExpress 2022 has TCP and Named Pipes disabled as protocols for the instance. If you open SQL Server Configuration Manager and browse to SQL Server Network Configuration > Protocols for <NAMED INSTANCE> you will see three protocols enabled. Shared memory is the only one enabled. Enable TCP/IP and restart the SQL Server service.
Provided you are allowing the ports you need through the firewall, you will be connected. You had indicated that you disabled the firewall, so that will likely not be an issue.
More here about what ports to open on the firewall if you would like to turn it back on.
https://learn.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?view=sql-server-ver16 -
Thirthaprasad S G 31 Reputation points
2024-11-27T06:33:08.04+00:00 Hi All,
I forgot to mention that, even the LOCALHOST was unable to connect to port 1433 in the present scenario. In previous versions of SQL (2014) though it was connecting Remotely but wasn't happening with localhost.
I have finally figured it out. It is the TCP/IP port for "IPAll" portion which was not specified to use 1433 leading to this connectivity issue with localhost as well as from Remote Hosts. Once I specified the port 1433 in IPAll settings and restarted the SQL Server service, both connections worked successfully.
Below is the screenshot of that particular setting which worked for me...!
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Bruce (SqlWork.com) 77,686 Reputation points Volunteer Moderator2023-05-05T14:48:12.56+00:00 Be sure the sql server port 1433 is open on the firewall of both the vm and hosting O/S
also check if the vm network is bridged or proxied behind the host. Can you ping the vm from a remote box.
-
Bob Vitter 201 Reputation points
2023-05-05T15:59:59.54+00:00 I disabled the Firewall on the VM
The network is not bridged or proxied and I can Ping the VM
WSUS found the VM
VM has SSMS 19.0.2 and SQLExpress 2022
Physical PC has SSMS 18.12.1 and SQLExpress 2019
The VM SSMS can connect to the physical PC SQLExpress but does not see the VM SQLExpress