Tutorial On Networking Hardware Data Transfer

Views 7 Likes Comments Comment
Like if this guide is helpful
In the past year we have experienced on a number of occassions confusion by ebay members over networking hardware specifications in relation to data tranfer. We have had to endure returns and costs as a result of this subject area. There are various terminology in the industry that does not alway's make sense. For example the classification of a 10/100 network cannot be interpreted and taken as red that the data transfer rate is 100 mbs. The classification is an old traditional specification. A 10/100 is a transfer rate up to 100 milli bars per second. A higher transfer specification is 100/1000 which measures up to 1000 milli bars per second. However most small networks and home users do not necessarily need speeds higher than 10/100. The problem lay's in a number of areas as to why sometimes a transfer rate seems delayed or a connection does not appear to be made. The problem could be the use of inferior Network PCI cards for example that has a lower specification to the hub or switch. Another known problem and factor is the operating system. It is commonly known in the industry that the XP range does not deliver a stable or hardened networking environment. Microsoft staff and teams have confirmed and acknowledged this to ourselves. The last and most stable connectivity operating system of Windows for networking was the Windows 2000 series, however this operating system had network authoring and codecs written by Sun Micro systems. The XP series does not as it was sadly the case again that Microsoft had to be dragged into Court over non payment of technical authoring, hence the reason why today Windows 2000 is not supported or continued. Please give due consideration when building a network that there is every chance the hub or switch is fine. It is also adviseable to set up dedicated IP Network addresses on your LAN as this will assist an operating system for a better and more decisive connection. Firewalls on a network can also be a common cause for connectivity and XP offers a basic package that does in very many cases cause connection failure. Please remember also a network can suffer as a result of a number of other issues in the way of driver incompatibility, file formats, hard drive formats, configuaration port conflicts with WAN and LAN, missing installation required applications from the operating system for networking. Another area of confusion is variation in operating systems. Please note that Linux can successfully share a network with Windows. it is also worth mentioning that networking connectivity can also be as a result of conflicts if you are using Internet sharing and your ISP's server firewall is causing a configuration issue. On the latter as it does have some relevance, if you are using XP on a network and endeavouring to internet share. It would be wise to use a purpose made server application known as a Proxy Server that can be configured very easily for this task and you do not have to rely upon XP services. Internet sharing will also mean the configuration of your Browser. Fire Fox and Netscape have a preference tab that will allow you access to the configuration for internet sharing. Once you have established your primary workstation or server that hosts the ISP WAN connection the other Browsers on other PC's will have to resolve to that address. In the LAN connection IP address you type in your host PC or Servers address and in the section known as port type in 8080. If connections are poor or time out there is every chance again it is a firewall issue. Good Luck! Riverside Networks Web Community Service
Have something to share? Create your own guide... Write a guide
Explore more guides