Timeline for Problems with remote accessing a new instance in SQL Server 2019
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2022 at 21:19 | vote | accept | Technology Researcher | ||
| Feb 22, 2022 at 21:19 | answer | added | Technology Researcher | timeline score: 0 | |
| Feb 22, 2022 at 21:19 | comment | added | Technology Researcher | Yes, I have managed to fix it, I changed the listening port in the configuration manager and then open up a firewall rule, and restarted my services. for some reason I wasn't able to connect but after a total vm restart I was able to connect. So I can only assume I forgot to restart a specific server accept I don't know which one, as I restarted all of the sql servicers except the agent services because they are disabled. | |
| Feb 22, 2022 at 3:20 | comment | added | Charlieface |
You can connect locally because it doesn't use TCP it uses shared memory, and in any case the firewall doesn't normally block localhost
|
|
| Feb 21, 2022 at 15:16 | review | Close votes | |||
| Mar 15, 2022 at 3:08 | |||||
| Feb 21, 2022 at 14:57 | comment | added | Doug Deden | Does this answer your question? Setting Up Named SQL Server Instance Network Connection | |
| Feb 21, 2022 at 9:12 | comment | added | Tibor Karaszi | You don't use SSMS for this. You use the "SQL Server Configuration Manager" tool. | |
| Feb 20, 2022 at 18:56 | comment | added | Technology Researcher | How do I set the port on the instance if ssms cannot connect to it locally? | |
| Feb 20, 2022 at 18:56 | comment | added | Technology Researcher | ow, that's a good point, I didn't knew that. I was thinking about that too but rather weird that I was able to connect locally. I have connected to server with multiple instances withouth the need to enter a port in the connectionstring or via ssms | |
| Feb 20, 2022 at 14:51 | history | migrated | from stackoverflow.com (revisions) | ||
| Feb 20, 2022 at 13:56 | comment | added | Charlieface |
Each instance is on a separate port. You need to open the firewall to sqlservr.exe on any port.
|
|
| Feb 20, 2022 at 11:09 | comment | added | AlwaysLearning | What TCP/IP port(s) is the NETWORKMONITOR instance listening on? Only one instance can be listening on tcp/1433 on any particular address, so if the SQLEXPRESS instance was already listening there then the new instance must be listening on a different port. | |
| Feb 20, 2022 at 10:08 | history | asked | Technology Researcher | CC BY-SA 4.0 |