samba - Sep 2007 - installing Samba as non-root user at work - please help.

Hi,

I've recently started at a new company that doesn't have a system in
place
to map my Linux home directory within Windows.  I have my own Linux box (a
recent Redhat install), and my own Windows XP PC.  I will get no help from a
system admin here, so my only option is to try installing Samba myself on my
Linux box.  To my surprise, I've found little or no information on
installing Samba as a non-root user.

All I wish to achieve is being able to map my Linux home directory on my
Windows PC.

We are on a Windows domain called "ENGINEERING".  It's on "
engineering.company.com" (where company is my real company's name).  I
have
a username, lets say "userpc", and a password, "passpc", on
my PC.  My linux
machine is also part of the "engineering.company.com" network, but I
use a
different username, "userlinux", and password, "passlinux".

I had no problems doing a local Samba install by changing the 'prefix'
during configure and install.  It's at that point that I am lost what to do.

I have started by editing the smb.conf file, and allow host access only by
the ip address of my windows box.  I also attempt to use a username map
file, since I'm using different usernames on my Windows PC and my Linux
box.  It's not entirely clear to me what to do with regards to the
workgroup/domain.  In some ways it'd be nice if I can just implement SMB
over TCP/IP and not worry about NT-Domains or Workgroups.

Afterall, all I am trying to accomplish is to map my Linux home directory to
only one other computer, my Windows PC, on the same network.  It'd be nice
if I could just kick off an smb server on my Linux box, and have my windows
box map the home directory by specifying the ip address of the linux box and
correct port.  But perhaps such a setup, even for my simple scenario, is not
possible with Samba.

Speaking of ports, I specify ports of 1445 and 1139 for smdb, since I cannot
use a port below 1024 without having root access.  Similarly, I attempt to
use higher port when I start nmdb.

I try to start both the smdb and nmdb daemons, but even that doesn't appear
to work correctly, as it appears that a non-root, local install is not truly
supported.  At least not with more tinkering.
>From my log.smbd:
[2007/09/19 17:00:16, 0] smbd/server.c:main(944)
  smbd version 3.0.26a started.
  Copyright Andrew Tridgell and the Samba Team 1992-2007
[2007/09/19 17:00:16, 0] lib/debug.c:reopen_logs(625)
  Unable to open new log file /usr/local/samba/var/log.smbd: No such file or
directory
[2007/09/19 17:00:16, 0] lib/debug.c:reopen_logs(625)
  Unable to open new log file /usr/local/samba/var/log.smbd: No such file or
directory
[2007/09/19 17:00:16, 1] smbd/files.c:file_init(193)
  file_init: Information only: requested 10000 open files, 1004 are
available.
[2007/09/19 17:00:16, 0] auth/auth_util.c:create_builtin_administrators(792)
  create_builtin_administrators: Failed to create Administrators
[2007/09/19 17:00:16, 0] auth/auth_util.c:create_builtin_users(758)
  create_builtin_users: Failed to create Users
>From my log.nmbd:
[2007/09/19 16:44:02, 0] nmbd/nmbd.c:main(697)
  Netbios nameserver version 3.0.26a started.
  Copyright Andrew Tridgell and the Samba Team 1992-2007
[2007/09/19 16:44:02, 0] lib/util_sock.c:set_socket_options(261)
  Failed to set socket option SO_BROADCAST (Error Bad file descriptor)
[2007/09/19 16:44:02, 0] nmbd/nmbd_subnetdb.c:make_subnet(107)
nmbd_subnetdb:make_subnet()
  Failed to open dgram socket on interface 10.30.102.110 for port 138.
Error was Permission denied
[2007/09/19 16:44:02, 0] nmbd/nmbd.c:main(771)
  ERROR: Failed when creating subnet lists. Exiting.


And even once I get these daemons up and running on my Linux box, it's not
clear to me what I need to do on the Windows side to establish a
connection.  What port would I use, since I am not using the standard ports?

Given the information I've provided, and knowing that I do not have root
access, can anyone provide any information to at least steer me in the right
direction?  I greatly appreciate your help.

Thank you,
Ben

Hi,
> Speaking of ports, I specify ports of 1445 and 1139 for smdb, since I
cannot
> use a port below 1024 without having root access.  Similarly, I attempt to
> use higher port when I start nmdb.
Even if this would work, you would be stuck with the problem  of
convincing your windows system to talk to these ports.
> Given the information I've provided, and knowing that I do not have
root
> access, can anyone provide any information to at least steer me in the
right
> direction?  I greatly appreciate your help.
Without root access you can pretty much give up on installing samba. If
your linux box allows ssh access, you might want to try something like
winscp to transfer your files from and to windows.

Regards,
Wolfgang Ratzka

<spamreceptacle@gmail.com> wrote in message 
news:1140a0ee0709211751o16c5b45s62b8422c37be4ea7@mail.gmail.com...
> All I wish to achieve is being able to map my Linux home directory on my
> Windows PC.
>
>
> Speaking of ports, I specify ports of 1445 and 1139 for smdb, since I
cannot
> use a port below 1024 without having root access.
Unless you want to do something fancy like SSH port tunneling, that won't
work.
The Windows CIFS/SMB client will only connect to port 139 and port 445.

I can't see a way to map a drive letter from your Windows box to your Linux
box
without cooperation from someone with root access on the Linux box.  If your 
Linux box supports SSH access, you could use a tool like WinSCP on your Windows 
box to copy files to and from your Linux box.

Hi,

I was able to actually get this to work!  I successfully mapped my Linux
home directory within Windows on a non-root smb install.

I was able to get smbd to run OK with the non-standard ports.

I then needed to do ssh tunneling to forward port 139 on a Windows Loopback
Network device to the non-standard port of 1139 on my Linux box.  I used a
method similar to this.

http://smithii.com/map_a_network_drive_over_ssh_in_windows

I'm now in business.

My next question is, can I have other users in my group map their own home
directories by using my smbd server that's running on my Linux box?

I'm assuming I'd need to add the users to the smbpasswd file.

But how does that all work?  If I were to add another user and choose my own
password for that user, I'm assuming I can't just map his home drive and
have full privileges to it (which is not what I want).  Does the smbpasswd
have to match the Linux password for the user?  If not, wow else would it
grant proper access to files, if it would seem I can masquerade as this user
and use an smb password that is different from his own Linux password.

Thanks

On 9/21/07, spamreceptacle@gmail.com <spamreceptacle@gmail.com>
wrote:
>
> Hi,
>
> I've recently started at a new company that doesn't have a system
in place
> to map my Linux home directory within Windows.  I have my own Linux box (a
> recent Redhat install), and my own Windows XP PC.  I will get no help from
a
> system admin here, so my only option is to try installing Samba myself on
my
> Linux box.  To my surprise, I've found little or no information on
> installing Samba as a non-root user.
>
> All I wish to achieve is being able to map my Linux home directory on my
> Windows PC.
>
> We are on a Windows domain called "ENGINEERING".  It's on
"engineering.company.com
> " (where company is my real company's name).  I have a username,
lets say
> "userpc", and a password, "passpc", on my PC.  My linux
machine is also part
> of the " engineering.company.com" network, but I use a different
username,
> "userlinux", and password, "passlinux".
>
> I had no problems doing a local Samba install by changing the
'prefix'
> during configure and install.  It's at that point that I am lost what
to do.
>
>
> I have started by editing the smb.conf file, and allow host access only by
> the ip address of my windows box.  I also attempt to use a username map
> file, since I'm using different usernames on my Windows PC and my Linux
> box.  It's not entirely clear to me what to do with regards to the
> workgroup/domain.  In some ways it'd be nice if I can just implement
SMB
> over TCP/IP and not worry about NT-Domains or Workgroups.
>
> Afterall, all I am trying to accomplish is to map my Linux home directory
> to only one other computer, my Windows PC, on the same network.  It'd
be
> nice if I could just kick off an smb server on my Linux box, and have my
> windows box map the home directory by specifying the ip address of the
linux
> box and correct port.  But perhaps such a setup, even for my simple
> scenario, is not possible with Samba.
>
> Speaking of ports, I specify ports of 1445 and 1139 for smdb, since I
> cannot use a port below 1024 without having root access.  Similarly, I
> attempt to use higher port when I start nmdb.
>
> I try to start both the smdb and nmdb daemons, but even that doesn't
> appear to work correctly, as it appears that a non-root, local install is
> not truly supported.  At least not with more tinkering.
>
> From my log.smbd:
>
> [2007/09/19 17:00:16, 0] smbd/server.c:main(944)
>   smbd version 3.0.26a started.
>   Copyright Andrew Tridgell and the Samba Team 1992-2007
> [2007/09/19 17:00:16, 0] lib/debug.c:reopen_logs(625)
>   Unable to open new log file /usr/local/samba/var/log.smbd: No such file
> or directory
> [2007/09/19 17:00:16, 0] lib/debug.c:reopen_logs(625)
>   Unable to open new log file /usr/local/samba/var/log.smbd: No such file
> or directory
> [2007/09/19 17:00:16, 1] smbd/files.c:file_init(193)
>   file_init: Information only: requested 10000 open files, 1004 are
> available.
> [2007/09/19 17:00:16, 0]
> auth/auth_util.c:create_builtin_administrators(792)
>   create_builtin_administrators: Failed to create Administrators
> [2007/09/19 17:00:16, 0] auth/auth_util.c:create_builtin_users(758)
>   create_builtin_users: Failed to create Users
>
> From my log.nmbd:
>
> [2007/09/19 16:44:02, 0] nmbd/nmbd.c:main(697)
>   Netbios nameserver version 3.0.26a started.
>   Copyright Andrew Tridgell and the Samba Team 1992-2007
> [2007/09/19 16:44:02, 0] lib/util_sock.c:set_socket_options(261)
>   Failed to set socket option SO_BROADCAST (Error Bad file descriptor)
> [2007/09/19 16:44:02, 0] nmbd/nmbd_subnetdb.c:make_subnet(107)
> nmbd_subnetdb:make_subnet()
>   Failed to open dgram socket on interface 10.30.102.110 for port 138.
> Error was Permission denied
> [2007/09/19 16:44:02, 0] nmbd/nmbd.c:main(771)
>   ERROR: Failed when creating subnet lists. Exiting.
>
>
> And even once I get these daemons up and running on my Linux box, it's
not
> clear to me what I need to do on the Windows side to establish a
> connection.  What port would I use, since I am not using the standard
ports?
>
>
> Given the information I've provided, and knowing that I do not have
root
> access, can anyone provide any information to at least steer me in the
right
> direction?  I greatly appreciate your help.
>
> Thank you,
> Ben
>
>
>
>
>
>
>
>