|
Home > Archive > Unix administration > June 2004 > samba communication
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
samba communication
|
|
| yls177 2004-05-24, 2:30 am |
| anyone has an experience in configuring samba such that samba is used
to communicate between a unix
and windows box?
is it just this smb.conf?
thanks
| |
| Øystein Folkvord 2004-05-24, 7:32 am |
| yls177@hotmail.com (yls177) writes:
> anyone has an experience in configuring samba such that samba is used
> to communicate between a unix
>
> and windows box?
Yes. It works very well 
> is it just this smb.conf?
I would suggest that you wisited http://www.amba.org or consulted a howto
(http://www.tldp.org/HOWTO/SMB-HOWTO.html should do)
Good luck!
--
Øystein
| |
| Dave Hinz 2004-05-24, 4:32 pm |
| On 23 May 2004 20:46:54 -0700, yls177 <yls177@hotmail.com> wrote:
> anyone has an experience in configuring samba such that samba is used
> to communicate between a unix and windows box?
Yes, that's what it's for, for file and print sharing. Makes the
unix box look like a Windows server, to windows clients.
> is it just this smb.conf?
Mosty. You might want to look into setting up 'swat', which gives
you a web administration console for samba, and is one of the few
web-based config tools that works intelligently. Prentice Hall
publishes "The official Samba-3 howto and reference guide" which
is excellent and has examples of pretty much any configuration
you might want to try, and then some, or let us know where you get
stuck and we'll give it a shot.
Dave Hinz
| |
| yls177 2004-05-24, 11:31 pm |
| Dave Hinz <DaveMay2004@duck-creek.net> wrote in message news:<2heg77FbvcinU1@uni-berlin.de>...
> On 23 May 2004 20:46:54 -0700, yls177 <yls177@hotmail.com> wrote:
>
> Yes, that's what it's for, for file and print sharing. Makes the
> unix box look like a Windows server, to windows clients.
>
>
> Mosty. You might want to look into setting up 'swat', which gives
> you a web administration console for samba, and is one of the few
> web-based config tools that works intelligently. Prentice Hall
> publishes "The official Samba-3 howto and reference guide" which
> is excellent and has examples of pretty much any configuration
> you might want to try, and then some, or let us know where you get
> stuck and we'll give it a shot.
>
> Dave Hinz
basically, i am a sap basis guy. and needs to shared some filesystems
from unix to windows. so is learning/looking for some help.. i will
post what i have learnt.. later.
cheers
| |
| Dave Hinz 2004-05-25, 4:32 pm |
| On 24 May 2004 19:52:57 -0700, yls177 <yls177@hotmail.com> wrote:
> Dave Hinz <DaveMay2004@duck-creek.net> wrote in message news:<2heg77FbvcinU1@uni-berlin.de>...
>
> basically, i am a sap basis guy. and needs to shared some filesystems
> from unix to windows. so is learning/looking for some help.. i will
> post what i have learnt.. later.
The sharing is pretty basic, authentication is where you need to decide
how it's going to work. I prefer to have the Samba server get
authentication information from the Windows domain, which means
setting security = DOMAIN in the [global] section of the smb.conf.
Depending on if your usernames map to their directory names, you
can even have them go directly to the share, right into their
own directory, instead of being presented with a list of them.
Suggestion - start with no authentication, get the sharing working.
Then, add domain authentication, tell the SMB server who the WINS
server is and what domain it's in, tell the domain controller on
the windows side that your SMB server is allowed to join the
domain, and you should be good to go. This is alot easier
in the Samba3 days than it was earlier.
If you get stuck, post your smb.conf and a description, and
someone here will probably have suggestions.
Dave Hinz
| |
| yls177 2004-05-31, 7:50 am |
| Dave Hinz <DaveMay2004@duck-creek.net> wrote in message news:<2hh6ceFc9n1jU1@uni-berlin.de>...
> On 24 May 2004 19:52:57 -0700, yls177 <yls177@hotmail.com> wrote:
>
>
> The sharing is pretty basic, authentication is where you need to decide
> how it's going to work. I prefer to have the Samba server get
> authentication information from the Windows domain, which means
> setting security = DOMAIN in the [global] section of the smb.conf.
> Depending on if your usernames map to their directory names, you
> can even have them go directly to the share, right into their
> own directory, instead of being presented with a list of them.
>
> Suggestion - start with no authentication, get the sharing working.
> Then, add domain authentication, tell the SMB server who the WINS
> server is and what domain it's in, tell the domain controller on
> the windows side that your SMB server is allowed to join the
> domain, and you should be good to go. This is alot easier
> in the Samba3 days than it was earlier.
>
> If you get stuck, post your smb.conf and a description, and
> someone here will probably have suggestions.
>
> Dave Hinz
i have 2 systems, one is windows W, and one is unix U. so in my unix
system, smb.conf, i have listed the important information that is
needed to communicate between the windows and unix system. basically,
i am on sap and wanted to share /usr/sap/trans.
workgroup = how can i identify this in my windows with my unix entry?
hosts allow =
guest account =
password server = this entry will be the same as the above hosts allow
interfaces = these are the network cards defined in my unix which will
be used for communication
[sapmnt]
path = unix path to share between windows and unix?.. where is the
windows defined?
other list of parameters
basically, the above is needed for my unix smb.conf.
how about tings on the windows side?
thanks
| |
| Dave Hinz 2004-06-02, 4:51 pm |
| On 31 May 2004 01:11:45 -0700, yls177 <yls177@hotmail.com> wrote:
> Dave Hinz <DaveMay2004@duck-creek.net> wrote in message news:<2hh6ceFc9n1jU1@uni-berlin.de>...
>
> i have 2 systems, one is windows W, and one is unix U.
OK,
> workgroup = how can i identify this in my windows with my unix entry?
It's the NT domain that your users authenticate to when they login to their
Windows boxes.
> hosts allow =
> guest account =
> password server = this entry will be the same as the above hosts allow
Start by allowing everything, and use your NT password server for this.
Narrow down hosts after you get the basic connection going.
> interfaces = these are the network cards defined in my unix which will
> be used for communication
Add this once you get it working. Just confuses things right now,
and without knowing your environment I can't make a specific
suggestion.
> [sapmnt]
> path = unix path to share between windows and unix?.. where is the
> windows defined?
Path is the unix path. The windows path will show up as, say, the
L: drive, so the users will mount whatever you're sharing right to L:\
>
> basically, the above is needed for my unix smb.conf.
> how about tings on the windows side?
Go to network neighborhood, select your windows domain, and if you have
Samba up and running, and advertised to it as a server, you'll see your
samba server there, with the shares you've specified.
Getting there?
Dave Hinz
|
|
|
|
|