Networking Computers - Tip for Windows Networking, Wireless Networking

IP is for communication between computers.




IP is a "connection-less" communication protocol.



IP does not occupy the communication line between two computers. IP reduces the need for network lines. Each line can be used for communication between many different computers at the same time.



With IP, messages (or other data) are broken up into small independent "packets" and sent between computers via the Internet.



IP is responsible for "routing" each packet to the correct destination.

TCP/IP is TCP and IP working together.



TCP takes care of the communication between your application software (i.e. your browser) and your network software.



IP takes care of the communication with other computers.



TCP is responsible for breaking data down into IP packets before they are sent, and for assembling the packets when they arrive.



IP is responsible for sending the packets to the correct destination.

When an IP packet is sent from a computer, it arrives at an IP router.



The IP router is responsible for "routing" the packet to the correct destination, directly or via another router.



The path the packet will follow might be different from other packets of the same communication. The router is responsible for the right addressing, depending on traffic volume, errors in the network, or other parameters.

TCP is for communication between applications.



If one application wants to communicate with another via TCP, it sends a communication request. This request must be sent to an exact address. After a "handshake" between the two applications, TCP will set up a "full-duplex" communication between the two applications.



The "full-duplex" communication will occupy the communication line between the two computers until it is closed by one of the two applications.



UDP is very similar to TCP, but simpler and less reliable.

nside the TCP/IP standard there are several protocols for handling data communication:



* TCP (Transmission Control Protocol) communication between applications

* UDP (User Datagram Protocol) simple communication between applications

* IP (Internet Protocol) communication between computers

* ICMP (Internet Control Message Protocol) for errors and statistics

* DHCP (Dynamic Host Configuration Protocol) for dynamic addressing

It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.
You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:
You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389. After this, you have to change the port number in Hex and save the new value.
If you want to change the port for a particular connection on the Terminal Server, then follow these steps:
You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection. After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389. Then you have to change the port number in Hex and save this new value.
After performing this, you have to make alteration in the Port on the Client Side. Follow these steps to perform this:
You have to open Client Connection Manager. Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there. Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export. Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server. Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one. If it has the same name, then overwrite it. In this way, you will receive a client that has the correct port settings to match your Terminal Server settings.

It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.

You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:

You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389. After this, you have to change the port number in Hex and save the new value.

If you want to change the port for a particular connection on the Terminal Server, then follow these steps:

You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection. After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389. Then you have to change the port number in Hex and save this new value.

After performing this, you have to make alteration in the Port on the Client Side. Follow these steps to perform this:

You have to open Client Connection Manager. Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there. Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export. Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server. Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one. If it has the same name, then overwrite it. In this way, you will receive a client that has the correct port settings to match your Terminal Server settings.

Microsoft Small Business Server 2000 helps the small and medium size organizations, by providing them many services in the affordable price. Small Business Server 2000 SP1a is the next version of it and having many improvements over it. For the installation of Small Business Server 2000 SP1a, you have to check whether enough free space is available or not. If enough space is not available, then you are not able to install the Small Business Server 2000 SP1a. For installing it, perform these steps:

You can download the Small Business Server 2000 SP1a package from the Microsoft Web site, but for performing this you should be the user of Small Business Server 2000. If you are not a user of the Small Business Server 2000, then you have to purchase its full product. After downloading this package save it on your computer. Now, you have to stop any services like antivirus that are running on the server. Then you have to double-click on the SBSSP1a.exe file. After this you have to unzip its files in the folder indicated in the dialog box. After all of the files are unzipped, then locate the folder in which you have saved its unzipped files. Then you have to double-click on the SP1Setup.exe in the folder.

Now, if you are prompted to install the Windows 2000 Service Pack 4, then click on OK. Then the Windows 2000 Service Pack 4 Setup Wizard starts. If you are not prompted, then it means that this wizard has already started. Then click on Next. After this, follow the instructions to complete the Setup Wizard. When you are prompted to restart the computer, perform it. After your computer has been restarted, log on as administrator. After following the above mentioned steps, Small Business Server 2000 SP1a will gets installed.