How do I get around this error in the most secure fashion running SQL 2008 on a Windows Server 2012 where clients must access the sql server from remote locations?
Whenever I make my connection strings as:
connectionString="Server=mysql.somedomain.com\SQLExpress;Database=xyz; User ID=qrs; Password=abc"
Local connections seem to work fine as Server=.\SQLExpress, so those are found fine.
However, that won't work for remote clients and even local clients when TCP is used.
Do I have to open port 1433 and set SQL 2008 to use a single static IP? I've seen that port and it gets attacked via DOS.
Michael Barber