Do you have a question? Post it now! No Registration Necessary. Now with pictures!
December 23, 2003, 5:03 pm
rate this thread
Samba is configured to utilize port 445 for *direct-hosted smb* ( no
Test client is Win2K box utilizing VanDyke Entunnel.
Samba works as expected, except for tunneled ssh.
Port 445 is forwarded to localhost 445.
When attempting to mount share utilizing net use <drive>:
184.108.40.206\<share> /USER:<workgroup>\<user> <password> via the Win2K
Command Prompt, net use complains that the user name or password is
invalid. When utilizing the actual server address in lieu of localhost,
Configuring Samba to listen to another port (20445) and forwarding to
localhost:20445 produces similar failures. A Fedora netstat check
indicates Samba is listening on 127.0.0.1:445
Could the issue with ssh be the long delay that Samba takes ( 'bout 20
seconds ) to authenticate?
Note that SSH tunneling is working properly on the test client and
server as I currently utilize it for squid, pop3, smtp, jabber and cups.
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum