> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of SEAK, Teng-Fong > > I would like to express my opinion about NetBEUI. > > My company is using some simple printers connected to > our network > through printer servers (one is NetGear something, the other is D-Link > DP-300). These printer servers are invisible to other > computers within the > domain. Official docs all tell us to use IP address and then > use port and > some more fiddlings to add these printers to Windows. It was > a headache to > me because my workmates always ask me how to do.
This is because they don't have a NetBIOS over TCP/IP transport. Most network printing devices do use IP printing, which is what I believe you are describing. > Then, by chance, I found that if I install NetBEUI, the printer > servers are *visible* and installing printers is just a childish game > because the servers are seen like a normal computer sharing > its printer. > So, I install NetBEUI in every computer, even in WinXP and my > headache is > gone. This is because those printer servers speak NetBEUI. In a feeble attempt to make this somewhat OT, let me point out that VNC DOESN'T speak NetBEUI, just TCP/IP. > I've seen in another post that the poster says something about > NetBIOS. I have to admit that I'm just a simple programmer > "promoted" to do > network administration because nobody else in my computer > would like to do > this diry job :( I'm not a network specialist and know nothing about > NetBEUI or whatever. If someone else thinks my problem could > have been > solved in a cleverer method, I'm open-hearted to listen. Thanks. It's not so much a black and white issue on older MS operating systems. If you have a Win9x/ME/NT/2k machine, then yes, this is one way to fix it (more on that later). On a WinXP machine this is the WRONG way to fix it. NetBEUI is unsupported, so it should only be used if absolutely required (as in the earlier example, a DOS client that only speaks NetBEUI). The only problem that was solved in your situation was "convenience". To gain this convenience you have A) added another network transport to the mix and B) installed an unsupported core networking component. Point A means you have extra traffic on the network, and one more thing to go wrong (just wait until you get to the point that half of your machines can't see the other half because some are using NetBEUI and some NetBIOS over TCP/IP). Point B means you have willingly taken the risk for anything Microsoft didn't test. Not really worth it for the sake of "convenience" to me. Since the Original Poster has his issue resolved, this thread is Way, Way OT. If you would like to continue the conversation off-list that wouldn't be an problem. -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
