Explain the following:  (1) System DSN   (2) User DSN   (3) File DSN?
537739
According to Microsoft documentation, 'DSN' means "The name that applications use to request a connection to an ODBC data source." In other words, it is a symbolic name that represents the ODBC connection. It hides the connection details like database name, directory, database driver, UserID, password, etc. So when making a connection to the ODBC, you don’t have to remember the database name, where it resides, etc.\n\nSo, what’s a file DSN?\n\nBefore I can explain this I need to explain System and User DSNs:\n\n1. System DSN: This is the DSN used through out the system, no matter which user logs in. Meaning, all users on the system can see this DSN and use it (as long as they know the user ID and password). The connection parms are stored in the registry.\n\n2. User DSN: This is a DSN created for a specific user. Only the user who created the DSN can see this and use it. Like System DSN, the information is stored in the registry.\n\nIn both these two cases, DSN details are stored in the system registry.\n\nWith that, let me explain what a file DSN is. Instead of storing the DSN details in registry, you store it in a file -- simple!!! The file is a simple text file, with a .DSN extension.\n\nAlthough it sounds simple, you need to know the parameters that make up a DSN. But again, it is not all that difficult, as you can look this up in any ODBC reference, or online help that comes with Visual Basic or Access.
1158251
Ya u can use 'local group" if u wanna tray that in ur server for trainig.\n\n\nGo to the Administrative tools, active directory, usrs and coputers\n\nGood luck
630463
Check this\nhttp://en.wikipedia.org/wiki/Comparison_of_file_systems
1094664
Actually DB server hostname/DSN has been provided by you web hosting company this details you can get from there.\nYour Database Name: in that server hosting tem has alcotated some db to you website\nDatabase Username/ Password: to authaticate you\nprefix for table in database for more information go to Source
259922
Probably the security is not set up properly.\n\nIf you are on a domain, you need to share folders and assign permissions.  Right-click on a folder and select "Sharing and Security".\n\nIf you are not on a domain... Then if say UserA on PC-A needs to access something on PC-B, then UserA needs to have his username and password configured on PC-B in order for him to access it.
521883
shared files are widely distributed across networks, administrators face growing problems as they try to keep users connected to the data they need. The distributed file system (Dfs) provides a mechanism for administrators to create logical views of directories and files, regardless of where those files physically reside in the network. Fault tolerance of network storage resources is also possible using Dfs.\n\nThis step-by-step guide describes how to use the Dfs Administrator snap-in. Installation of the Dfs service takes place automatically during Windows 2000 Server Setup. However, you must configure Dfs in order for a Dfs share to be accessible to clients.\n\nPerform these steps on the domain controller while logged on as a user with administrative privileges.\n\nIn the Windows 2000 operating system, Dfs can integrate with Active Directory to create fault tolerant Dfs roots on Windows 2000 domain controllers (DCs) and member servers. If you have multiple servers in your Windows 2000 domain, any or all participating servers can host and provide fault tolerance for a given Dfs root. Active Directory is used to ensure domain controllers in the domain share a common Dfs topology, thus providing redundancy and fault tolerance.\n\nAlternatively, you can create a stand-alone Dfs server, which does not take advantage of Active Directory and does not provide root level fault tolerance. A DC can host a single Dfs root, and you can have an unlimited number of Dfs roots in each domain. Up to 32 DCs can host the same root. Multiple Dfs root volumes can be hosted in the domain. Additional computers hosting the root or child nodes (links) improves load balancing, fault tolerance, and site preference to directory service-aware network clients. Dfs links below the root can reside on any UNC path accessible to the Dfs server and clients.\n\nIn this walkthrough, it is assumed you are creating a fault-tolerant Dfs Root.\n\nStarting Dfs\n1.Click Start, point to Programs, point to Administrative Tools, and then click Distributed File System.\n \n2.Right-click Distributed File System in the left pane, and click New Dfs Root. The Create New Dfs Root wizard appears, then click Next.\n \n3.Make sure that Create a domain Dfs root is selected, and then click Next.\n \n4.Select the host domain for the Dfs root; in our example, this is san.com, and then click Next.\n\nSelect Host Domain for Dfs Root\n5.Accept the name of the host server for the Dfs root. In our example, this is displayed as HQ-RES-DC-01.Reskit.com. Click Next\n \n6.Choose the local share point to be used on the target to host the Dfs root. In our example, click Create a new share and type the path to share as c:&#92;dfsbooks and the share name as books. The snap-in lets you create both a new share and new directory if they do not already exist.\nSelect the share for the Dfs root volume\n \n7.Click Next. If the specified folder does not exist, you are asked if you want to create it. Click Yes to continue. Add a comment if you wish to further describe this root. Click Next.\n \n8.Click Finish to create the Dfs root. After the Create New Dfs Root wizard has completed, you are ready to administer your Dfs root.\n \nIf you have multiple domain controllers hosting a fault tolerant Dfs root, keep in mind that fault tolerant Dfs uses Active Directory to store topology knowledge. Thus, it is necessary for the topology knowledge to converge between the domain controllers. Updates to the Dfs configuration initially take place on the host server in the Windows 2000 domain. Domain controllers may have a different view of the Dfs configuration until multimaster replication from the Dfs host makes changes fully replicated between all domain controllers in a domain. Dfsthe root and all its linksis stored as a single entity known as a blob. When a change is made to the blob, the whole blob replicates until consistent throughout the domain.\n\nThis takes about five minutes between any given two replicat
777188
Network Operating System?\nNot Otherwise Stated (or Specified) ?
930685
You have to ask the right question.\n\nHow do your users use the LAN they are on? Server based applications? Internet access (ie. Mail, browsing, web apps, etc?)\n\nIf they use server based apps then file sharing is more important.\nIf they use the Inet then network apps is more important.\n\nIf you are the SysAdmin it is your job to make everything work for your user community. They are your customers!
562626
if you know a lot about computers, pc and operating systems, then  you might want to load a linux server software on the pc and start from there.  if you want to make it easy though  you could do the following.\n\non your harddrive, set up a folder called share.  within that folder set up sub folders for each person that you want to store info on.  for the main folder using properties, declare it as a share and you can assign a password to it or not.  for each of the personal folders, assign a password that is only known to that person.  depending on your level of windows you may need to declare that file sharing is permittted.  \n\non each of the individual pc, create a network drive that points to the share folder, and a second network drive that points to the personal folder.  do  your homework and read up on the syntax etc.  now each person can store files in their personal folder and keep them protected unless they wish to share the password, and they can also store files in the main folder for everyone to see and use if necessary.\n\nif you have a printer connected to that new server pc, you can share the printer, and everyone on the lan can also use it by creating a network printer.  same thing with external usb drives, dvd drives, cd etc.  it can give you a lot of flexablity, but you have to manage it, its not magical.
35911
you must have the 2 systems networked, with a data connection established (typically ODBC), and authentication setup. (with the database already setup)
394120
the client connects to the server and gets all the info it needs...\n\nthe client is the users machine
4687
Windows will not allow you to name files or folders after certain reserved names such as "LPT1" or "PRN".  These names refer to hardware devices in the system and would confuse the OS if you tried to refer to a file with that name.  "CON" is the system name for console.  Therefore you can not use that as a folder name.
484154
The local administrator has access to system files and folders that the application changes during installation. You can change your access by going to Control Panel, User Accounts.
343604
root is the default sys admin name. at the login window type root and then a password you will remember and it should log you into the root account( you are now god do a happy dance) if it dosnt log you in it means someone else is already the root.
9243
an idlist is a shell link to your Control Panel. Apparently, the computer cannot locate a system file needed for the use of the Control Panel.\n\nAs you could notice, there is no file system path for the control panel. So to identify a file system path there, Windows creates a string of numbers called IDlist.\n\nAlas, the numbers (520:1024 in your case) are not a "real" string, rather the number of the allocated buffer and its memory needs.\n\nYou can try to "read" the numbers, some websites give you a kind of key, but it's really really difficult. Take a look at http://help.madshi.net/IIDListRef.htm \n\nSo I would suggest the intuitive approach: Did you install a program with a path to the Control Panel (a screensaver? fonts?) If so, restore Windows to the point before the installation.\n\nGood luck!
384491
For the same reason that a user program can't directly\nscribble on the raw disk or tweak the device registers\non any other peripheral.  \n\nThe OS is there to mediate access between multiple\nprocesses (and sometimes multiple users).  The networking\nstack can be written "knowing' that the device drivers\nwill create well-formed packets and "follow the rules".\n\nIf you really want direct access, build your own device\ndriver (or even your own variant of the Linux kernel)\nand you can control both the horizontal and vertical.
1180953
The following file names are also reserved under Windows:\n     com1, com2, com3, com4, com5, com6, com7, com8, com9, lpt1, lpt2, lpt3, lpt4, lpt5, lpt6, lpt7, lpt8, lpt9, con, nul, and prn