Not Allowing Remote Access

  • Could someone please help clarify what is the ramifications for not allowing remote access, which allows remote procedure calls.

    I have been asked by our audit department to disable remote access and want to insure that it will not impact log shipping, linked server process or any DTS jobs that we run.

    The documentation that I have found does not directly address the impact of disabling remote access.

    Thanks for the help!

    Charles L. Nichols


    Charles L. Nichols

  • What is your definition of "remote access"? Are you just disabling RAS to an interior LAN, or are you planning to somehow prevent network access to the SQL Server machine entirely (and if so how did you plan to do so).

    Windows itself requires on RPC calls, so if you plan to do something like disable port 135 on the SQL Server machine, you are likely to screw up other things that may be occuring inside windows itself, especially if you have AD or Exchange or other applications.

    Not to mention SQL Server can run on different protocols, some of which are difficult to tell whether they are "remote" or "local" (depending on your definition of each).

    Putting the SQL Server behind a firewall would allow you to filter by source IP address for example (of course, if it isn't behind a firewall now and is sitting on the internet, just paint a target on it).

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply