Protocols - few is better

How many protocols does your LAN use?

Best Practice (Litmus Test)

Professionals: Use TCP/IP as their only protocol

Amateurs:  Insist on installing NetBEUI

How many Protocols does your LAN use?

Professionals realize that the best practice is to only install TCP/IP, adding other protocols is just duplication.  TCP/IP is wonderful, it does everything you would ever need a protocol do to.  Moreover the more protocols you have the more network traffic there will be.  In particular avoid protocols like NetBEUI that broadcast.

Some network managers get upset when I suggest they remove NetBEUI.  What is fascinating is their reasoning.  They say: 'It is so much faster.  We have applications that only work with NetBEUI'.  I say: 'What about all that broadcasting?'  Then I challenge them to just run TCP/IP on their network.

There are always exceptions to any rule, and I would allow NWLINK if you have old Netware servers. Also, I did once see a convincing case for using a second protocol for RAS.  The client wanted a fix to secure and isolate clients dialling into his network.  However, I would have preferred to :

a) Decommission those Netware servers

b) Implement a firewall as a RAS solution.

Challenge: Check out some of the new Protocols in Windows 2000

• LDAP
• IPSEC and IPSECMON
• Kerberos (Kerbtray in the resource kit)
• L2TP and PPTP
• CHAP and EAP
• BAP and PPP
• OSPF in the Routing and RAS snap-in

More Information. As an MCT trainer, I can thoroughly endorse TrainSignal because they deliver practical hands on training.  In particular, I like the way that TrainSignal cover all learning methods, instructor lead, video and of course text material.  You can either take one module, for example File Server or go for a combination of modules.  See more about Windows 2003 training here

Sign up to my new Ezine and get a free Best Practice ebook.