I will explain the situation that I had to solve.
I have 3 printers connected to the lan. 1 to my PC & the other 2 to the
Linksys Switch + Printserver combo.
The reason was if I was working late I doid not want other PCs - with
connected printers to be left on just so that I would be able to print to
them. Now if I want to print to a printer connected to the printserver &
want to map a logical printer port to one of these print server connected
printers I have to have NetBeui. The command does not show up othrewise.
Otherwise I have never used any protocol other than TCP/IP for my networking
requirements
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David Brodbeck
Sent: 18 July 2001 01:17
To: '[EMAIL PROTECTED]'
Subject: RE: a Question
If you're running Win9x with TCP/IP as the default protocol, will a network
mapping you do from a DOS window be done via TCP/IP? Seems to me like it
would work just like the mappings made via the GUI, but I've never tried.
If it does there's no really need to use NetBEUI for this.
-----Original Message-----
From: Neal Isaac [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 3:33 PM
To: [EMAIL PROTECTED]
Subject: RE: a Question
Hate to break the news to you Phillip. Netbeui will not work over the
Internet and has virtually gone the way of the DoDo bird. TCP/ip is it.
Try Windows 2000 and the Remote TCP/ip printing feature. Trying Dos
mappings will not work over the Internet unless you can somehow tunnel using
a third party tool.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Pradip Shah
Sent: Tuesday, July 17, 2001 11:27 AM
To: [EMAIL PROTECTED]
Subject: RE: a Question
Here is a little bit from a novice.
I still need "netbeui" whuich stands for netbios extended user interface if
I wish to capture a printer port from a dos window under Windows 9x for
remote printing.
Not withstanding anything available on large systems I still find dos based
multi user accounting applications 100 times more reliable & crash proof
than anyrthing available on windows platform. For small businesses involving
10 to 12 computers it is still a very good solution.
As a rule I have VNC server running on all the machines on a pper ro peer
network so that I can take over control of any machine to change the
configuration/ reboot add remove feature etc.
Pradip Shah.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Glenn Maks
Sent: 17 July 2001 22:35
To: [EMAIL PROTECTED]
Subject: RE: a Question
The history behind NetBEUI dates back to the old IBM LAN Manager days
roughly 1985, Microsoft quickly adopted this transport for their
Windows for Workgroups strategy, this transport was designed to be used in
small LAN environments that would be connected to other
LAN segments or mainframes using a gateway. Here are some of the advantages
of this small compact transport. Very fast in small LANs,
it has good error protection and it uses very little memory. Here are some
of the disadvantages. It is not routable, and the performance
over WANs is very poor, to get around these limitations Novell developed
NetBEUI over IPX for routing, the rest is history. NetBEUI is
still available as a installable transport because there still are small
LANs in operation and NetBEUI fits this role very well. Hope this
answered your question.
Glenn
just curious. why would you want to run any application using netbeui.
-shashi
-----Original Message-----
From: Glenn Maks [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 9:07 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: a Question
originally I was responding to a question asked about remote access between
two computers on the same subnet using NetBEUI, which I
don't thing VNC supports, using software within the scope it was designed
for is always your best bet, that is to say exploiting the designed
functionality which best fits your task at hand. Applying firewall security
and Netmeeting is a whole different discussion all together, and we
all know the only true secure connection is not have one at all, as far as
running everything over a single port, that is what wrappers
do, once again, WebEx wrote their own wrapper to funnel all of the
Netmeeting functionality over Port 80 to allow them to market their
service as a true web based collaboration service. I have to say this,
utilizing the collaboration features within Netmeeting over a VPN
works just fine, I do remote administration to servers in Holland and the UK
from where I sit here in Horsham, Pa with no problems, I also
use VNC to other remote administration tasks as well and that works just
fine, it is sort of like using the right tool for the job, you don't
hammer a nail in using a pair of pliers, and you can't run VNC over NetBEUI.
I have found Netmeeting to be a "virtual" nightmare through a secure
firewall. VNC has some security problems of its own, however routing VNC
could not be simpler or more secure. Kudos for the designers of VNC on this
point. Netmeeting requires multiple outbound and inbound ports including
389, 522 and 1503. These pose a potential security risk to your network.
VNC uses its own port of 5900 that can be customized by terminal. This is
much better than using existing LDAP, TCP and UDP ports as you do not run
the risk of an intruder utilizing these ports to gain entry to other
resources. In my opinion there is no comparison between Netmeeting and VNC.
If anyone does figure out how to route Netmeeting through a single port, I
would be more than interested to know how.
In future releases of VNC I would love to see communication between client
and server be encrypted within the program, rather than using a tunnelling
or third party packet encryption method.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
