"John R Weiss" said:
I've used NETBEUI extensively in mixed-OS environments, starting with WFWG
3.11/Win95 (with Novell and a Token-ring net!) and going all the way to a XP
Pro/XP Home LAN. Fortunately, XP Pro is more well behaved than the previous Win
versions, so I have not had to use NETBEUI on my XP Pro/Win2K LAN.
In none of those cases were firewalls the culprit, because there were no
software firewalls at all involved during initial installations, and only one
instance of a dedicated hardware firewall (behind which the entire LAN existed).
I agree that NETBEUI as a "universal antidote" SHOULD not be required, but the
fact is that it is considered as such by many people.
I understand using NetBEUI in the days of WFWG 3.11, which didn't
include TCP/IP in the original release. Microsoft provided TCP/IP
later as a free download.
I've set up lots of mixed-OS environments since then, and TCP/IP has
always worked right out of the box. I remove NetBEUI when I find it
on a client's network.
So here's a summary of my view on the subject:
1. It's OK to use NetBEUI, but you won't be able to do it in Vista.
2. If you use it, un-bind File and Printer Sharing from TCP/IP.
3. NetBEUI is never necessary in a typical Windows network.
4. There's some unusual hardware, like Malcolm mentioned, that
requires it, at least during initial setup.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com