This comes up with a similar message of not being able to connect. One interesting thing is I can't get Remote Desktop working for a Server 2016 instance I set up to test on AWS either. I am a little bitter because Windows updates has continued to plague me and others with problems making everything that could go wrong, go wrong. It just seems to be Microsoft instances that are a heap of crap. I can connect to a PostgreSQL DB on RDS like a charm via a PowerShell script. I have tried the connection from a colleagues computer at a different location from a different IP (Whilst the SG rule was set to All Traffic & 0.0.0.0/0) I have a local DB setup and connected in MS SQL Server Management Studio I tried using different DNS servers but the hostname resolved to an IP address anyway so I don't think that would be a problem? My ISP is IdNet (UK) and they don't block ports or anything stupid like that.
I ticked 'Trust server certificate' for a laugh and tried that unticked too. Connection Properties: I've left these as default, except for Network Protocol which I have tried TCP/IP & Default. Authentication: SQL Server Authentication: username & master password for the instance Connection: I am using the suggested string for Server Name: '.,1433' and have tried different variations I ended up creating an All Traffic rule for 0.0.0.0/0 - Just in case. Security Group: Amazon adds your public IP address as an inbound rule which is helpful. I did try Zenmap and it came back with: '1433/tcp filtered ms-sql-s' - So I assume this is potentially up because it doesn't say down? Is there another way to confirm this? Ports: I have literally opened my computer up entirely by disabling the firewall and allowing ports 1433 & 1434. In a nutshell, I have checked the following: I have tried everything I can think of and different suggestions from other people all over the place. 40.v1' instance from MS SQL Server Management Studio remotely. I am trying to connect to an 'SQL Server Express Edition. I have been scratching my head on this one for three days now.
0 kommentar(er)
