Customer center

We are a boutique essay service, not a mass production custom writing factory. Let us create a perfect paper for you today!

Example research essay topic: Blah Blah Nt Server - 5,200 words

NOTE: Free essay sample provided on this page should be used for references or sample purposes only. The sample essay is available to anyone, so any direct quoting without mentioning the source will be considered plagiarism by schools, colleges and universities that use plagiarism detection software. To get a completely brand-new, plagiarism-free essay, please use our essay writing service.
One click instant price quote

... ug to all of you future admins. Don't be a censored head! Just because a printer won't print doesn't mean that the printer is the problem. Do your homework and trouble-shooting before calling the printer manufacturer and blaming them for having a crappy printer. I will give you an example of what I am talking about.

I was dealing with a PC support person for the Cleveland Cavaliers. I got an email stating that the printer has never worked since the day that they got it and has cost them thousands of dollars in down-time and he wanted to know what we planned on doing about it. I asked him what the problem was and he said, "It doesn't print jobs sometimes." Well, that is certainly helpful - I know exactly what your problem is... "you are a retard", I though to myself. This guy had done 0 troubleshooting and really had no problem description. So, I gave him a list of things to check (not sure if he ever did) and told him to CALL me.

So, a month later I get an email from him and he tells me that he has checked everything and still having the same problem and said that he was 100 % sure that it was the network card. After arguing in vain with him I told him that I would send a new network card and when it didn't fix the problem he could CALL me with a decent problem description. A month later he emails me again and tells me that it is still happening and they are losing thousands of dollars per day and blah blah blah. I basically emailed him back and told him that I wouldn't work with him anymore because he was an idiot and sucked at his job and sucked as a human being. Then his boss emailed me and we got in touch with each other and had it fixed in 1 hour as it turned out to be a simple timeout setting. Moral of the story?

Don't be that guy (or girl). Ok, got that off of my chest. Network printing has a couple advantages over a parallel or serial connection. The most obvious reason is that a network connection allows multiple users easily share the same printer and allows for permissions to be set for that device.

It will typically be faster to connect to printer via ethernet than a parallel connection. How much faster depends on a variety of variables including, printer processor speed, computer processor speed, network traffic, data format, etc. In order to put a printer on a network, you will typically need a print server. During driver installation on an NT server, you will want to select local printer if this NT box will be the print server. The clients, on the other hand would select network printer and browse to the printer or enter the UNC path to it. When installing on the print server you have to select shared and give it a share name (under 12 characters) in order for clients to be able to use the print queue.

When you select "shared" you have the option of specifying the operating systems that will be sharing the printer. If you select any of these you will need to supply drivers for those operating systems. If you are accessing a shared printer from an NT workstation, you do not have to load the drivers. The workstation will pull them off of the server during installation. NT allows you to pool your printers so that your job will print on the first available printer. This only works if you have more than one identical printer with an equal amount of memory in each.

Once your drivers are all installed, you need to worry about spool settings. By default, an NT server will spool print jobs so that the client computer is "freed" up so that the user can continue with their work. This is called background printing. There may be occasions where you will not want to spool the jobs to the server - maybe you have a crappy server that can't handle the workload or for trouble-shooting reasons. In these situations, you can change the scheduling to "print directly to the printer." Printer permissions are only slightly different than NT's regular permissions. The table below should explain it.

No access Can't print or do anything else. Print Can print, pause, resume, delete and restart their own documents only. Manage Documents Have "print" permissions for all documents (not just their own). Can also control document settings. Full access Have "manage document" permissions and can also change printing order and change the printer's permissions and properties. In addition to permissions, priorities for print jobs can be set.

For example, If you are the president of a company and you feel that your documents are more important than the secretaries', then on the server you can creat 2 printer objects and assign a different print priority to each so that your documents come out first. Like other things in NT, a printer can be audited by enabling "file and object access auditing in the user manager. Then in the printer properties, you can select the users and / or groups that you would like audited. I may include more info here than is needed for the test, but after working for a printer company I found that most people are pretty ignorant about printers. Even Administrators would call and would be completely clueless as to where to start. Having said that, I will start off with the famous "can't print" problem.

Please note that the following discussion focuses on TCP/IP printer connections, whereas on the exams Microsoft will be referring to HP printers using the DLC protocol. No matter what the problem is, whether it be print quality or connection related, print an internal page. Most printers have some sort of startup or configuration page that it will print and this page may also have the printers network settings on it. This will verify that the printer is working properly.

Treat the printer just like you would a computer that is not participating on the network properly. I. E. if it is a TCP/IP printer, try to ping it.

If the printer uses a jet direct box with IP, ping the box. If this doesn't work make sure that you can ping another device on the network. Check your network settings. Make sure that someone hasn't fiddled with the printers settings and that the printer's and computers IP settings are correct. Make sure that everything is plugged in correctly even if you are sure that it is.

Don't be cocky, you don't want to be that guy that calls tech support and they help you determine that the printer isn't connected. Believe me it happens. I have also seen a case where an ethernet cable was chewed up by rats, so take a good look at it. One of the best ways to test cabling, is to take the drop in question and connect it to another printer or computer. Can you ping the new device? If not then you probably have a cable problem.

If you were able to ping it, then see if you can print from the server. If not, then do the following: Make sure that NT is pointing at the correct port. Verify that the correct driver is installed (you may need to consult your printer manufacturer to find out which is the correct one). Reinstall the driver. If you were able to print from the server just fine, then try to narrow down whether it is just one client or several or all that are unable to print.

This is where it starts to get tricky and you have to do your homework. If only a certain group of users can't print, it may be a routing problem. If it is all, then something probably isn't set up correctly on the server. If it is just one user that can't print, then it is probably a driver problem (assuming that they can access the rest of the net. ). If for some reason a document gets stuck in the spooler, restart the spooler service. This is, of course, isn't even the tip of the iceberg but these are the basics.

The main point is that when troubleshooting anything, try to narrow it down first. You probably won't figure it out on your first try - use the process of elimination. -- CONNECTING A DOS WORKSTATION TO NT -- DOS is the most complicated one to connect to NT because it has no built-in networking support. There are several different ways to do this and we will look at each. The first way is to use NT's NCA (Network Client Administrator). The NCA setup will ask for your Network card type, protocol info, etc and will then create a file on a floppy that you would use as a boot disk on the DOS client after modifying the protocol. ini file.

This will provide enough network support to connect to the NT server. Then a batch file will be run that will install the Microsoft Network Client 3 for DOS. There is an easier way to set up the Microsoft Network client 3 for DOS that bypasses using NCA. Browse to the "clients" directory and look in the "ms clients" subdirectory. In here, you will find a "disk 1 " and a "disk 2 " directory. Copy each of these to a separate floppy disk.

Now all you have to do is install disk one into the DOS client, switch to the A drive and type setup. This will run the installation program and ans should be pretty straight forward from there. When you first try to logon, you will get a message that your password has expired so you will have to change it using the following command: net password /domain: (your domain) (username) (old password) (new password). You will probably get an error message, but the password has been changed and should work when you try to logon again. -- GETTING AROUND THE NETWORK WITH DOS -- To browse the network, use the "net view" command without the quotes. To view shared resources on a particular server, use "net view (server name) ." To connect to a shared resource, use "net use (drive letter): (server name) (resource) ." If you need to map to drive letters higher that E, then you will have to edit your config. sys file and add LASTDRIVE = (whatever you want the last drive letter to be).

To use a printer type "net use (port such as lpt 1: ) (server) (printer share name) ." To disconnect a network connection type "net use /delete." -- CONNECTING WINDOWS FOR WORKGROUPS TO NT NETWORKS -- During installation of Windows for Workgroup you will install the network card. If it was not done at this time or you installed a new network card, then go to the Network Group and run the network setup program. Once the network card is setup and you have logged into the domain, you can browse shared network resources and servers. To do this, open file manager and click "disk" and then "connect network drive" and you will see the browse list. Working with printers is similar except you open Printer Manager and click "Printer" and then "Connect Network Printer." -- CONNECTING WINDOWS 95 / 98 TO NT NETWORKS -- Like Windows for Workgroups you will have the option of setting up network support during Windows installation.

But again let's pretend that it didn't happen that way or that you are adding a new network card. To set this up, all you have to do is go to the networking control panel, click the configuration tab, select "add" and you will see choices of client, adapter, protocol and service. Select "adapter." Select your adapter type or go to have disk if you wish to install 3 rd party drivers. IPX and Netbeui protocols will automatically be installed. Clicking on the "add" or "remove" buttons from the configuration tab to add or remove protocols. In order to enable the workstation to log into the domain, you will need to go to the "properties" of Client for Microsoft Networks.

In this dialog box, you will need to select "log on to Windows NT domain" and enter the domain name. Once finished with all of this you will have to reboot and will then be able to log in. Like NT. Windows 95 / 98 uses the Network Neighborhood interface to browse the network.

What the hell is it? It is similar to a centralized network - remember that from networking essentials? Essentially, the network would have 1 or more terminal servers and the rest of the computers would be almost like dumb terminals which are also known as "thin" clients. Thin clients can be any crappy old computer that you have laying around which is one of the attractions to this type of set up - hardware savings, although you have to have enough beefed up servers to support them. This is not the only advantage however, you also save on support as Winter can be configured to run all of the applications on the servers.

This means that if there is a problem, odds are good that it is occurring at the server which makes for easy and centralized support. Installation of the Terminal Server is very similar to an NT installation. Once installed, you will notice some differences in the administrative tools from NT 4. 0 as it will now include the following: Terminal Server Client Creator -- Will create floppies for Client installation on the workstations. Terminal Server Administration -- The Big Brother application that allows you to view what the clients are running, disconnect them and view protocol information. Terminal Server License Manager -- Allows you to add or subtract client licenses that you must pay for. Terminal Server Connection Configuration -- Used to configure the RDP protocol, set security and a bunch of other stuff.

In order to set this up for a workstation, the Windows Terminal Client must be installed. On the server side, you will need to select either Remote Desktop Protocol (RDP) or MetaFrame. MetaFrame is faster as it only sends the changed information from the client as opposed to RDP which will resend the whole desktop if a user deletes a file from it, for example. -- MACINTOSH CONNECTION TO NT NETWORKS -- NT offers Services for Macintosh to allow MACs to access shared resources as well as provide other services including: Support for appletalk protocols without the need for a gateway. Allows MAC users to access non-PostScript printers without the need to convert documents. Ability to map extensions for PC files which allows MAC apps to recognize PC file extensions.

Allows PC users to access Laserwriter printers without the need to convert documents. Allows for 255 simultaneous appletalk sessions per NT server. So how do you set this all up? On the server side, you need to install services for Macintosh which requires an NTFS partition.

If there are routers on the network, they will need to be configured to route the Appletalk protocol or NT server can be set up to perform this function. If you will be using NT as the router, you will need to specify the zones and the network range. Each number in the network range will support up to 256 devices per network segment. After rebooting, the NT server should show up in the chooser on the MACs and a Microsoft UAM Volume will appear on the NTFS partition. Now MAC volumes can be created using server manager. Finally, you will need to set your permissions for the MAC volumes.

Following are the MAC permissions: See Files Like NT's read permission. Permits the everyone, a primary group or everyone to view files in the MAC volume. See Folders Same as see file permissions except it applies to folders within the MAC volume. Make Changes Similar to NT's change permissions. Permission to view, add and delete files or folders. Can also save changes.

Replace permission on subdirectories Whatever permissions are set and copies them to all of the folders within the MAC volume or a folder within the volume. Cannot remove, rename or delete. Users can't rename, remove or delete a MAC volume or a folder within it. Not much setup needs to be done on the MAC side unless you would like to maintain NT's C 2 security and allow for encrypted passwords. The software for this is included with NT server and would need to be installed on every participating MAC client. You are now ready to move files back and forth, except you will undoubtedly run into problems.

Obviously, Macs and PCs use different file systems and this also means that they won't recognize each others file types without some configuration. For DOS extensions, you will need to use file manager to change the extension mappings for ones that aren't correctly configured. If an application isn't listed then you will need to get to the type and creator codes for the files it supports. On the Mac you will probably need a 3 rd party converter application like Machine. Many applications have cross platform versions available. If you would like to find out more about how Appletalk works, click here to read our tutorial.

The browsing service allows one to view what resources are available on your network. In order for this to work, at least one computer has to be the Master Browser that is responsible for maintaining a browse list. Keep in mind that every computer on the network is either a master browser, backup browser, potential browser or not participating. There are several rules that govern who becomes the master browser as follows: Each subnet on a tcp / ip network must have its own master browser. As long as a PDC is up and running, it will be the master browser and any Bdc's will be backups. This can be changed by editing a couple of registry keys, however.

There will be 1 backup browser for every 15 computers on the network. If the master browser cannot be reached, then an election is held to determine the most suitable candidate. Priority is based on the type of computer (NT Server then NT Workstation then Win 95 then ETC) Whenever you log in to an NT Server, a session is created. Server Manager is a very important tool for managing your domain as it allows you to: Synchronize a PDC's security database with the Bdc's. Add and remove NT machines from your domain. Change an NT server from BDC to PDC or vice versa View users with open sessions on a particular machine View how long the user has been using a particular resource The resources being accessed during the session View all non-hidden computers on the network Send messages or alerts to clients (for Win 95 / 98 must have Win popup running) Allows you to configure the services on your other NT servers.

Remote administration will only work on other NT Servers, NT workstations or LAN Manager 2. x and will only include current data. If you want to view statistics over a period of time then you will need to set up Performance Monitor or use the set statistics server from a command prompt. Server Manager also gives you the ability to disconnect users from a server, however, certain things must be in place in order for it to work. When a user logs on to a server, the server verifies the users login information with a domain controller and a Security Access Token (SAT) is created that allows the user to reaches a share. If you disconnect the user, the next time they attempt to access a particular share the server will look at the SAT and let them back in and the user will never even know that they had been given the boot.

Instead, change the users permissions to no access and then boot them. Then the server will have to query a domain controller to create a new SAT and the domain controller will report to the server that the user doesn't have access to that share. Next, I want to mention the system shares that Server Manager allows you to view. They are as follows: ADMIN$ This share is used for the remote administration of a server. NETLOGON You will only see this one on domain controllers. It is used by the net logon service, which keeps your PDCs and Bdc's synchronized.

It is responsible for handling login attempts. REPL$ Used when NT server is acting as an replication export server. IPC$ Shares the named pipes that are used for the creation of sessions between apps. Used during remote administration or viewing shared resources. drive letter$ This is the root directory for a storage device on an NT server. Server Manager is also used to set up replication.

Directory replication is used to export directories to another NT server or Workstation such as the exportation of login scripts from a PDC to a BDC, for example. This is useful for server load balancing and redundancy. Only NT servers can export, NT servers, NT workstations and OS/ 2 LAN Managers can import. Replication occurs in the following manner: Let's say that you have a domain called "crap."Crap" has a server called "poop" that is configured as an exporter to the "crap" domain. You also have 3 NT workstations that have the directory replicator service running and are configured as importers. Once the service has been configure a directory at C: winnt system 32 REPLEXPORT will be created.

Directories that are to be exported will go in subdirectories that you create within the C: winnt system 32 REPLEXPORT directory. Once everything is configured on the importer, a directory called C: winnt SYSTEM 32 REPLIMPORT will be created. This is where the directories will be copied to. Then, run server manager and click the replication button to set up the rest.

Note that the importers and exporters must support the same file system. You also must make sure that the Directory Replication service is started in the "services" control panel. Unfortunately, most networks will be a mix of network operating systems which makes the process of everything working together a little more complicated. The big one that you have to work about in real life and in the exam is Netware, so really know this section. The 2 basic Netware situations that you will need to worry about for this exam are: NT Server on a Netware network and Netware on an NT Server network. Nwlink is a reputable transport protocol that imitates Netware's IPX/SPX protocol and is all that is necessary to allow NT to run applications from a Netware server, but does not allow file and print sharing.

After this is installed you will now have multiple protocols bound to your ethernet card (if you didn't already). To improve your network performance change the binding order so that the most frequently used protocol is first. File and Print Services for Netware (FPNW) is add on software that allows Netware clients to access an NT Server. The Nwlink protocol must be installed for this method to work. Client Services for Netware (CSNW) allows NT workstations file and print sharing access to a Netware server.

The Nwlink protocol will automatically be installed with CSNW. Gateway Services for Netware (GSNW) creates a gateway that allows NT clients to access a Netware network via an NT Server without having to install any client software. GSNW will also allow you to run many Novell commands from a command prompt. Nwlink is required and will be installed automatically when GSNW is installed. You must create a group called NTGATEWAY on the Netware server and then map a drive on the NT Server for the clients to access. The account used for the gateway must be a member of the NTGATEWAY group and have appropriate permissions for the resources on the Netware server.

Only the NTGATEWAY account is necessary to allow all users to access Netware resources. Accessing a Netware server via a gateway will be slower than connecting directly. Go here for our new whitepaper dedicated to Gateway Services For Netware with installation instructions. Netware Client Software is Novell's solution to the whole mess and substitutes ODI (what Netware uses) based network drivers for the NDIS ones that come with NT. This would be used if you were connecting a few NT workstations or Win 95 / 98 machines to a Netware network and did not want to use CSNW. This situation doesn't really apply to this exam, but I included it just in case.

Once you have all of this figured out, you then need to worry about the frame type. If mismatched frame types are used then communication will not happen. By default, Nwlink and GSNW will only allow you to connect to Netware 3. 12, 4. 1, 4. 11, which use Ethernet 802. 2 frame type. Auto-detection should work fine in this situation as Nwlink also uses 802. 2.

Auto-detect is only capable of selecting one frame type so to connect to NetWare 3. 11 or lower, you need to use manual configuration and select both frame types as these lower versions of Netware use the Ethernet 802. 3 frame type. NT has a file called NWCONV. EXE that is designed to aid in the event that you are moving away from a Novell based network to an NT network. You must first set up GSNW as described above. After running the conversion, you need to make sure that all of the Netware workstations have the SMB redirector's installed so that they will be able to access the NT server.

Performance Monitor uses "counters" not only allows you to view statistics on a local NT Server, but on others located on the network as well. Perfmon allows you to locate trouble areas and bottlenecks on your NT Server. The main sources of these bottlenecks are the network card and drivers, CPU, memory and the disk subsystem. These problems will vary depending on whether your server is a file server or an application server. Perfmon gives you several ways to handle your statistics as follows: Chart - good for finding problems over a period of time.

Log - used to view data over a period of time. Alerts - Alerts can be configured so that you are notified when a particular counter has passed a benchmark that you have set. The results can only be sent to one user. Following are how to tell where the problem is: DISK - If the %disk time is over 90 % or the disk queue length is over 2, then there is a problem with either the disk or the controller.

You must type DISKPERF -Y at a command prompt to enable disk performance counters. NETWORK CARD - Use the network/%network utilization counter. You won't be able to use this unless you have the Network Monitor Agent installed and running. If this value is over 30 % then the network card is the problem.

As previously mentioned, make sure that you bind your most used protocols first. CPU - Check the %processor time. If it is running above 80 % then there is a problem. To get TCP/IP statistics you will need to have SNMP running. MEMORY - The pages / sec counter should be less than 20. The available bytes should be more than 4 mb and committed bytes should not exceed the amount of physical memory installed in the computer.

You will also want to use Performance Monitor to keep an eye on your paging file (virtual memory) by using the %usage and %usage peak counters. Microsoft recommends that the paging file is set to a value equal to the amount of RAM + 12. So if you had 32 mb of RAM, your initial paging file size would be 44, but using Perfmon and viewing the %usage and %usage peak counters is the best way to tell whether it is cutting the mustard. The Event Viewer is a configurable tool that keeps track of what happens on your server and tracks 3 categories of information: System, Security and Application.

The system log will contain information about drivers and services that fail to start. The security log will keep track of events that you enable in auditing. The Application log keeps track of application errors and processes. Task manager allows you to list and stop running programs, start programs, view CPU and memory usage, view running processes and change their priority.

RAS is basically NT's dial up networking service that allows NT to dial out to other computers and to receive calls as well. On the client side it is called Dial Up Networking (DUN) which is not as robust as RAS. Essentially, RAS turns your dial-up-communications into a network card. In NT 4. 0 a new software layer called TAPI has been added which allows software vendors to not have to provide support and worry about the type of modem being used. TAPI handles this for them. RAS supports the SLIP and PPP dialup protocols.

PPP is most commonly used as it allows for dynamic addressing. RAS supports modem, frame relay, direct serial, x. 25 and ISDN connections. Additionally, RAS has an option for multilink PPP that allows for connections to automatically be pooled. By default RAS uses the Netbeui protocol but can also use TCP/IP and IPX/SPX. TCP/IP must be used with programs that use Winsock. An LMHOSTS file on a RAS client can speed up NetBios name resolution.

RAS provides several different authentication possibilities as follows: Allow any authentication including clear text -- Allows for a variety of password authentication protocols including PAP. This is a good option if you have a variety of RAS client types. Require encrypted authentication -- Will allow any password authentication except for PAP. Require Microsoft encrypted authentication -- This will use CHAP (Challenge Handshake Authentication Protocol) or MSCHAP and means that only Microsoft clients will be able to attach. Require data encryption -- Will require all data to be encrypted By default nobody is able to dial in to the RAS server. These permissions have to be set in the Remote Access Service Administrator.

Once this is done, there is a callback security option that must be set. Callback security can be set so that the RAS server will call back a user trying to login to verify that their phone number matches their login ID and password. Not only does it provide security, but it can also save customers money if they are dialing in long distance. There are 3 possible options: No call back -- Default option that provides no added security. Set by caller -- Once the user is validated, RAS will then call the user back. Provides no additional security.

Bibliography:


Free research essays on topics related to: tcp ip, server, nt server, blah blah, printer

Research essay sample on Blah Blah Nt Server

Writing service prices per page

  • $18.85 - in 14 days
  • $19.95 - in 3 days
  • $23.95 - within 48 hours
  • $26.95 - within 24 hours
  • $29.95 - within 12 hours
  • $34.95 - within 6 hours
  • $39.95 - within 3 hours
  • Calculate total price

Our guarantee

  • 100% money back guarantee
  • plagiarism-free authentic works
  • completely confidential service
  • timely revisions until completely satisfied
  • 24/7 customer support
  • payments protected by PayPal

Secure payment

With EssayChief you get

  • Strict plagiarism detection regulations
  • 300+ words per page
  • Times New Roman font 12 pts, double-spaced
  • FREE abstract, outline, bibliography
  • Money back guarantee for missed deadline
  • Round-the-clock customer support
  • Complete anonymity of all our clients
  • Custom essays
  • Writing service

EssayChief can handle your

  • essays, term papers
  • book and movie reports
  • Power Point presentations
  • annotated bibliographies
  • theses, dissertations
  • exam preparations
  • editing and proofreading of your texts
  • academic ghostwriting of any kind

Free essay samples

Browse essays by topic:

Stay with EssayChief! We offer 10% discount to all our return customers. Once you place your order you will receive an email with the password. You can use this password for unlimited period and you can share it with your friends!

Academic ghostwriting

About us

© 2002-2024 EssayChief.com