Remote Access: User Authentication, SQL Server, and Access Controls

This report examines the process of enabling remote access, focusing on key aspects such as user authentication, SQL server configuration, and access controls. The report begins by outlining the initial steps for establishing remote connections, including the use of dial-up connections, VPNs, and virtual private networks. It then details the procedures for managing user account details and passwords, highlighting the importance of RADIUS authentication and authentication profiles. The report emphasizes the significance of connecting to the SQL server to enable single-user accounts for both local and remote access, thereby enhancing network security. It also differentiates between local and remote servers, explaining how administrators can resolve related issues, such as those addressed through remote desktop connections. Furthermore, the report explores how access controls are altered once remote access is enabled, emphasizing the role of proper configuration in managing stored procedures and preventing unauthorized access. The report concludes by underscoring the importance of a secure and well-managed remote access setup for maintaining network integrity.

Running head: ENABLING REMOTE ACCESS
Enabling Remote Access
Name of the Student
Name of the University
Author’s Note:

1
ENABLING REMOTE ACCESS
1. The system administrators currently create the Ken 7 users in every computer where
the users require access. There are few steps that would help the users in connecting to the
network eventually. They could complete this step with the help of a specific dial up connection
or any VPN or virtual private network connection (Jaha & Libya, 2015). Any dial up connection
needs both the client computer and the server computer for properly configuring the modem.
This client or the server makes a connection on the analog public telephone networks. The
remote users can easily identify themselves by means of remote access authentication. This
would also make the connection safe and secured.
2. The procedure for making any change to the account details or the passwords of the
users is much different from the remote users. For the remote users, this procedure or process
comprises of three important steps. These steps are as follows:
i) The first step is the setting up of RADIUS authentication. The server profile eventually
identifies all the external service for authentication and provides necessary instructions.
ii) The second step is the creation of an authentication profile. It would be responsible for
identifying the specific server profile (Maiti, Kist & Maxwell, 2015). The password change
message is added in this step.
iii) The final step is the committing of the configuration.
3. The specific administrators should connect to the SQL server for allowing a single user
account to be utilized for the local and remote access. This would eventually restrict the overall
access of the existing local users and the network would be secured. Moreover, the connection to
the SQL server would also be responsible for securing the database and hence this database
could be utilized by the users.

2
ENABLING REMOTE ACCESS
4. The main difference between a local server and a remote server is that a local server is
on the personal computer; however, a remote server is on any other computer. Thus, the user
defined accounts on personal computers are local servers and that on the other computer is
remote server (Maiti, Kist & Maxwell, 2015). These user accounts could be stored either in the
Active Directory or on the local computer. It thus uniquely identifies the computer within a
domain. These types of differences could be resolved by the administrators. The remote desktop
connections would be the best way in solving such issues.
5. The process for defining the access controls eventually change once the remote access
is enabled. This process is altered when the configuration of the remote access is being done
properly. The option for remote access manages the execution of the stored procedures from all
the remote or local servers where the instances of the SQL server are running (Gill, Yang &
Wang, 2013). The perfect configuration of the remote access is responsible for managing or
preventing the local stored procedures from being run from the remote servers from being run on
local servers. Hence, the access is controlled properly without having any issues, making the
remote access perfect.

3
ENABLING REMOTE ACCESS
References
Gill, K., Yang, S. H., & Wang, W. L. (2013). Secure remote access to home automation
networks. IET Information Security, 7(2), 118-125.
Jaha, A. A., & Libya, M. (2015). Performance Evaluation of Remote Access VPN Protocols on
Wireless Networks. International Journal of Computer and Information
Technology, 4(02).
Maiti, A., Kist, A. A., & Maxwell, A. D. (2015). Real-time remote access laboratory with
distributed and modular design. IEEE Transactions on Industrial Electronics, 62(6),
3607-3618.