is SSH with win 2000 really a practical solution for the
'simple' task of file xferring when ftp is an available
option, or am i missing something?
----- Original Message -----
From: "Lyle" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 16, 2001 8:08 PM
Subject: RE: mapping a remote drive
> Netbeui is not routable and won't work through any
router.(Netbios riding on
> top of TCP/IP or IPX/SPX is different)
>
> Yes that is one way to connect via VNC to various machines
behind a
> firewall. And FTP, HTTP and such are fairly hard coded,
but they can be
> moved to'non-standard' ports. FTP would probably be the
hardest as it would
> take some playing on the client end. HTTP is easy to
'move' on the client
> end for special machine.
>
> But the suggestion for SSH makes the most sense to me.
>
> -----Original Message-----
> From: David Rothman [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 16, 2001 6:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: mapping a remote drive
>
>
> ok fair enuf. clearly if u r not behind a router and/or
> firewall, u shud only enable print/file sharing if you've
> done the 'unbinding dance' and only permit the sharing to
be
> done with something other than tcp/ip (namely netbeui).
>
> but let me see if i understand you/this correctly:
>
> with vnc, to let the outside world connect to various
> machines behind a router, u would forward say port 5800 to
> 192.168.0.1 and 5801 to 192.168.0.2 and so on. IF one
> wanted to use the mapped drive idea, and if that entails
> opening port 138, how would u go about assigning the other
> machines in the LAN? IOW, i doubt that its 138 for
> 192.168.0.1 and 139 to 192.168.0.2 etc.
>
> lastly, if one is using vnc, is ftp the generally accepted
> way to handle file xfer? or should i be exploring win
2000
> vpn (or something else)? thanks...
>
>
>
>
> ----- Original Message -----
> From: "Lyle" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, February 16, 2001 4:05 PM
> Subject: RE: mapping a remote drive
>
>
> > I see thousands more scans against port 138 than I do
> against port 5800 or
> > 5900. Yes, if you limit your exposure, that's true and
> you absolutely have
> > to have good passwords that are changed often. And you
> have to make
> > absolutely sure that you haven't forgotten to patch
> something that leaves
> > port 138 vulnerable to a known hack.
> >
> > Just because port 138 is well known, it scares me to
open
> it more than VNC.
> > There are lots more attempts against port 138 than VNC.
> >
> > Lyle
> >
> > -----Original Message-----
> > From: David Rothman [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, February 16, 2001 2:49 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: mapping a remote drive
> >
> >
> > yes..clearly it means opening a port, but with a smart
> > password, is it any different that opening a port for
VNC
> or
> > ftp for that matter?
> >
> > in fact, if u only open one drive or one directory to
the
> > world, might it not be even safer?
> >
> > ----- Original Message -----
> > From: "Lyle" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, February 16, 2001 3:27 PM
> > Subject: RE: mapping a remote drive
> >
> >
> > > That means opening up netbios to the world(port 138).
> NOT
> > a smart idea.
> > >
> > > -----Original Message-----
> > > From: David Rothman [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, February 16, 2001 9:02 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: mapping a remote drive
> > >
> > >
> > > with vnc, when you want to talk to machine(x) which is
> > > behind a router, the router needs to be set to forward
> > port
> > > 590x to machine(x).
> > >
> > > presumably this is also true with mapping a drive
(using
> > win
> > > 2000 pro)
> > > on a machine behind a router, but the syntax is not
> > obvious
> > > to
> > > me. i would think it's an argument to the
> \\server\share
> > > syntax. does anyone know what it is? thanks..
> >
>
> ----------------------------------------------------------
> > -----------
> > > 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
---------------------------------------------------------------------
