[lug] Cable and Samba

[John Hernandez]

As an alternative to Windows SMB, you might try setting up an ssh server on 
the linux side and installing WinSCP on their boxes.  It's more secure and 
probably more suitable for low speed / WAN links.  The disadvantage is that 
files cannot generally be edited "in place" from the network location.  They 
instead need to be copied back and forth.  Some users can live with that if 
the files are relatively small.

A more seamless alternative is WebDAV.  It enables remote filesystems over 
HTTP and can be provided by an apache server on your end.  See the apache 
WebDAV module docs and the MS docs for more info.

On Wednesday 23 July 2003 08:05, Gregory Haggquist wrote:
> I have a RedHat 9.0 system connected to the internet via DSL from Qwest. I
> have routed ports 137-139 to the proper locations on my end. Two of my
> users want to access the Samba Server from their Cable Internet connection.
> When they have used a DSL connection to access the Samba Server there are
> no problems, but when they use the same computer with same settings using
> the cable connection they can not access the server name. I contacted the
> Cable company and they state only port 80 is open, ports 137-139 are closed
> on their end. I am assuming this is the problem, is there any way around
> this issue other than changing ISPs.
>
> Regards,
>
> Greg Haggquist
> gwh at traptek.com
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug

-- 

 |  John Hernandez - NOAA Boulder NOC - 303-497-6392
 |  Mailstop R/OM62. 325 Broadway, Boulder, CO 80305
 |  PGP Public Key ID: 586A7E23