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.
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.
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.
> -----Original Message-----
> From: Steve Bostedor [mailto:[EMAIL PROTECTED]
> Sent: mercredi 19 mars 2003 23:14
> To: William Hooper; [EMAIL PROTECTED]
> Subject: RE: Problem connecting with net name on Windows XP
>
>
> I don't want to take this off-line because the rest of the
> community will miss what I am saying and it is an important
> tip that could help a lot of people out. If for some odd
> reason, I'm off my rocker and I am spewing non-sense into the
> list, the worst that will happen is that someone will have
> one extra protocol in their list. :)
>
> NetBEUI resolves names on a network by broadcasting and
> receiving those broadcasts. You are correct, NetBEUI is not
> directly required by VNC, but if you wish to connect to
> another computer by using the name and you don't have a DNS
> server and do not wish to use a hosts file, NETBEUI is for you.
>
> It appears that you are confusing the role of NETBIOS with
> NETBEUI. You mentioned that NETBEUI is on another transport
> than TCP/IP but in fact, NETBIOS is the transport layer
> protocol and NETBEUI is at the network layer. NetBIOS is
> concerned with setting up sessions and transporting the data.
> NETBEUI is concerned with things like name resolution and
> network mapping.
>
> Microsoft is dropping NETBEUI in order to push everybody to
> their Active Directory. It still works great for home LAN's
> as a quick and dirty name resolution protocol. I do have
> direct experience mixing Win9x and XP and properly configured
> NETBEUI is, in fact, required for them to see each other.
> There is a knowledge base article on it, but I don't have
> time to go dig it up right now. I hope that everybody
> understands why I suggest to install NETBEUI, now.
>
> - Steve Bostedor
> http://www.vncscan.com
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
