What are the differences between network computer and thin client computer?
343106
Thin Client:\nIn client/server applications, a client designed to be especially small so that the bulk of the data processing occurs on the server. \nAlthough the term thin client usually refers to software, it is increasingly used for computers, such as network computers and Net PCs, that are designed to serve as the clients for client/server architectures. A thin client is a network computer without a hard disk drive, whereas a fat client includes a disk drive.\nNetwork Computer:\nAs indictaed above, it has a hard-drive for locally loaded software (and OS) as well as a greater potential for processing power...
1088493
Internet is the whole network of computers that are connected to each other. \nOnline is when you are connected to the internet, or a website that is connected to the internet.
207429
XP Home doesn't have the Remote Desktop server capability.  XP Home can be a client (controlling an XP Pro machine), but it can't be a server (being controlled by another machine).  For that, you can use a program like VNC, free from http://www.realvnc.com . \n\nThese tips should help you get the computers to see each other: \n\n\n1. If the computers run the original or SP1 versions of Windows XP, disable XP's built-in Internet Connection Firewall on local area network connections -- it's for use only on a direct modem connection to the Internet.  If they run SP2, enable the exception for file and printer sharing in the Windows Firewall.  Disable and un-install all \nother firewall programs while troubleshooting.  When un-installing a firewall program, use the un-install procedure provided by the \nmanufacturer .  Don't use Control Panel | Add or Remove Programs, which might not completely un-install it. \n\n\nFor more information, see: \n\n\nWindows XP Internet Connection Firewall \nhttp://www.practicallynetworked.com/sharing/xp/ic_firewall.htm \n\n\n2. Use only one protocol for File and Printer Sharing.  If the network needs more than one protocol, unbind File and Printer Sharing from all but one of them.  Details here: \n\n\nWindows XP Network Protocols \nhttp://www.practicallynetworked.com/sharing/xp/network_protocols.htm \n\n\n3.  Make sure that NetBIOS over TCP/IP is enabled on all computers. Details here: \n\n\nEnable NetBIOS Over TCP/IP (NetBT) \nhttp://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm \n\n\n4. Run "ipconfig /all" on XP and look at the "Node Type" at the beginning of the output.  If it says "Peer-to-Peer" (which should actually be "Point-to-Point") that's the problem.  It means that the computer only uses a WINS server, which isn't available on a peer-to-peer network, for NetBIOS name resolution. \n\n\nIf that's the case, run the registry editor, open this key: \n\n\n   HLM&#92;System&#92;CurrentControlSet&#92;Services&#92;Netbt&#92;Parameters \n\n\nand delete these values if they're present: \n\n\n   NodeType \n   DhcpNodeType \n\n\nReboot, then try network access again. \n\n\nIf that doesn't fix it, open that registry key again, create a DWORD value called "NodeType", and set it to 1 for "Broadcast" or 4 for "Mixed". \n\n\nFor details, see these Microsoft Knowledge Base articles: \n\n\nDefault Node Type for Microsoft Clients \nhttp://support.microsoft.com/default.aspx?scid=kb;en-us;160177 \n\n\nTCP/IP and NBT Configuration Parameters for Windows XP \nhttp://support.microsoft.com/default.aspx?scid=kb;en-us;314053
656784
It relies on another computer to function. The thin client may have some programs in ROM, but it relies on  terminal server to operate at it's full potential.
720891
Unix or Linux would be my answer.  Linux especially can be adapted for a network's server needs.
155724
The biggest differences are going to be the size of you database and your security.  Businesses are going to need dedicated storage area and firewalls and/or proxy servers.  Home networks can do most of this through software instead of hardware.
660668
If you want a server to remain stable and have close to 24/356 uptime, you don't want a Windows server. If the Windows clients will be like dumb terminals, you might need to put some work into getting your clients to work with your non-Windows server, but for most purposes...\n\nLinux all the way.\n"Know-how" isn't even required if you use Fedora Core, Red Hat Enterprise Linux, or SUSE (among others), and their graphical server configuration tools.
384081
Well, all Messneger applications do the following:\nthey use\n- TCP Protocol for authentication (LOGIN), etc\n- UDP Protocol for chatting\n\nThe difference between the 2 is that TCP guarantees the delivery of data while UDP doesn't, and thats why, in some cases, while text messaging or Voice chatting, some text &/or portions of voice conversation is omitted...\n\nHope this answers your question...
1171285
yes, if they have network capability - what kind of computers are you talking about?
215048
Could always use a remote client such as Tight vnc, its pretty good, works with windows and unix. Just be careful which ports you leave open ;-)\n\nphil\n\nps. its open source
766782
The principal difference is multi-tasking.  Older computers could only run one job at a time.\n\nOn the old mainframes your program had to be written off-line (usually by hand on paper, then punched into a deck of cards), then submitted as part of a "batch job" to the computer operator.  The operator would then mount any tape or disk needed for the job (the data files), load the program into the computer's memory, and run it.  When this was finished they did the same for the next program, and so on.  The program itself did not reside on the computer or any of it's tape or disk drives except while actually running, and no other program or process could run at the same time.\n\nSimilarly the early operating systems for desktop computers could only handle one thing at a time.  They were more interractive because you wrote your programs while sitting at the computer, saved them to disk or tape, and ran them right there for testing ad debug instead of submitting the job and waiting for it to come back an hour or a day later -- maybe without having run at all due to some simple syntax error or such.  But they were still only running one program at a time (the editor, the compiler, and hopefully the resulting executable code).  There were early desktop operating systems that could have several programs LOADED at once into different segments of memory, but only the one in the top window was actually running -- the others were basically "hibernating" until the top-window program ended (or the window was minimized) and then the new "active window" program began or resumed running.\n\nModern operating systems allow many programs to be running simultaneously on one computer, each sharing the resources of the computer with the other applications.  This required the development of means by which the operating system could seize control back from a misbehaving program that was "hogging" all the system resources or caught in a perpetual loop, so that the "blue screen of death" or similar crashes could be avoided.\n\nI don't recall for sure when the first multitasking O/S was developed for mainframes, but I think it was in the 1970's for the early Hewlett-Packard systems like the HP3000.  The first multi-tasking O/S for deskdops that I can recall was the early 1980's Apple Macintosh O/S, but to be honest I didn't use that one much so it might not have been a true multitasking O/S (might just have been a top-window-is-active type).  The earlier Apple computers (Apple I, II, II+, IIc/IIe, etc) were not multitasking nor were any of the PC O/S's up until about Windows 95.  The Commodore Amiga might have had basic multitasking capabilities (it had a lot of advanced features) and I think the Apple IIgs did as well.\n\n- - - - - - - \n\nAnother major way in which operating systems have improved is in "hardware abstraction" -- it used to be that you had to tailor a program to each new computer it was going to be run on, the "operating system" really only handled file I/O and printing.  Modern operating systems make it almost irrelevant what particular computer you are running on -- only the O/S itself has to be tailored to the hardware, from there it handles loading all appropriate device drivers and such so that applications programs don't have to be concerned with HOW to write to the printer or whether or not the drivers were loaded.
487089
The main advantage of a network is that computers can share information.  A computer network can store more data than a stand-alone computer.  This is great if you have a business because your employees can exchange vital information easier.\n\nThe main disadvantage would be security concerns, i.e. someone hacking into your network.  However, you can buy software and hardware to help prevent this.  Just remember that any protection you get can be broken if the hacker has enough time and patience.
1003447
microsoft windows nt- to go hand to hand with the powerful unix client server system that once demanded corporate computing,microsoft developed microsoft windows nt.unlike windows 95-98 windows nt is specifically designed for client server systems to msupport client server computing ,windows nt is made up of 2 components,windows nt work station,and windows nt server, windows nt is a sophisticated operating system oriented to business needs ,the windows nt work station module is designed for individual desktop computers,on screen it looks like windows 95,but it isn't as easy to use.the real benefits of nt workstation emerge in a networked corporate environment,where nt desktops link to servers running windows server.
137755
proxy server is a computer that offers a computer network service to allow clients to make indirect network connections to other network services. A client connects to the proxy server, then requests a connection, file, or other resource available on a different server.\n\nIn other words its more or less like a BARRIER between the end computer and the internet.\nExample-> Your PC -> PROXY SERVER -> Internet\nThe proxy server has the ability to monitor every request, incoming and outgoing.
579558
client server, two tier, is comprised of two components: the client that sits on a workstation and a database server. The client communicates directly with the database and processes the information locally.\n\nthree tier architecture is comprised of a client, a middle  tier, and a database server.  The client communicates to the middle server, the middle server communicates to the database server.  Usually the middle server holds or pools the database connections. The middle tier usually takes the form of a web server that sends information back to the client so it can be rendered. \n\nhth, r
868579
I found this article that might give you some suggestions:\n\nhttp://www.networkcomputing.com/showitem.jhtml?articleID=160910914&pgno=1\n\nplrr
363845
internet is collection of comoputers and small networks. networks is also group of computers. they can have different types of hardware and software. they all have technique to connect to the internet. your computer is also part of the internet.