Comments on: Secure Windows File Sharing (Samba) over the Internet without Putty. https://46palermo.com/blog/secure-samba-windows-file-sharing-without-putty/ Magento developer and CMS expert Wed, 09 Jul 2014 18:41:17 +0000 hourly 1 https://wordpress.org/?v=3.0 By: Damian Gaweda https://46palermo.com/blog/secure-samba-windows-file-sharing-without-putty/#comment-56 Damian Gaweda Fri, 19 Dec 2008 22:11:36 +0000 https://46palermo.com/nicer-samba-windows-file-sharing-over-ssh/#comment-56 I think it's an issue introduced by microsoft's security update KB942624. I'm experiencing the 'permission denied' problem on my Vista. I haven't found a solution for this so I'm using SftpDrive for the time being. I think it’s an issue introduced by microsoft’s security update KB942624. I’m experiencing the ‘permission denied’ problem on my Vista.

I haven’t found a solution for this so I’m using SftpDrive for the time being.

]]> By: Thomas https://46palermo.com/blog/secure-samba-windows-file-sharing-without-putty/#comment-55 Thomas Fri, 19 Dec 2008 21:31:56 +0000 https://46palermo.com/nicer-samba-windows-file-sharing-over-ssh/#comment-55 Hi! I'm writing here even though it actually belongs to the article which describes setting up the loopback interface. (not possible to leave a reply there - "wrong captcha text" 10 times) No success in my case with the forwarding; I have WinXP SP2, have installed the update mentioned in the article, but Windows says "... cannot access this share. Check spelling etc" when typing "\\10.0.0.1\myshare" into the address bar. Also using "Connect to net drive..." it does not work. The samba server is running, the loopback interface and the pure forwarding part work as well (as shown in the status messages in myentunnel when doing a raw telnet connect to 10.0.0.1:139), but windows does not seem to initiate a connection on 139, rather on 445 first. Any ideas? Port 445? (Tried, but yielding a "permission denied" when trying to establish the tunnel) In Putty: I assume you have to choose the option "Local" when adding the forward, i.e. having an equivalent of "-L 10.0.0.1:139:127.0.0.1:139". Hi!

I’m writing here even though it actually belongs to the article which describes setting up the loopback interface. (not possible to leave a reply there – “wrong captcha text” 10 times)

No success in my case with the forwarding; I have WinXP SP2, have installed the update mentioned in the article, but Windows says “… cannot access this share. Check spelling etc” when typing “\\10.0.0.1\myshare” into the address bar. Also using “Connect to net drive…” it does not work.

The samba server is running, the loopback interface and the pure forwarding part work as well (as shown in the status messages in myentunnel when doing a raw telnet connect to 10.0.0.1:139), but windows does not seem to initiate a connection on 139, rather on 445 first.

Any ideas?

Port 445? (Tried, but yielding a “permission denied” when trying to establish the tunnel)

In Putty: I assume you have to choose the option “Local” when adding the forward, i.e. having an equivalent of “-L 10.0.0.1:139:127.0.0.1:139″.

]]>