afrorhythmatic

[afrorhythmatic]

PC network setting

[afrorhythmatic]

How To Inform If Somebody Is Lurking On Your Wireless House Network

Power down your DSL or cable modem by unplugging them. This is usually altered to 255.255.. this kind of that the nearby subnet includes the deal with. Choose the LAN link, or the 1 that is difficult wired to your network. So you need to check your IP address, for whatever reason. Maybe you're playing an online game with a friend, or you need to access your PC remotely. Whatever the reason, there are a number of different ways you can check your IP address.

In case you select shared IP addresses you can profit by reselling some extra space on your server. But generally after some time you will realize that you need to get your own address. The shared ones have a bunch of downtime problems due to the fact that the server is shared with others. These also do not have backup in case of a computer crash. So, it is a risk you have to take if you want to use the shared addresses. If that is not the case, you can browse on the Internet to find suitable deals for getting a specific address for yourself.

If you are performing this type of installation for more than a handful of people, it is best to install this once on a Windows Server and share that printer to everyone. Normally it takes between 5 and 10 minutes to perform this type of install on each pc.

Using MAC filtering we can influence this behavior to our advantage. We can create what is called a MAC filtering table on our wireless router and specify only the MAC addresses that we want on our network. This is done by using the "ipconfig /all" command mentioned earlier to find the MAC of each of our preferred network devices and adding them to the MAC filtering table on our router. Adding addresses is done by accessing the routers web interface. Many routers have utilities which make this process a breeze.

Ensure any local firewalls are not blocking the Remote Desktop Port. The best way to test this functionality, if you can, is to use a PC on your LAN. From a PC on the same network as yours, type "telnet ", ie "telnet 192.168.0.1 23456". If you receive a blank cmd window, then this is working OK. If you receive an error, and all the above tests are successful, then this indicates that something on your PC is blocking this connection. You will need to look at any local firewalls that may be preventing this access (including the inbuilt Microsoft Firewall).

Theoretically, a repeater should be set-up in the middle of the rest of your wireless devices. In reality this may not be easy to do or exactly what you need. When you set up your repeater, make sure it is within the range of your original network. Once it's set up, make sure that the repeater new signal reaches where you wanted to use the wireless network previously but couldn't. You may need more than one repeater to cover your entire house.

An IP address also has what is called a subnet mask attached to the end of it. For example, one with a subnet mask look like this 192.168.1.1 255.255.255.0. The purpose of the subnet mask is to let you know which part of the IP address belongs to the network and which part belongs to the hosts. This can kind of be compared to area codes when calling somebody's telephone number.

In most SIP environments there will be several VoIP calls in use concurrently. Every one of these calls will be managed through the VoIP switch, each one requiring its own voice channel. Each channel (or phone call to look at it another way) must use a unique port. If there are 100 concurrent VoIP calls in use there must be 100 ports available for the VoIP switch to allocate to each call. This is where SIP comes in. It basically controls everything that is needed in setting up the call. For each call SIP will find a spare port, allocate it, send these details to all parties, set the call up and ring the phones. Once the call has finished SIP terminates the session and informs the phone switch that this port can be reassigned to another call.

Of course, it couldn't be that simple and the pending introduction of IPv6 (q.v. article 6 in this series) will change much of the traditional methodology described above. Don't worry about it 'till it happens!