On the Server Properties page, click the Connections page. From the local server, you can disable a remote server configuration to prevent access to that local server by users on the remote server with which it is paired. To enable remote procedure calls RPC against a remote server, you must set up login mappings on the remote server and possibly on the local server that is running an instance of SQL Server. This configuration enhances the security of your server by reducing its attackable surface area.
Before using RPC you must enable this feature. Remote login mappings must be set up on the remote server. Using these mappings, the remote server maps the incoming login for an RPC connection from a specified server to a local login. For SQL Server authenticated local logins, you do not have to set up a login mapping on the local server.
SQL Server uses the local login and password to connect to the remote server. For Windows authenticated logins, set up a local login mapping on a local server that defines what login and password are used by an instance of SQL Server when it makes an RPC connection to a remote server. No local mapping is required for Joe , because the default is to use the same login name and password, and serverReceive has a mapping for Joe. These attributes include the version number of SQL Server, the type and number of processors in the computer, and the version of the operating system.
From the local server, you can view databases, files, logins, and tools for a remote server. Linked Servers Database Engine. Configure the remote access Server Configuration Option. Click on Windows icon. This will open the New Inbound Rule Wizard. In the Protocol and Ports window, mention the protocols and ports to which a rule applies. In the Action window, select the Allow the connection option to specify the action to be taken when a connection matches the conditions specified in the rule and click on Next.
In the Profile window, specify the profile for which the rule applies. Here we have selected Domain. In both case the New Inbound Rule Wizard will appear. Under the Rule Type choose Port and click the Next button:. From this link you can more informed of all rule types which are shown in the image above. In the Protocols and Ports there are a several options that you can choose, depending on which type of protocols you select.
As we mentioned at the beginning of the article TCP is used for the default instance and named instance if is the only instance installed on the machine and default port is For this example, select the UDP protocol and in the Specific local ports enter port number In the Action dialog choose Allow the connection and click the Next button:.
In the Profile dialog choose all three profiles and click the Next :. Note : When we give the name of the rule, please write some descriptive name that you can understand later, when you need to find them or edit in the Inbound Rules list.
In the Program under the Services click the Customize button:.
0コメント