samba - Apr 2010 - Allow Local System user on win2k3 access to Samba share

Greetings,

I have a service running on a Windows Server 2003 box that I want to write to a
Samba share running on Solaris 10. The Samba is not a DC. How can I give access
to the Local System user on the Windows box without making the share writeable
to any other user or system?

Regards,
KB



________________________________
Notice of Confidentiality:

The information contained in this communication is intended solely for the use
of the individual or entity to whom it is addressed and others authorized to
receive it. It may contain confidential or legally privileged information. If
you are not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking any action in reliance on the contents of this
information is strictly prohibited and may be unlawful. If you have received
this communication in error, please notify us immediately by responding to this
email and then delete it from your system.

You could run the service on the windows 2k3 box under another username thats 
allowed to access  samba. As long as the usernames and password match i dont see
any issues.

-----Original Message-----
From: Kevin A. Brown <Kevin.Brown at digicelgroup.com>
Sent: 25 April 2010 10:58 PM
To: samba at lists.samba.org <samba at lists.samba.org>
Subject: [Samba] Allow Local System user on win2k3 access to Samba share

Greetings,

I have a service running on a Windows Server 2003 box that I want to write to a
Samba share running on Solaris 10. The Samba is not a DC. How can I give access
to the Local System user on the Windows box without making the share writeable
to any other user or system?

Regards,
KB



________________________________
Notice of Confidentiality:

The information contained in this communication is intended solely for the use
of the individual or entity to whom it is addressed and others authorized to
receive it. It may contain confidential or legally privileged information. If
you are not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking any action in reliance on the contents of this
information is strictly prohibited and may be unlawful. If you have received
this communication in error, please notify us immediately by responding to this
email and then delete it from your system.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Well the  local system account is not able to log into other machines because it
has  a blank password. Blank password accountsare not allowed network access

-----Original Message-----
From: Kevin A. Brown <Kevin.Brown at digicelgroup.com>
Sent: 26 April 2010 12:30 AM
To: Damien Dye <damien.j.dye at googlemail.com>; samba at lists.samba.org
<samba at lists.samba.org>
Subject: RE: [Samba] Allow Local System user on win2k3 access to Samba share

It's a MS SQL database service. Our standard is to have it run as Local
System.

KB

-----Original Message-----
From: Damien Dye [mailto:damien.j.dye at googlemail.com]
Sent: Sunday, April 25, 2010 6:27 PM
To: Kevin A. Brown; samba at lists.samba.org
Subject: RE: [Samba] Allow Local System user on win2k3 access to Samba share

You could run the service on the windows 2k3 box under another username thats 
allowed to access  samba. As long as the usernames and password match i dont see
any issues.

-----Original Message-----
From: Kevin A. Brown <Kevin.Brown at digicelgroup.com>
Sent: 25 April 2010 10:58 PM
To: samba at lists.samba.org <samba at lists.samba.org>
Subject: [Samba] Allow Local System user on win2k3 access to Samba share

Greetings,

I have a service running on a Windows Server 2003 box that I want to write to a
Samba share running on Solaris 10. The Samba is not a DC. How can I give access
to the Local System user on the Windows box without making the share writeable
to any other user or system?

Regards,
KB


Notice of Confidentiality:

The information contained in this communication is intended solely for the use
of the individual or entity to whom it is addressed and others authorized to
receive it. It may contain confidential or legally privileged information. If
you are not the intended recipient you are hereby notified that any disclosure,
copying, distribution or taking any action in reliance on the contents of this
information is strictly prohibited and may be unlawful. If you have received
this communication in error, please notify us immediately by responding to this
email and then delete it from your system.