TCP/IP alone or add other protocols (eg NetBeui)

[RalphArch]

Can someone please address whether it makes any sense to add or use for example NetBeui on a home network when I have a working setup with TCP/IP? I see others are using it and I am curious why.

Current setup is Client for MS networks. For internet a Winproxy server with one-way cable modem (telco return). All computers have TCP/IP; most have IPX (so my kids can play a lan game with Red Alert 2 - IPX goes out after that is over) and all using Win98 or WinMe with an occasional boot to Linux.

[DVNT1]

Because Microsoft's File & Print Sharing occasionally has trouble on IP alone, NETBEUI is often added.

It is also helpful to reduce chances of Internet intrusions into your File Shares if you bind Sharing to a protocol other than IP.

As a side note, IPX is considered a faster protocol than IP. In my home LAN I run IP & IPX (802.2).

[RalphArch]

Interesting. I don't have file and print sharing bound on either the cable modem nic nor the dial up connection; and WinProxy is configured as a firewall for the TCP/IP - but I guess you are saying there's more security still using Netbeui for file and print sharing? And maybe those occasional delays to display files in other computers will be shorter.

And even if I didn't choose to add NetBeui I should enable sharing on the IPX in addition to the TCP/IP (needs to stay bound for Linux)

Any downsides to proceding with these additional protocols?

[DVNT1]

but I guess you are saying there's more security still using Netbeui for file and print sharing?

Mostly just helps to reduce the impact of some mistakes, not really more secure otherwise.


And maybe those occasional delays to display files in other computers will be shorter.

Maybe.


And even if I didn't choose to add NetBeui I should enable sharing on the IPX in addition to the TCP/IP (needs to stay bound for Linux)

Not sure what other choices you have in that case, but I don't know of a noticeable negative in doing so.


Any downsides to proceeding with these additional protocols?

More overhead, but in small LANs the impact is so minor I've never noticed it.

[eicken]

Try this site may answer some of your questions. http://grc.com/su-bondage.htm

[RalphArch]

Thanks - quite a site and great details - Guess I should rearrange my network

[shadow]

It's always best to unbind the TCP/IP from your LAN and use NetBEUI on the LAN. It's light, very fast and non-routeable which makes it a perfect choice for speed and security.

[DVNT1]

shadow, the worst thing about unbinding IP from the LAN, many programs and games require IP to communicate.

[shadow]

I gues it depends on your needs as you say. I do not have tcp/ip bound to file & print sharing on my LAN, I use NetBEUI internally and all computers do communicate to the internet but with their own ip#'s. It has always worked well for me, any communication between computers works just fine.