🚀 go-pugleaf

"BPC" <theconsumer@comcast.net> wrote in message
news:%ibU8.513517$%y.34681440@bin4.nnrp.aus1.giganews.com...
> Thanks for all the quick responses!
>
> WinXP is my operating system.

    Windows 2000 and Windows XP DO NOT require any form of netbios.
    Although NetBt (Netbios over TCP/IP) is enabled by default.
    All other M$ network OS's require some form of netbios.
    Netbeui, is a fairly old networking protocol that is optimal for small
    workgroups but degrades rapidly with increased network size.
    It is basically Microsoft's form of Netbios directly over ethernet.
    NetBt is Netbios over TCP/IP. Until WIndows 2000 all M$ OS's required
    some form of netbios.
    Since virtually everything needs to connect to the internet anymore
    and you must have TCP/IP to connect to the internet, Netbeui is pretty
    much defunct.
    Netbeui is unroutable and further does nto run over TCP/IP
    therefore you do not need a firewall to block netbeui.
    NetBt is a very bad thing to expose to the internet. If you must have
    it on you net then you better block it at your firewall.
    Some very old and odd print servers actually worked over netbeui.
    I have not heard of anything made recently that requires netbeui.
    I have alot of linksys gear and it is all TCP/IP, but I do nto have
    any of there print servers.
    Setting up a TCP/IP print server under Windows XP should be
    fairly simple. You select the printer that is attached at the far end
    when asked what port it is on indicate that it is a network port.
    The possibility exists that XP will actually find it for you, but in
    the event that it does not you specify the port name (whatever you want)
    and the IP address. Configuring the IP address for the print server
    is either done manualy via telnet or a web browser (most linksys stuff I
know
    is configured via a browser). You can "Temporarily" asign a widget an IP
    address accessible from your machine only using the arp command -
    arp -s an.unused.local.ipaddress the-widgets-mac-address
    This will allow you to access it via a browser or telnet so that you
    can tell it what address to permanently use. If you have a DHCP server
    creating a DHCP reservation for the widget is the best way to go,
otherwise
    use the web configuration to assign the widget a permanent IP.
    Use that IP when you install the network printer port.
    The last possible issue is whether the widget speaks lpr or raw sockets.
    Most newer widgets speak raw sockets and that is the easiest to setup.
    To configure a widget to talk lpr generally requires knowing the print
queue
    name on the widget - generally set using the browser configuration.






>
> "Iceman" <c0ld0n3@yahoo.com> wrote in message
> news:47f2iugq33jsp6b4vllsfejr8ffhdf14lo@4ax.com...
> > On Tue, 02 Jul 2002 05:30:53 GMT, "Berk S. Daemon"
> > <someone@somewhere.com> wrote:
> >
> > >
> > >"BPC" <theconsumer@comcast.net> wrote in message
> > >news:jyaU8.565721$Oa1.36076408@bin8.nnrp.aus1.giganews.com...
> > >> After spending the majority of my evening on the phone with
incompetent
> > >> Linksys support, the last one told me I need to find "netbeiu" (his
> > >> spelling) and learn how to install it. He says I need this to make
the
> > >> Linksys wireless print server work with their wireless router. He
says
> > >once
> > >> I install this magical file everything will work perfectly.
> > >>
> > >> Here's the problem: He could not tell me what the file is, where to
> find
> > >it
> > >> or how to install it. He just mentioned this file then told me he
> couldn't
> > >> stay on the phone with me any longer! He was the 3rd Linksys support
> > >person
> > >> to mention this file and offer no suggestions on how to find it. I'm
> > >fairly
> > >> computer savvy, (I set up the rest of the wireless network) so could
> > >someone
> > >> point me in the direction of this magical end-all file to solve my
> > >wireless
> > >> print server issue?
> > >>
> > >> Thanks in advance. It's good to know there is someone out there who
is
> > >> willing (and unlike Linksys support, able) to help!
> > >>
> > >> BPC
> > >
> > >If they're product(s) require NetBEUI or any form of NetBIOS, then if I
> were
> > >you I would immediatly return the product with some ass wipe in the box
> to
> > >the manufacturer and tell them that's what you think of it!
> > >
> >
> > You need a form of NetBios on any windows network in order to
> > communicate with other devices and or computers. Your firewall should
> > block it from getting out on to the NET.
> >
> > NetBeui is faster than TCP/IP and is a simplified way of communicating
> > on a local lan for small workgroups, it is brainless, no config needed
> > and will not run on the internet. (to keep your internet running fast
> > on a dial up make sure that netbeui and ipx/ is not enabled for the
> > modem connection)
> >
> > If you do not like either of these protocols the I suggest you run a
> > *nix box and stay away from Samba
>
>