I wrote Networking Essentials today and after failing on the first attempt with 741 in Feb, I passed today with 965.

I could say that I owe my good score to the information on your site – especially the link posted on 26/4/98 called "Questions". Thanks Robert!

I had seen about 90% of the questions before. I did, however, note some questions that were slighty unfamiliar:

1. A computer uses NWLink IPX and not able to access the network. Hardware is not the problem. What is the probable cause?

1. Incorrect sub-net mask on the client
2. Incorrect IP address on the client
3. Incorrect Frame Type on the client
4. Incorrect WIN.INI file on the client

I chose C.

1. An client in an Ethernet network is not able to access the network.

• Initialisation was successful. All other clients can access the network. Hardware is not a problem.

   

  Is the problem?

1. Insufficient extended memory in the client
2. Network adapter in server configured to the wrong transceiver
3. Network adapter in client configured to the wrong transceiver
4. There are an excess number of collisions on the media.

I chose C

1. In the past year, 55 clients have been added to a 10BaseT network. The network is slow in peak times. What is the most economical solution?

1. Replace Ethernet adapters with FDDI?
2. Replace Ethernet concentrators with Ethernet Switches
3. Replace Ethernet components with 100Mbps ATM
4. Rplace Ethernet components with 16Mbps token ring.

1. A network with 27 servers and 750 clients running NetBEUI, IPX, TCP/IP.

• A client running NWLink IPX is installed which is not able to access some shared network resources. All others are able to access.

  Cause?

   

1. Subnet mask setting on client incorrect
2. Protocol mismatch between new client and inaccessible shared resources
3. NetBIOS names duplicated
4. Cable failure between client and inaccessible resource.

I chose B but wasn’t 100% sure.

1. The only scenario I hadn’t seen word for word in the braindumps!:

• Required: Centralised control of access to shared resources

  Optional:

1. Track access and attempted access to shared resources
2. Track attempts to guess passwords
3. Implement a method to protect user accounts from password breaking.

Solution:

Implement NTFS with user level security on all servers. Set appropriate access control on shared resources. Change passwords every 40 days. Disk striping with parity. Backups.

I said meets required and one optional.

I had this question in addition to the other two scenarios that had one with auditing and one without!

Hope this helps! On to NT Workstation!