Windows

NetBEUI can't be routed, so if wins goes down, no one will be able to see anything outside thier particular segment. If wins does go down, you should still be able to communicate with tcp/ip until you can get it back up.

Short of it being a "backup" in case WINS goes down, there isn't much of use for it unless your environment isn't routed.

There is no reason not to remove it, especially if you have a network larger than about ten computers. Without WINS the computers just resort to broadcasts for names. This does slow the resolution some and adds traffic but it shouldn't be worse thannetbeui only.

If bandwidth is not really a problem then keep NetBEUI for:
1.) Failsafe
2.) Much faster on internal(non routed) networks than TCP/IP.
3.) Direct communication with SMB Services as opposed to TCP/IP (That's what makes it faster than TCP/IP in thefirst place)
4.) Practically no overheads (which is a good argument to hold on to it)

Yes, tell your Network Manager that NETBEUI is the most fastest, most reliable and most efficient protocol that works well in small LANs, with VERY LITTLE OVERHEAD.
The drawback is it is not routable as everyone here says, and it is not intended for WAN use.
Thats your best argument there.

Jun