November 15, 2011 at 11:20 pm
What's the general accepted method for blocking remote access to SQL Server 2008?
Local code access only is required by the app in question.
November 16, 2011 at 9:14 am
In SQL Server Configuration Manager, disable all the network libraries but Shared Memory. Shared Memory can only be used locally. This will require a restart of SQL Server (not the OS) to take effect.
K. Brian Kelley
@kbriankelley
November 22, 2011 at 10:27 pm
Sounds like a nice easy method, thanks!
Any drawbacks?
November 23, 2011 at 2:12 am
by external / remote do you mean from outside of your organisation or nothing can use SQL apart from anything which runs on the SQL host?
e.g block all WAN traffic but not LAN traffic?
if it is block all traffic from WAN and LAN so that only code and applications which run on the SQL host can use the SQL server then yeah, just enable shared memory
if you want to allow just LAN traffic and not WAN, I would speak to your network admins and ask them to block the SQL ports on the incoming firewall so that for example port 1433 traffic is stopped when it comes in from the internet
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply