IP Address

      

1. Short for Internet Protocol, IP is an address of a computer or other network device on a network using IP or TCP/IP. For example, the number "166.70.10.23" is an example of such an address. These addresses are similar to an addresses used on a house and is what allows data to reach the appropriate destination on a network and the Internet.
There are five classes of available IP ranges: Class A, Class B, Class C, Class D and Class E, while only A, B, and C are commonly used. Each class allows for a range of valid IP addresses. Below is a listing of these addresses.

Class	Address Range	Supports
Class A	1.0.0.1 to 126.255.255.254	Supports 16 million hosts on each of 127 networks.
Class B	128.1.0.1 to 191.255.255.254	Supports 65,000 hosts on each of 16,000 networks.
Class C	192.0.1.1 to 223.255.254.254	Supports 254 hosts on each of 2 million networks.
Class D	224.0.0.0 to 239.255.255.255	Reserved for multicast groups.
Class E	240.0.0.0 to 254.255.255.254	Reserved for future use, or Research and Development Purposes.

Ranges 127.x.x.x are reserved for the loopback or localhost, for example, 127.0.0.1 is the common loopback address. Range 255.255.255.255 broadcasts to all hosts on the local network.

IP address breakdown

Every IP address is broke down into four sets of octets that break down into binary to represent the actual IP address. The below table is an example of the IP 255.255.255.255. If you are new to binary, we highly recommend reading our binary and hexadecimal conversions section to get a better understanding of what we're doing in the below charts.

IP:	255	255	255	255
Binary value:	11111111	11111111	11111111	11111111
Octet value:	8	8	8	8

If we were to break down the IP "166.70.10.23", you would get the below value. In the below table, the first row is the IP address, the second row is the binary values, and the third row shows how the binary value equals the section of the IP address.

166	70	10	23
10100110	01000110	00001010	00010111
128+32+4+2=166	64+4+2=70	8+2=10	16+4+2+1=23

Automatically assigned addresses

There are several IP addresses that are automatically assigned when you setup a home network. These default addresses are what allow your computer and other network devices to communicate and broadcast information over your network. Below is the most commonly assigned network addresses in a home network.

192.168.1.0	0 is the automatically assigned network address.
192.168.1.1	1 is the commonly used address used as the gateway.
192.168.1.2	2 is also a commonly used address used for a gateway.
192.168.1.3 - 254	Addresses beyond 3 are assigned to computers and devices on the network.
192.168.1.255	255 is automatically assigned on most networks as the broadcast address.

If you have ever connected to your home network, you should be familiar with the gateway address or 192.168.1.1, which is the address you use to connect to your home network router and change its settings.

Getting an IP address

By default the router you use will assign each of your computers their own IP address, often using NAT to forward the data coming from those computers to outside networks such as the Internet. If you need to register an IP address that can be seen on the Internet, you must register through InterNIC or use a web host that can assign you addresses.

Anyone who connects to the Internet is assigned an IP address by their Internet Service Provider (ISP) who has registered a range of IP addresses. For example, lets assume your ISP is given 100 addresses, 109.145.93.150-250. This means the ISP owns addresses 109.145.93.150 to 109.145.93.250 and is able to assign any address in that range to its customers. So, all these addresses belong to your ISP address until they are assigned to a customers computer. In the case of a dial-up connection, you are given a new IP address each time you dial into your ISP. With most broadband Internet service providers because you are always connected to the Internet your address rarely changes and will remain the same until the service provider requires it to be changed.

Read More

Windows Server 2008 R2 Update Issues and Role Errors

Windows Server 2008 R2 Update Issues and Role Errors

For sometime now we have been finding that some of our Windows Server 2008 R2 servers were not installing Windows Updates.

Some servers would not even find any updates, and others would simply get to the "Downloading..." screen and never progress any further. In addition we would also get an annoying problem in Server Manager; where the Roles and features are usually displayed, the window would be blank with a message that simply said "Error."

After alot of research from various sources on the Internet, we have found this to be caused by a combination of a corrupt Trusted Installer and corrupt or missing Windows Update Files.

Althrough time comsuming, we have found the following solution:

First of all navigate to C:\windows\servicing on the server with the problem. In here you will find the "Trusted Installer package files. It consists of four files:

TrustedInstaller.exe
CbsApi.dll
CbsMsg.dll
wrpintapi.dll

These need to be deleted and replaced from a known working server.

Before you can do this you will need to stop and disable the "Windows Modules Installer" service and the "Windows Update" service.

Copying these files over should replace the corrupt Trusted Installer.

Keep these services in this state until after the next step.

Open the properties of C:\windows\servicing\Packages and take ownership of it. Note: NT SERVICE\TrustedInstaller is the current owner and MUST be replaced afterwards.

Delete the contents of this folder.

Now replace with the contents of C:\windows\servicing\Packages from a known working, up to date Windows Server 2008 R2 box. I found I had to copy from several servers to ensure I had all of the packages.

Change the owner of C:\windows\servicing\Packages back to NT SERVICE\TrustedInstaller. Remember this is a local account on the Server, not the domain.

Re-enable the "Windows Modules Installer" service and the "Windows Update" service and reboot the server.

You will know if the fix has been successful as Server Manager will load correctly displaying the Server Roles.

Now run Windows updates.

If the problom persists it is possible you are still missing a Windows Update file in the C:\windows\servicing\Packages folder.

You can either go through the process again with packages from another server or run: Windows6.1-KB947821-v10-x64 from Microsoft.

This will install the System Update Readiness Tool and run a check on your packages. A log file "c:\windows\logs\CBS\CheckSUR.log" will be created to tell you which packages are missing. Then you can simply copy them from another server or download the update from Microsoft and extract the files you need using the "KBArticleNumber /X:C:\ExtractedPackage" command.

As I said before this can be time consuming, the server may require several reboots and you need to keep running Windows Updates until your server is patched and up to date.

Read More

Remote Server Administration Tools for Windows 7

Remote Server Administration Tools for Windows® 7 with SP1 enables IT administrators to manage roles and features that are installed on computers that are running Windows Server® 2008 R2, Windows Server® 2008, or Windows Server® 2003, from a remote computer that is running Windows 7 or Windows 7 with SP1.

Click Here...

Read More

Install Remote Desktop Web Connection on Windows XP

1. Open Add or Remove Programs in Control Panel.
2. Click Add/Remove Windows Components.
3. Select Internet Information Services, and then click Details.
4. In the Subcomponents of Internet Information Services list, select World Wide Web Service, and then click Details.
5. In the Subcomponents for World Wide Web Service list, click the Remote Desktop Web Connection check box, and then click OK.
6. In the Windows Components Wizard, click Next.
7. Open Internet Services Manager.
8. Expand the folder hierarchy until you reach the local computer name\Web Sites\Default Web Site\tsweb folder.
9. Right-click the tsweb folder and then click Properties.
10. Click the Directory Security tab on the Properties dialog box.
11. In Anonymous access and authentication control, click Edit.
12. Check the Anonymous access check box on the Authentication Methods dialog box, and then click OK twice.

..

1. Ensure that Remote Desktop Web Connection is installed and running on the Web server.
2. Ensure that your client computer has an active network connection and that the WINS server service (or other name resolution method) is functioning.
3. On your client computer, start Microsoft Internet Explorer.
4. In the Address box, type the Uniform Resource Locator (URL) for the home directory of the Web server hosting Remote Desktop Web Connection.
5. The URL is "http://" followed by the Windows Networking name of your server, followed by the path of the directory containing the Remote Desktop Web Connection files (default = /Tsweb/). (Note the forward slash marks.) For example, if your Web server is registered with the WINS server as "Admin1", in the Address box you type: http://admin1/tsweb/, and then press ENTER. The Remote Desktop Web Connection page appears on the screen.

 

 

 

 

 

1. In Server, type the name of the remote computer to which you want to connect. 
2. Optionally, specify the screen size and logon information for your connection.
3. Click Connect.

1. After you supply your username and password the Windows XP desktop appears and you can begin to work.

Read More

DHCP installation and configuration in windows server 2008

Read More