






All devices connecting to a wireless router must possess a working network adapter. As illustrated in the diagram, connecting to the router a broadband modem (that has one or more built-in adapters) enables sharing of a high-speed Internet connection.
Wireless routers technically allow dozens of computers to connect over WiFi links. Nearly any residential wireless router will have no trouble supporting the number of wireless devices found in typical homes. However, if all WiFi computers attempt to use the network at the same time, slowdowns in performance should be expected.
Many (but not all) wireless network routers also allow up to four wired devices to be connected via Ethernet cable. When first installing this kind of home network, one computer should be cabled to the wireless router temporarily to allow initial configuration of the wireless features. Employing Ethernet connections after that is optional. Using permanent Ethernet connections make sense when the computer, printer or other device lacks WiFi capability or cannot receive an adequate wireless radio signal from the router.
Optional Components - Networking the router for Internet access, printers, game consoles and other entertainment devices is not required for the rest of the home network to function. Simply omit any of these components shown that do not exist in your layout.
Limitations - The WiFi portion of the network will function only to the limit of the wireless router's range. The range of WiFi equipment varies depending on many factors including layout of the home and any radio interference that may be present.
If the wireless router does not support enough Ethernet connections for you needs, add a secondary device like a network switch to expand the wired portion of the layout.
All devices connecting to an Ethernet router must possess a working Ethernet network adapter.
Optional Components - Networking the router for Internet access, printers, game consoles and other entertainment devices is not required for the rest of the home network to function. Simply omit any of these components shown that do not exist in your layout.
Limitations - If the Ethernet router does not support enough Ethernet connections, add a secondary device like a network switch to expand the layout.
Nearly any home network wireless access point will have no issue managing to support the number of wireless devices there. However, if all WiFi computers attempt to use the network at the same time, performance slowdowns can result.
All devices connecting to an Ethernet router must possess a working Ethernet network adapter. All devices connecting a wireless access point must possess a working WiFi network adapter.
Optional Components - Networking of Internet access, printers, game consoles and other entertainment devices is not required for either the router or access point to function. Simply omit any of these components shown that do not exist in your layout.
You can choose which devices to connect to the router and which to the wireless access point. Additional network adapters may be needed to convert some Ethernet devices, particularly printers and game consoles, to work wirelessly.
Limitations - The WiFi portion of the network will function only to the limit of the wireless access point's range. The range of WiFi equipment varies depending on many factors including layout of the home and any radio interference that may be present.
If the wireless router does not support enough Ethernet connections, add a secondary device like a network switch to expand the wired portion of the layout.
Direct Connection is common for game consoles to support two-player network gaming (e.g., Xbox System Link).
Optional Components - Connecting to the Internet requires that one computer possess two network adapters - one to support the Internet connection and one to support the second computer. Additionally, Internet connection sharing software must be installed to allow the second computer Internet access. If Internet connectivity is not necessary, these things can be omitted from this layout.
Limitations - Direct connection works only for a single pair of computers / devices. Additional devices cannot join such a network, although other pairs can be connected separately as shown above.
5. Ad Hoc Wireless Network Diagram
Optional Components - Networking an ad hoc layout for Internet access, printers, or game consoles and other entertainment devices is not required for the rest of the home network to function. Simply omit any of these components shown that do not exist in your layout.
Limitations - All devices connecting via ad hoc wireless must possess a working Wi-Fi network adapter. These adapters must be configured for "ad hoc" mode instead of the more typical "infrastructure" mode.
Because of their more flexible design, ad hoc Wi-Fi networks are also more difficult to keep secure than those using central wireless routers / access points.
Ad hoc Wi-Fi networks support a maximum of 11 Mbps bandwidth, while other Wi-Fi networks may support 54 Mbps or higher.
6. Ethernet Hub/Switch Network Diagram
Optional Components - Networking of Internet access, printers, or game consoles and other entertainment devices is not required for the rest of this home network layout to function. Simply omit any of these components shown that do not exist in your design.
Additional hubs and switches can be incorporated to the basic layout shown. Connecting hubs and/or switches to each other expands the total number of computers the network can support up to several dozen.
Limitations - All computers connecting to a hub or switch must possess a working Ethernet network adapter.
As shown, unlike a network router, Ethernet hubs and switches cannot interface directly to an Internet connection. Instead, one computer must be designated as controlling the Internet connection and all other computers access the Internet through it. Internet connection sharing software can be installed on each computer for this purpose.
When connecting multiple computers with phoneline networking, one central computer "gateway" must be established. The gateway represents the network's primary device for connecting to the Internet. A few models of home network routers (sometimes called "residential gateways") support phoneline networking today. Otherwise, you must designate one computer as the gateway and install two network adapters on this computer to enable it for gateway functions. Depending on the type of primary device chosen, hybrid networks with a combination of phoneline, Ethernet or Wi-Fi devices can be created.
The Home Phoneline Networking Alliance (HomePNA) develops technology standards that compatible phoneline equipment must support.
Optional Components - As mentioned above, a network router is optional when building a phoneline home network. Phoneline networking also works regardless of whether the residence is subscribed either to basic local telephone service or to DSL Internet service.
Limitations - HomePNA phoneline networking has proven much less popular than Wi-Fi or Ethernet alternatives. Phoneline networking products will generally be more difficult to find, and there will be fewer choices of models for this reason.
All phoneline network equipment must be connected to the same electrical circuit within the residence. Specifically, residences that have two phone lines installed, must choose one or the other line to connect all devices.
The range of an HomePNA (version 2.0) phoneline network is about 1000 feet (300 m). The maximum bandwidth of an HomePNA 2.0 network is 10 Mbps, while an HomePNA 3.0 network supports more than 100 Mbps. The speed of phoneline networking can suffer depending on the quality of phone cables installed in the residence.
8. Powerline Home Network Diagram
To connect to a powerline network, one end of the adapter plugs into a standard electric wall outlet while the other connects to a device's network port (usually Ethernet or USB). All connected devices share the same communication circuit.
The HomePlug Powerline Alliance develops technology standards supported by compatible powerline equipment.
Optional Components - Not all devices on the home network must be connected to a powerline router; hybrid networks with Ethernet or Wi-Fi devices can be joined with the powerline network. For example, a Wi-Fi powerline bridge can optionally be plugged into a wall outlet, enabling wireless devices to connect to it and in turn to the rest of the powerline network.
Limitations - HomePlug phoneline networking remains much less popular than Wi-Fi or Ethernet alternatives. Powerline networking products will generally be more difficult to find with fewer choices of models for this reason.
Powerline networks generally do not work as reliably if devices plug into power strips or extensions cords. Connect directly to the wall outlets for best results. In homes with multiple circuits installed, all devices must connect to the same one circuit to communicate with each other.
The maximum bandwidth of a HomePlug (version 1.0) powerline network is 14 Mbps, while the newer HomePlug AV standard supports more than 100 Mbps. Poor quality electrical wiring as found in older homes can degrade the performance of a powerline network.
To create a VPN, you will need three separate Windows 2003 servers and at least one remote client. The remote client's machine needs to be running Windows XP.
The first Windows 2003 server your VPN will need is basically an infrastructure server. It must act as a domain controller, DHCP server, DNS server and certificate authority. If you already have a Windows 2003 network in place, you don't need to go out and buy a server to fit this role.
Any Windows 2003 domain will already have at least one domain controller and one server acting as a DNS server. Most Windows 2003 networks are also running DHCP services. If you already have all these services in place, the only thing you will have to worry about is setting up a certificate authority (which I show you how to do in Step 3). For now, you just need to know that the server acting as a certificate authority must be running Windows Server 2003 Enterprise Edition.
The second server you will need is a VPN server. Windows Server 2003 Standard Edition and Enterprise Edition both ship with the necessary software. Therefore, you won't need any special software on this server. The only specific hardware this server needs is two NICs. One NIC will connect to the Internet and the other will connect to your private corporate network.
The final server you will need is an authentication server. When remote users attempt to access your corporate network through a VPN, they need to be authenticated. The mechanism of choice for authenticating remote users is a RADIUS server. RADIUS is an acronym standing for Remote Authentication Dial In User Service. Microsoft includes its own version of RADIUS in Windows Server 2003 Standard Edition and Enterprise Edition. The Microsoft version of RADIUS is called Internet Authentication Service (IAS). There are no special hardware or software requirements for this server.
The last thing that I want to talk about as part of this step in the tutorial is server placement. Each of the servers I have discussed will be connected to your private network via a hub or switch. The only server that will have any external connectivity is your VPN server. It is a security risk to connect the VPN server directly to the Internet though. It is best to place a firewall in front of the VPN server so you can filter out everything but VPN traffic.
In Step 2, we'll begin the domain configuration process. Your network should contain the required Windows Server 2003 domain controller and DNS server before moving on to the next step.
Windows will now install the DHCP services. When the installation completes, you will have to create an address scope and authorize the DHCP server to function on your network.
Therefore, protect your certificate authority server the way you would protect a nuclear bomb. Make sure that it is as secure as possible and that you perform full system backups frequently. You also want to protect those backups so they are not accidentally compromised.
You will now be prompted to enter a common name for the certificate authority. You must also select a certificate validity period. The default setting allows certificates to be valid for five years, but you can increase or decrease this time frame according to your own corporate security policy.
Your VPN server is now configured. You're in the home stretch! All you need to do now is configure your clients to work with the VPN you have created.
To allow a Windows XP client computer to access your private network, you must tell it to use a VPN connection.
You should see the content's of your server's C drive (assuming that you have the rights). Of course, it's rare that you would be directly accessing the server's C drive. More often, you would be accessing a specific share on the server. To do so, you would enter \\servername\sharename.
Instructions are for both Mac and PC Cisco VPN Clients so you can use your NetID.
Step 1: Launch the Cisco VPN Client. |
Step 2: At the main screen, make sure the UR-VPN connection entry is highlighted and then click the Modify icon. |
Step 3: At the lower left hand corner of the window you will see the button Erase User Password. Click on the button to remove your saved credentials. Then click the Save button. This will return you to the main connection window. Do NOT change the username or password in the boxes for Group Authentication. |
Step 4: The next time you connect to VPN it will get an Authentication pop-up box: Type in your NetID and password. You can check the Save Password box to have it remember your login credentials. |
This program will work on following Windows Operating Systems:
• Windows 2000s
• Windows XP Professional
Step 1: Download the Cisco VPN client for windows onto your desktop. After the download is complete double click the icon to start the installation. | ||||||||
Step 2: The first screen you come to will be the welcome screen, click "Next". | ||||||||
Step 3: At the License agreement screen just click "Yes". | ||||||||
Step 4: At this screen use the default provided and click "Next". | ||||||||
Step 5: At this screen, again use the default and click "Next". | ||||||||
Step 6: The install will now start. The install process will take a several minutes. During the installation, on a Windows 2000 or Windows XP machine you may get a pop-up window asking if you want to continue the install process. Windows 2000 users click “Yes” Windows XP users click “Continue Anyway” When the installation has finished you will come to this screen, click the "Finish" to reboot your computer.
| ||||||||
Step 7: After your computer has rebooted you should now see an Icon on your desktop that looks like this: Double click the Icon to launch the VPN client. | ||||||||
Step 8: When the application opens up you should get this screen: | ||||||||
Step 9: Click the "Connect" button and you will get this pop-up window: Enter your NetID "Username" and "Password". Click "OK" | ||||||||
Step 10: If you have successfully connected to the U of R Network you will get screen: Just click "Continue" and you are now connected. If you look in the lower right-hand corner of you screen, next to the clock, you will see a yellow padlock like this: This padlock is your VPN connection, when it is in the locked position you are connected to the U of R Network and when the padlock is in the unlocked position you are not connected. If you need to disconnect your VPN connection just double-click the padlock and click the "Disconnect" icon.
** If you are using a Firewall and/or Router in your setup, please checkout out our webpage for help on how to configure your device to allow a VPN connection. VPN when using Firewalls and Routers.If you are using a firewall and/or router you may not be able to connnect to VPN using the default setup of your device. You may need to configure your firewall and/or router to allow traffic to and from the VPN server. Due to the number of different firewall and router products, we cannot offer help on configurations to get VPN access working. We can offer some information on what you may need to input in order to get VPN access through your firewall and/or router.
Using this information or a combination of it along with the documentation for your firewall or router, should make it possible to connect to VPN while still using your device without any loss of security. Here are some popular vendors of Firewalls and Routers. Firewall (software) ZoneAlarm by Zonelabs - www.zonelabs.com Norton Personal Firewall by Symantec - www.symantec.com McAfee Personal Firewall by McAfee - www.mcafee.com
Routers Linksys - www.linksys.com D-Link - www.dlink.com Netgear - www.netgear.com Belkin - www.belkin.com (Article is grabbed from http://www.rochester.edu) |
1. Create a New Connection by selecting "Start ->Settings -> Network Connections".
2. Click Next to advance to the next step.
3. Selcet "Connect to the network at my workplace", then click Next.
4. Selcet "Virtual Private Network connection", then click Next.
5. Type a name to distinguish this VPN connection, then click Next.
6. Type the IP address or host name of VPN server.
9. Now you can see the authentication process status.
10. VPN connection is established.
With Remote Desktop, you can connect to your Windows XP machine from anywhere on your Local Area Network (LAN). You can even set it up so that you can connect to the machine over the Internet from anywhere in the world.
Prior to Windows XP, if you wanted this kind functionality, you had to do some special configuring using Windows Terminal Services.
In this blog, I will show you how to configure the Remote Desktop Web Connection and use Internet Explorer as a remote client to connect to your XP machine.
To connect to your machine from a remote location, you must install the Remote Desktop Web Connection on the Windows XP system you want to access remotely. This feature is basically a component of XP’s Internet Information Services (IIS).To install the necessary files for the Remote Desktop Web Connection, you will need to have access to your Windows XP CD. To Install IIS and the Remote Desktop Web Connection, follow these steps:
By default, the Remote Web Connection files are installed to the \\%systemroot%\Web\Tsweb directory of your Web server. Let’s verify that the files were installed correctly and make sure that anonymous access is selected:
Once you’ve properly configured the Remote Desktop Web Connection, it’s time to configure this computer to use Remote Desktop:
Note:
All Administrators have access regardless of whether they are added to the list.
You’re now ready to connect to your computer from another Windows machine running Internet Explorer 4.0 or greater.
Note: Remember that to connect to your XP system by computer name from a remote location, you must be connected to your network via dial-up or VPN. If your Windows XP machine has a static IP address, you can connect to it over the Internet using the static IP as well. If you don’t have a static IP address, you can connect with port forwarding from the router or firewall in front of the XP machine, although connecting via dial-up or VPN is much easier and more secure.
If you are connecting to the Windows XP system from another XP system, you can simply go to Start | Programs | Accessories | Communications | Remote Desktop Connection and enter the
name or IP address of the machine you want to connect to, as shown in Figure H.
If you want to use the above method from a computer running Windows 95, 98, NT 4.0, or 2000, insert the Windows XP CD and wait until it loads. From the startup screen, click Perform
Additional Tasks and then click Set Up Remote Desktop Connection. Once installation is complete, you can access the Remote Desktop Connection client from Start | Programs | Accessories | Communications | Remote Desktop Connection. You can also download from the Internet.
You can now use either Internet Explorer or Windows XP’s Remote Desktop Connection client to connect to any remote system that is configured asa Remote Desktop host. With this functionality, you can connect to your computer from various locations to access your applications, files, contacts, etc. This feature provides solid functionality and good performance. It’s definitely worth taking a look at Windows XP if you think this feature can benefit employees who often need remote access to their systems from different locations.
Did you know that each time you open My Computer on Windows XP, your computer automatically searches for the network files and printers your specific login has access to? This entire process can decrease system performance to a crawl as well as take much longer to display all of your icons in the My Computer window. You have the ability to stop Windows from automatically searching for network resources and printers by performing the following:
The SendTo feature in Windows XP is a hidden gem that I want to share with you. I don't think a day goes by that I do not take advantage of this feature.
Click Start Run and type sendto in the textbox.
The sendto folder opens up and allows you to enter shortcuts to folders that you find desirable. For example, you could enter a shortcut to your music, pictures, a network share, etc.
Once you have created your shortcuts, simply right-click on the documents of your choice and use the sendto feature to get them to the appropriate place.
I recently came across a tip while working within Windows Vista. Typically when I use the command prompt, I type cmd in the Run window and then browse to my appropriate directory.
In Windows Vista, you can avoid this extra time by browsing to the appropriate directory in Windows Explorer and then simply hold down the SHIFT key and right-click on the folder and choose Open Command Window Here.