Open WesToleman opened 2 years ago
Do connections with SSMS or other tools work from the same client machine? I'd guess the port is blocked by the firewall on the host.
Maybe try a tcp:
connection instead of named pipes.
Connections with SSMS and Invoke-SqlCmd
both work so it's not a firewall issue.
I've moved it over to where it (may) belong, i.e. the SQLServer PowerShell repo (which I recently opened for Issues).
Hi @Matteo-T, have you accidentally closed the transferred issue or is this solved?
@WesToleman - it was actually intentional. Based on my preliminary understanding, this has nothing to do with SMO and it's rather some SQL PowerShell issue. If that turns out to be incorrect, I'll move it back here and let David know.
@Matteo-T, I'm confused, this is issue 21 in the SqlServer PowerShell Module repository. I'm writing this comment from https://github.com/microsoft/SQLServerPSModule/issues/21
.
Oh I see. In that case, yes. I goofed up. Let me make it right. Sorry about that.
The SQL Powershell path provider times out when attempting to remotely access instances running on ports other than 1433.
Accessing the root path is fast and
Invoke-SqlCmd
connects to the instance without issueThere's no issue when accessing the instance from the host itself
Remotely accessing both default and named instances running on port 1433 works without issue.
Is there something I can reconfigure to work around this issue?