Tech Tips / Windows XP / Networking
Administrators face the challenge of determining whether they should continue using NetBEUI or implement TCP/IP. The answer for most users is TCP/IP, but some administrators aren't willing to leave NetBEUI. They believe that it's much easier to configure than TCP/IP and provides more security. This isn't necessarily true, however.
TCP/IP does require some administration. Every computer that participates in a TCP/IP requires at least an IP number and a subnet mask. Additionally, computers might require the IP address of a DNS server and a router. By comparison, NetBEUI requires no configuration.
Still, the truth is that Windows XP (and other, older Microsoft operating systems) completely automates TCP/IP's configuration. For example, if you have three computers that need to participate in a network, you simply hook them up, and the computers will automatically obtain an IP address and have the ability to communicate with one other. If you have one computer with an Internet connection, you just share this connection, and the other computers are able to access the Internet. Everything is automated; you don't have to configure anything yourself.
NetBEUI supporters might argue about TCP/IP security. Since NetBEUI is not a routable protocol, no one can hack into NetBEUI-only machines via the Internet. While this is true, they forget one thing: Even though NetBEUI isn't routable, it is bridgeable. This is especially important with cable providers because other customers might be able to access a computer if not manually prevented. Windows XP ships with an integrated personal firewall that can secure Internet connections and prevent intrusions.
As you can see, the myths about NetBEUI vs. TCP/IP are outdated. There are few compelling reasons for not choosing TCP/IP over NetBEUI.
If you're an experienced IT professional and would like to share your expertise with other Setup32.com readers, why not submit a new tip to our Tech Tips area?
Certification Links