The world of Internet users is growing daily. Millions of people are more interested in this type of technology. People like the wireless networks at home, but that isn’t the only place that the security of wireless system broadband networks come into question. The workforce is using these systems. Mobile employees that are on the road a lot will use this type of technology. There are also consumers and all types of environments where wireless networks are used:
The network shell (Netsh) command line utility allows local or remote configuration of network devices such as wireless interfaces. Using the Netsh wlan option you can create filters that block users from connecting to specific wireless networks which may pose a risk to the security of your environment. Users connecting to unsecure open wireless networks increase the risks of their computers being compromised.
The default IP address of Windows 7 (and Windows Server 2008 R2) virtual Wi-Fi Access Point (AP) feature called Wireless Hosted Network is 192.168.137.1. Although, this address is highly unlikely to conflict with other addresses that you may have configured on your network still, you may wish to change it to another value. In order to be able to change this default IP address you need to modify a Registry setting as follows:
If an organization has stringent security policies in place that control network traffic and LAN connections, and does not control the users’ ability to bridge the organizational internal network to an insecure wireless network then the organization may fail its objectives to secure its internal assets appropriately. Laptop users connected to the wired LAN can also connect to a neighbouring insecure wireless network and create a bridge between the networks’ segments which allow the laptop users to expose internal resources to external third-parties.
Imagine you need to share some files with a friend or with a colleague while in a meeting and do not have any network means to connect to! You can set up a temporary wireless network between two or more computers running Windows 7 or Vista assuming that both computers are equipped with a wireless interface and are within 9 meters of each other. An ad hoc wireless network is quickly set up as you can see from the following steps:
Connecting a wireless-enabled computer running Windows 7 to a wireless network is pretty straight forward however; if that doesn’t work you can try the netsh command line tool. Below, you will find the steps required to connect your computer to a wireless network using the netsh wlan command. Alternatively to netsh, you can either open Network and Sharing Center and click Connect to a network or click the network icon on your taskbar at the bottom right section of your screen.
In general, troubleshooting network connectivity issues require the same techniques but with Wireless Networks there is an additional layer that you need to consider. You need to be aware of the wireless layer and the implications it has over your connection. In this article I will point out the most common wireless problems and how to resolve them.
The task of setting up wireless networks is either flawless or drives us crazy. We may be reluctant to modify a working configuration or so much time may have been dedicated in troubleshooting and configuring a practical solution that we tend to ignore the security part of the wireless setup! You must build your wireless setup around the security controls and features provided by WAP devices and not implementing security as an afterthought. There are quite a number of security measures we can take and they depend mostly on your WAP devices but the following features which must be available on most WAPs will help you increase your wireless setup security:
As wireless technologies become more ubiquitous, keeping yourself up-to-date with standards and technologies may help you select the right Wireless solution for your needs. Here is a list of the most common wireless technologies used in offices and homes: