This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.
Multi-vendor network management provides a single point of control while managing both legacy and new wireless networks from Aruba and its competitors. Unlike single vendor strategies that require the enterprise to conform to a sole equipment provider's point of view, a multi-vendor network strategy empowers enterprises with the freedom to choose.
The network strategy should be built upon an open standards based solution that fits with the business' vision, a path for network progress, and best of breed innovations that carry a competitive edge. Operating systems from different vendors use special methods to access files across a network. Windows OSs uses the Common Internet File System (CIFS), which is currently a newer version of the SMB protocol. Native to Linux and UNIX is the Network File System (NFS). The native Macintosh protocol for accessing network files, which is part of the AppleTalk protocol suite, is AppleTalk Filing Protocol (AFP), and Novell NetWare uses NetWare Core Protocol (NCP).
There are two basic way to communicate different OSs. One is Client End and another One is Server End.
In a multi-vendor environment, multiple redirectors can be loaded on to a single client to make easy connections to different vendors' servers. This setup is called a client-based multi-vendor solution. Each redirector redirects a request to the right server. When multiple client redirectors are installed on a single OS, adjusting the bindings of those redirectors might be required to make sure that the network protocols used with every redirector are suitable and set in precedence order. In a network with both Windows and Linux servers and clients, a similar solution is essential. The native Linux file-sharing protocol is called NFS.
Figure: Windows XP with clients for Netware and Microsoft installed
For a Windows client OS to access NFS property on a Linux server, NFS client software must be installed on the Windows OS. Windows installation CDs don't come with the essential software, but it can be downloaded free from the Microsoft Web site in a package called Windows Services for UNIX. Also, for a Linux client computer to right to use Windows server property, Windows compatible client software must be installed and configured on the Linux computer. The client software that allows Linux computers to entrance Windows file and printer shares is called Samba.
Server-based multi-vendor solution, software should be loaded on the server to supply services for a exacting client. For example, if a Windows Server 2003 network includes Macintosh computers, the administrator can include Services for Macintosh to any of the Windows server OS. Windows Server 2003 NOSs contain this service, which equipment a simple solution for Macintosh connectivity. With Services for Macintosh installed on a Windows server, Macintosh clients can attach to resources on the Windows server. This service also converts files to Macintosh set-up mechanically when retrieving them from the server. This is usual change enables Macintosh users to share files with any other user connected to the Windows server where Services for Macintosh is installed. Another advantage of using Services for Macintosh is that Macintosh users can right to use resources on a Windows server in the same way they entrance property on a Macintosh server. This feature, which allows easy change from a Macintosh-only network, is also available in other Windows server services, such as Gateway (and Client) Services for NetWare. Windows servers can be prepared with Windows Services for UNIX, which can provide NFS server functionality on a Windows computer, and Samba can be configured to allow Windows-compatible file and printer sharing.
Different vendor and Solutions
Most popular PC operating system produces vendors: Microsoft, Linux, Novell, and Apple. In an attempt to simplicity connectivity between different NOSs, these companies include utilities in their OSs to allow simple connectivity between clients and servers from different vendors.
All Windows OSs, starting with Windows for Workgroups, include the Microsoft redirector, Client for Microsoft Networks. The Microsoft redirector is designed right to use CIFS or SMB-based file systems across a network. Installing the OS installs the Microsoft redirector automatically. The installation process loads all required drivers and edits the startup files so that when the computer restarts, the redirector is in place, ready for instant use.
Microsoft networks is enable server side, file and print sharing, used for sharing files and printers via CIFS or the older SMB, is installed on Windows OSs automatically.
Windows Vista or Windows XP Professional client to a Novell NetWare network running the IPX/SPX protocol, NWLink and the Microsoft version of the NetWare supplicant, Client Service for NetWare (CSNW),must be loaded on that Windows machine. Recall that NWLink is the Microsoft completion of the IPX/SPX protocol suite. When connecting a Windows Server 2003 system to a NetWare network, NWLink as well as Gateway Service for NetWare (GSNW) must be loaded on the Windows server. GSNW allows Windows clients running Client for Microsoft Networks to right to use NetWare property by using the Windows server as an agent. The Windows server running GSNW establishes a connection with a NetWare server.
These services include an execution of Network File System (NFS), which is a circulated file system native to UNIX and Linux systems. NFS permits networked machines to export portions of their local file systems and make them available to qualified users elsewhere on the network. The directory into which the NFS volume is mounted is referred to as the mount point. Linux- or UNIX-based file systems and services make sense for three reasons:
Because Samba is a server-based explanation, software and services need to be installed only on a rather small number of servers rather than a large number of clients.
Because Samba is an open basis software product, you can download it free from the Internet and install and use it without charge.
Because Samba allows a Linux or UNIX machine to pretense as a native Microsoft network server; Windows clients need no additional software to right to use its services. Samba-based resources show in a Windows browse list along with other network nodes and their file and print shares.
Macintosh is the OS files and the hardware essential to correspond in an AppleTalk network. The AppleShare networking software mechanically provides file sharing and includes a print server that allows computers to share printers.
Foundry has built a position for innovating highâ€performance networking solutions that address the needs and supplies of today and tomorrow's network infrastructures. At the core of this position is our assurance to open standards solutions. Foundry Networks provides a inclusive end to end IP communications, which not only provides a establishment for existing applications, but embraces new applications without costly upgrades or substitute. With Foundry products as your network basis, you can be sure that inheritance applications will be supported, and that you will be able to take benefit of new applications and next generation technologies that are operations critical to our business.
A Collage scenario for multi-vendor environment
Applying Multi-vendor solution to a company can contain drawbacks with the current hardware pattern.
Vendors are extensively accepted upon option thus it may be not easy for a wide reality of users to accept the change some might find it fascinating others might find it a bit of awkward.
Although today's surroundings features a singular hardware arrangement for all platforms but hardware intended for an exclusive platform can have trouble implementing to the current surroundings.
As of a collage most students would want to use the same types of file or surroundings in precise to swap information which can be a concern in multi-vendor surroundings
Some vendors relay on precise hardware condition and thus it may not be cost effectual for the collage
DIFFERENCE BETWEEN TWO DISKLESS WORKSTATION LINUX & WINDOWS XP
A workstation that does not have a hard disk.
All Programs and data are retrieved from the network. A personal computer or workstation which has neither a hard disk nor floppy disk drive and which performs all files entrance via a local area network connection to a file server. Diskless workstations are perfect when many users are operation the same application. They are small, quiet, more reliable than products with disks, and help put off both the theft of data and the beginning of viruses since the software and data accessible on them is controlled by the network manager or system manager.
DISKLESS WORKSTATION CHARACTERISTICS:
In a server-based computing system protocol such as RDP, ICP or other protocol are used.
Wireless LANs supported Ethernet connection.
Other peripherals, I/O for Keyboard and mouse and optional I/O for Printers are use.
A video processor for strong graphics and colors - a major improve from the dumb terminal.
Solid-state structure - no moving parts such as fans or disk drives results in longer life and higher consistency.
Central software administration and operation - means easier IT administration and greater security.
Firmware-based software and no disk drive making thin clients less susceptible to viruses or malware.
A thin client computing situation based on a Linux operating system is recognized as a Linux thin client. A Linux thin client situation offers the profit of often being free to use and also being open resource for the operating system to be customized. This is valuable to organizations with custom hardware considerations and expert programmers accessible to offer individual solution. There are various flavors of Linux thin client environments, including thin station. One recent benefit to organization a Linux thin client situation is the opportunity of running another operating system, such as Windows, inside of a light Linux setting up. This can be done using the free Virtual Box software.
Microsoft offers Terminal Services, a thin client server-side explanation for Windows computing environments. Terminal Services is easy to get to on Microsoft Windows Server operating systems. Using the service on a network enables a variety of client computers to entrance and use shared software applications, such as Microsoft Office and run them nearby on a client computer. Windows TS is based on Win Frame, a creation from Citrix, which was a repackaging of Windows NT. Microsoft approved the technology and made it part of possible versions of the NT operating system. This is also the source for the Remote Desktop Protocol used in Windows operating systems today, which allows for graphical thin client entrance to Windows computers.
Total cost of ownership for each of the workstation in a practical scenario
Model: hp_t5735 (Linux-based thin client)
Product Name: hp_t5735 (Linux-based thin client)
Processor: AMD Sempron 2100 + clocked at 1GHz
512MB DDR2 RAM, 1GB flash Memory
ATI Radeon x1250, supporting dual monitors and resolution up to 2048 x 1536 Display
Networking -- 10/100 Gigabit Ethernet, optional modem
8 USB ports (2 front, 4 rear, and two in secure compartment)
PS/2 mouse connector
microphone input and headphone/speaker output
PCI or PCIe expansion slot (on optional module)
2 x serial (one on optional module)
1 x parallel (on optional module)
Dimensions -- 1.8 x 8.5 x 10.5 inches (4.57 x 21.51 x 26.67 cm) with stand
Weight -- 3.5 pounds (1.6 kg) with stand
Power supply -- surge-tolerant 50 W power supply with worldwide auto-sensing 100-240 VAC, 50-60 Hz energy-saving automatic power-down.
Monitor : Hyundai Image Quest Q910
Keyboard : A4Tech X-Slim Keyboard
Mouse : Logitech SBF-96 Optical Wheel Mouse
Hyundai Image Quest Q910
Figure: HP t5630 (windows based thin client)
Product Name t5630 Thin Client
Graphics Memory Accessibility Shared
Graphics Controller Model Chrome9 HC3
Graphics Memory Capacity 64 MB
Standard Memory 1 GB
Flash Memory 1 GB
Green Compliance Yes
Ethernet Technology Gigabit Ethernet
Processor Manufacturer VIA
Processor Speed 1 GHz MHz
Processor Type Eden
Citrix ICA 10.x
Microsoft RDP 6.0
Windows Media Player 11
Microsoft Internet Explorer 7.0
Operating System Windows XP Embedded with SP2
Monitor: Axion 77814
Keyboard: A4Tech X-Slim Keyboard.
Mouse: Logitech SBF-96 Optical Wheel Mouse.
Brief Description of a thin client
A thin client (sometimes also called a lean or slim client) is a computer or a computer program which depends deeply on some other computer (its server) to complete its traditional computational roles. This stands in difference to the usual fat client, a computer intended to take on these roles by it. The exact roles unspecified by the server may vary, from provided that data perseverance (for example, for diskless nodes) to actual information dispensation on the client's behalf. The most common type of modern thin client is a low-end computer not curable which concentrates solely on provided that a graphical user interfaces to the end-user. The remaining functionality, in demanding the operating system, is provided by the server. Thin clients have their roots in multi-user systems, usually mainframes accessed by a few sort of terminal computer. As computer graphics developed, these terminals transitioned from provided that a command-line frontier to a full graphical user interfaces, as is common on modern thin clients. The perfect multi-user environment along these lines was UNIX, and completely graphical X terminals were moderately accepted thin clients in the 1990s. Modern UNIX derivatives like BSD and GNU/Linux carry on this multi-user belief.
Figure: IBM EXX thin client
Characteristics of Thin client:
Thin client as programs
The concept of a thin client extends straight to any client-server design: in which case, a thin client request is simply one which relies on its server to procedure most or all of its business reason. This idiom is comparatively common for computer safety reasons a client clearly cannot be trusted with the logic that determines how truthful they are; an opponent would simply skip the logic and say "I'm as trustworthy as possible!"
Figure: Size comparison - traditional Desktop PC vs. Clientron U700
Since the customers are made from low-cost hardware with few touching parts, they can function in more hostile environments than straight computers. However, they unavoidably need a network relationship to their server, which must be remote from such hostile environments. Since thin clients are contemptible, they offer a low danger of theft in general, and are easy to restore when they are stolen or broken. Since they don't have any complex boot images, the difficulty of boot image control is central to the central servers.
Benefit of thin client:
The mixture of optimized hardware, software, and services allows Thin Computing to bring many benefits for any enterprise, business, or organization. Such as:
Unlike PCs, thin clients have no local storage space space devices. So thin clients are not susceptible to viruses and other malware as long as the servers are sheltered. Since there is no way to amass and take out proprietary in order from thin clients, that data is always secure on the server, and acquiescent with privacy system. And since nothing is stored on the desktop, there is nothing of simple value for thieves to actually remove. Safety software is also easier to sustain, update, and improve on a few servers in its position of thousands of PCs.
Thin clients are much easier to position and arrange for the simple because software is delivered to the server. So there is very little hands-on fixing necessary (other than connecting the cables). Support up data is also simple, since server is resides the data. There is no anxiety about staff forgetting to back up their limited hard drives or forgetting to leave their computer associated for usual back ups. Because all applications are stored, delivered from the server, updates can be performed at the wine waiter level, eliminating the need for physical updates of entity systems. This also improves description control for applications.
Thin clients have solid-state expertise; there are no touching parts to be unsuccessful. And with no local storage space space, there is no chance for an entity system to come under assault from viruses and malware. Plus, should a thin client still fail, the data is always directly accessible from another structure. This lack of local storage space, and the problems connected with it, makes data much more accessible to the people who use thin customers than those working on PCs.
Thin client are vastly different PCs because there are no automatic parts, such as fans or disk drives, to go down. With no local storage space of applications or data, it is unfeasible for viruses that interfere structure of the securities. By avoiding the opening of downloaded software while approaching storage and computing power to more dependable servers, thin computing radically increases the dependability of the entire communications.
Drawbacks of thin client:
Thin clients can also be unstated as the advantages of thick/fat clients. For example, thin client servers require a high recital level, since this is where the mass of dispensation takes place.
Thin clients do not hold up multimedia-rich applications, like video gaming. Multimedia-rich applications need a important amount of bandwidth to purpose to their highest potential. Thin clients' use of moderately little bandwidth mean that moving picture; video, and other graphic features are not well supported in this environment. For example, thin clients are often besieged and stop working when they are necessary to stream media or use Flash players.
Operating systems like Windows are intended to run on local property. This in fact makes them less supple, in straight negation to it proposed goals. Since thin clients run on remote possessions it may be hard to run these systems on thin client-server networks. High latency networks, where the lag time in transferring data over a network is long, can make thin clients not viable. If a network is down, there is no way for a thin client to entrance the server and dispensation power it needs to respond to requests. In contrast, thick clients can go on to work offline if a network is down. This single point of failure means that thin clients are banned from using and desktop applications and may consequence in lost work.
The network support infrastructure required to utilize Thin Client
Thick clients support any kind of server and do all the required work is just a file store. Client machines are characteristically of a high requirement and host application locally. Such networks are better for the use of difficult applications such as Digital Video Editing or explicit design and where a lot of peripherals are used. This disadvantage of a merely thick client network is that all preservation, such as application setting up and system updatesÂ needs to be conducted locally on a station by station basis. Applications are installed nearby on every station on the other hand they are managed and forbidden centrally.Â All management tasks, including the RM organization Console are accessible transversely the network and can be worn to supervise any station.
Thin clientÂ networks move the dispensation control missing from the workstation or client onto a isolated computer - characteristically an inner server. The remote computer is associated using a particular protocol that essentially allows the communication of audio and video data from the server to the client and the safe transmission of keyboard and mouse contribution sever back to the client. When connection over a controlled locale network or crossways the Internet. When user connected to remote computerÂ set up a logon assembly on that computer in a parallel wayÂ asÂ they would log on to it nearby. Once logged on they have the similar settings they require when they logon any place also on the system, and the same limitations and permissions apply to them. Several remote users can be logged onto the same server at the same time, since thin client require lot less hardware specification. Because the client itself has little to do but exhibit information and accept user input, the dispensation power it requires is minimal - consequently the term 'thin' client. This means that you can use purpose built thin client devicesÂ or existingÂ older/low-specification hardware.
Two different solutions offered by two different commercial vendors:
HP (Windows XP & Linux)
WYSE (Windows XP & Linux)
Processor: AMD Sempron 2100+
512 DDR SDRAM
Graphics ATI Radeon X1250
Input/output support Keyboard (USB/PS2), Mouse (USB/PS2)
Audio Internal amplified speaker and 44-KHz sample rate and Output 1/8" mini microphone
Security lock slot, USB compartment and also amart card option.
Via C7 Eden processors feature within every Wyse V class (800Mhz inside the L Family and 1.2 GHz inside the LE Family) delivering brilliant recital with low energy use
The Wyse V class chains fixed and wireless networking, serial, video, sound and neat card connectivity
Supplied with a perpendicular foot as standard and optional level standing feet Can also be mounted to walls, under desks and to the stern of monitors
Draws just among 13 to 15 watts of power when connected to one keyboard, PS/2 mouse and monitor
Full addition with Wyse WSM proviosioning software with the Wyse V00L and V00LE
Deploy fully practical desktop computers, with better manageability with the ability to create modified system images.
Introduction: installing thin client in a computer requires some additional steps to be taken along side software installation like setting up the terminal creating an environment for network booting , etc below I have shown the method of installing and setting up a popular thin client based OS called " Thin station "
Thin station is a lightweight client Operating System for thin clients which has a rebuilt utility of connecting to the server, thin station is based on Linux construction but is able to run in any server environments. It is mostly intended for office school labs and other business environments
Preparing windows for installing thin station
Booting from a flash drive or compact disc
A free tool called magic disc can be found in
After setting up a virtual disc drive should appear in my computer amongst drives
Next insert the flash drive to the peripheral
Installing thin station
A self extracting precompiled image file can be downloaded from http://www.thinstation.org/
The setup file extracts into C:\Documents and Settings\Administrator\Thinstation-2.2.2\prebuilt
The following steps should be taken in order to built an ISO with user pattern
mount the ISO using magic disc mentioned before and copy the files from ISO to "C:\Documents and Settings\Administrator\Thinstation-2.2.2\prebuilt\LiveCD\desktop\RebuildIsoWithConf\cd-files"
Copy the "thin station. profile" from "C:\Documents and Settings\Administrator\Thinstation-2.2.2\prebuilt\LiveCD\desktop\Floppy" and copy it to "RebuildIsoWithConf\cd-files"
run rebuild-iso.bat from "C:\Documents and Settings\Administrator\Thinstation-2.2.2\prebuilt\LiveCD\desktop\RebuildIsoWithConf"
Above steps are independent to CD or flash drive below steps should be taken for compact disc or flash boot
Upon writing the image file to CD the thin station should boot up from the CD device
booting from flash drive
a new image should appear in the folder labeled "RebuildIsoWithConf"
Next by using the xcopy command in the command prompt files in the cd drive can be written in the removable drive
"xcopy G:\*.* h: /s/e/f"
Where G is the virtual CD drive and H is the flash drive
Upon choosing the boot media as flash drive the thin station should boot automatically
The thin station interface
Screen Shot when Terminal Service is Loading
A Screen Shot when Thin station booting up
A Screen Shot for GUI Interface
Setting up Terminal Services for connecting thin station to the server:
Go to Start menu >Administrative tools> configure your server wizard and choose terminal server and press next two times to confirm the system will restart with confirmation
A box should appear as a confirmation of the system of being a terminal server press finish to exit
Go to Control Panel > Add/Remove >Windows Components Wizard section. Click on Terminal Server Licensing and follow the installation instructions.
Web site Reference: