Hmm, I thought NetBeui was just NetBios-over-TCP/IP, which is Windows File & Printer Sharing. No? I mean, I don't have anything like SMB specifically setup in my Win2K box, I just use the File & Printer Sharing, and Samba in MacOSX works fine with that.
Hmm, I thought NetBeui was just NetBios-over-TCP/IP, which is Windows File & Printer Sharing. No? I mean, I don't have anything like SMB specifically setup in my Win2K box, I just use the File & Printer Sharing, and Samba in MacOSX works fine with that.
Yes and no. NetBEUI is indeed NetBIOS, but it's the kind that isn't layered on top of TCP/IP (it's "raw" NBF). It's just enough of a networking protocol to make its way around a LAN, not even carrying enough information to cross a router.
Anyway, even Microsoft have deemed NetBEUI obsolete and unsupported since Windows XP, and it was time to get those Windows machines updated to TCP/IP five to ten years ago. There was a NetBEUI stack for OS 9 called MacSOHO, but there really hasn't been much demand for such a thing under OS X.
I wouldn't be so sure about that. Back in the days of Windows for Workgroups 3.1, a group of hackers used NetBEUI to access Microsoft's computers in Redmond.
IIRC NetBEUI is a superset of IBM's original NetBIOS protocol. It is non-routable - it was developed for the old days when LANs used hubs instead of switches. Everything was done with broadcast traffic.
Ah, those were the days... I remember typing LAN Manager commands at the DOS prompt...
But (and I'm less certain of this) I think having NetBEUI/NetBIOS routable via TCP/IP has been available in MS Windows since Win95 - Certainly it was possible on my Win98SE machine.
You've got to understand that "Windows File and Printer Sharing" has not meant the same thing from 95 -> XP. A LAN Manager system will not be able to connect to a modern XP box, at least not without a lot of serious hacking. This is intentional - a number of the early Windows NT network hacks were only possible because of default settings that made its networking backwards-compatible with LAN Manager. Fixing those holes was basically a matter of turning off those compatibility settings (note that these were password-related, not protocol related).