Support Secure Remote Access To Networks example essay topic

Public phone lines and a modem are a typical communication conduit to connect to a company network. Although wireless technology will definitely change our options for connecting to a network from a remote location in the next few years, a modem is still the connection device most commonly used. To allow this type of remote access, Remote Access Services must be set up. Setting up remote access is really a two-part process.

First, a RAS server needs to be installed and configured, second a RAS client has to be configured. Depending on the size of the network, the RAS server can be the primary network server or an additional server on the network that is specifically charged with handling remote access connections. Configuring a RAS server involves three main tasks. Installing network protocols: Windows 2000 allows clients to use TCP / IP, IPX / SPX, AppleTalk, or NETBEUI protocols to connect to network resources. In order to use the RAS services, the correct hardware must be installed.

These devices can use several different technologies, namely: analog modems, null modem, X. 25, or ISDN. Windows can support 256 modems, enabling RAS to serve as a powerful dial-up server. Although it is most common to make serial connections through modems, it is also possible for computers to communicate through two directly wired serial ports (null modem) where the cable that connects the computers fools them into thinking they are communicating through modems. X. 25 is an old, slow, wide area network protocol based on packet switching. It is limited to 56 Kbps and is being phased out by newer faster protocols. ISDN is a digital dial-up technology that offers better performance than analog modems, but is also being surpassed by other newer faster protocols. Configuring the Remote Access Service is the final task for configuring a RAS server.

Windows 2000 Server uses the Routing and Remote Access snap-in to start and configure the RAS server. Once the server is configured, the task of authentication pops up. Different authentication protocols can be used that must be negotiated by the remote clients for them to connect to the remote access server. A number of different authentication protocols are available. Some authentication protocols provide greater security than others. For example, the Password Authentication Protocol (PAP) uses clear text login names and passwords making it easier for hackers to steal logon and password information.

Whereas Challenge Handshake Authentication Protocol uses encryption and other methods to provide a more secure environment when the clients negotiate access. Another way to thwart an evil-doers plan to attack a system is to configure a server to do a callback. The remote connection can be configured so that the server will hang up after authenticating the user and then call back the user's phone number to reestablish the connection. Once the server is configured, user accounts must be enabled for dial-in access. Windows 2000 server has a tab in the user properties used to configure the dial-in information. The client computer must be configured with a LAN protocol or protocols that match those supported by the RAS server and network.

The client computer must also be outfitted with a device that allows it to remotely connect to the RAS server. Supporting a remote access system is no small task. Managing user accounts and the server can give any administrator a headache. The Gartner Group as reported by TRENDS says: "enterprises are increasingly turning to service providers to configure, own, and manage their remote communications infrastructures". One company they reported is Hitachi Metals America Ltd. As a result of outsourcing Hitachi's WAN to a service provider, three extra sites have connected to the corporate network, and twice the bandwidth is now available at the site.

They reported a $2,000 per month cost savings for the entire network by not using long distance links between sites. Technologies such as tunneling, encryption, and authentication provide secure links and give companies a pretty good level of comfort about having their valuable data pass over a provider's shared network. But there are still other problems to overcome, such as the major obstacle of call failure and not being able to connect to the ISP's server or the cost of implementing the services into a network. Managed access theoretically reduces this risk of not being able to connect to the ISP, but does not eliminate the risk and carries a heavier payment.

Services that need to be counted as costs for maintaining remote access services are: database administration like performance tuning; server administration such as operating system administration; network administration to include monitoring and performance tuning; data center operations like data backups; hardware and software licensing and upgrades; paper and other office supplies; training costs; help-desk support; maintenance contracts from hardware and software vendors; along with other facilities and utilities. With all the extra costs, its easier to see why the Hitachi company opted for the outsourcing of some of these costs. Motives will vary, some network administrators will want to reduce communications costs, others may want to offload management tasks and free up their employees to work on other tasks. Hitachi says they used to have a hard time keeping staff. Often after an employee were trained on a new access technology or a specific vendor's piece of equipment, they were out the door with a better offer in hand. By outsourcing the remote access the problem gets dumped on the service provider.

Whether using a public phone line and a modem or using a wireless network, remote access is necessary for most networks. Outsourcing may be a perfect solution to help offload or offset ever increasing costs of supporting such a network. Windows 2000 server has plug-in software to help support secure remote access to networks with out of the box functionality and support for administrators. Windows 2000 is a good solution for remote access services. i. Robert R einstein, 2000, Practical Microsoft Windows 2000 Server, Chapter 17 ii. Harris Kern, Stuart Gal up, Guy Ne miro, 2000, IT Organization: Building a Word Class Infrastructure, Chapter 3 .

Joe Habra ken, 2001, Absolute Beginner's Guide to Networking, Third Edition, Chapter 17 iv. Salvatore Salam one, 1998, Trends, Remote Access: Goodbye Modem Pools, Hello Service Providers, web.