Re: new user cannot access UNIX share

In comp.unix.admin David Wurdeman <david.wurdeman@xxxxxxxxxxxxxxx>:

"Dave Hinz" <DaveHinz@xxxxxxxxx> wrote in message
news:5crlvoF31q46sU1@xxxxxxxxxxxxxxxxxxxxx
On Thu, 7 Jun 2007 15:45:30 -0500, David Wurdeman
<david.wurdeman@xxxxxxxxxxxxxxx> wrote:
First just let me say that I have been mostly Microsoft the past 10
years,
but have now inherited a UNIX server at my new job. I have had some
basic
UNIX experience, but not enough to fix the following problem:
*newly created user cannot access a share on the UNIX server*

Hi David, welcome to the group. You're off to a great start. Let's dig
into this & see what we've got.

Background:
We have a shared directory on our UNIX server that holds the databases
for
an in-house application. Recently we had a new user enter the company.
I
got onto the UNIX server (the graphical based screen--of course!) I
found
the utility to create a new user.

OK, it'd maybe help to know the flavor of Unix, sometimes not but
usually it does.

THEN--I went to utility installed on my pc called Vision FS Profile Edit.
I
was told by the UNIX guy who was adminstrating the server that "you need
to
use this to give access to the shared folder". I got into the utility,
found the shared folder, went to the properties and found the new user I
created, and gave him rights to the share.

Sounds good so far...

However, when I login to the new user's pc, go to network neighborhood--I
can see the Unix share but when I try to connect using the created Unix
username and password I get an "access denied".

OK so it sounds like you have a Samba server running on the Unix box.
And for some reason this user can see it but not authenticate. Are they
using their Unix password or their Windows password? What are his
coworkers using to authenticate there? It's highly configurable if
you're running Samba so the best bet will involve finding out whose
setup works, and observing how they do it.

I have tried logging-in on the UNIX console using the new user's name and
password, and it lets me in. So UNIX recognizes the account.

OK, it's quite possible that there is a username mapping that needs to
be done to tie his Windows login to his Unix login, so Samba knows that
"jblow123" in the Windows domain is equivalent to "joeblow" in the Unix
world.

Can someone tell me what I might be doing wrong? Is there an additional
step
in the "Vision FS Profile Editor" that I need to do? Is there something
I
need to to from the console?

Look for something like "account name mapping". I've never seen Vision
FS Profile Editor, details on OS would be helpful if what I've said
doesn't help.

The system we are running is SCO UNIX (hope I got that right).

Lucky you ;)

I very truly appreciate any help/advice. Feel free to ask more questions
if
I am not clear on what I need to do.

You're off to a good start, let us know what you find based on the
above.

Dave Hinz


Thanks so much for the reply--it is a real relief to have someone help me on
this problem 'cause it has me stumped!

When I get to the console login screen it says :"SCO Openserver Release 5"

The in-house program we are running on the users Windows workstations
requires a Windows drive letter mapped to the directory on the UNIX server.
As far as setting-up previous users, I have gone into Network
Neighborhood-->Tools-->map network drive. I then choose the drive letter I
need. However, since our users have different accounts for the UNIX server,
I choose the option to "connect using a different user name". I then enter
their UNIX username and password.

This has worked fine for the existing UNIX user accounts. However when I
follow this procedure for the new user, it comes back with the "access
denied" error.

I am thinking I need to ask the question as to how UNIX controls access to
folders on a server when accessed from across a network.

It seems it isn't unix but a samba server running on the SCO box
controlling access. You almost certainly just need to add the
user to the smb.conf or how it is called on SCO, exactly where
you find the other users who have access or perhaps just add the
user to a group allowing access with standard unix tools, such as
'usermod'. Get a shell on the unix box and enter:

'id <username_that_can_access_share>'

Without ' and replacing <username_that_can_access_share> with a
working user name.

You should get something like:

$ id root
uid=0(root) gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)

Now do the same for the new user and check for differences after
"groups="

Either one might be the solution. I am sorry I do not know any of
the tools you mention, dislike thing not really portable.

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@xxxxxxxxxx | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 268: Neutrino overload on the nameserver
.

Relevant Pages

  • Re: Network Printing...Finally
    ... You do not need Print Services for Unix running on the Windows machine to ... service simply allows Windows to act as an LPR server. ... Samba is not the best way to go! ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Problem setting up NFS on Ubuntu
    ... >>> forgotten most of the litle I knew about commercial Unix, ... >> alike on the FS and use samba to export it to doze clients. ... >>> I have also discovered how to login to the gui as root, ... >>> which should make windows client access easier, and does work also from RISC ...
    (comp.os.linux.setup)
  • Re: version control using subversion
    ... Some applets that help designers get in ... If you want to cross boundary between unix and windows, you may find complications and need system administrators help anyway... ... There is in Samba a way to send winpopup notifications like those defined in windows for workgroups. ...
    (comp.cad.cadence)
  • Re: Next project, C programming problem.
    ... >> But while it may be able to tell what a windows file is (actually, ... >> file formats) there is no way it can know what a file on a Unix ... SAMBA should not be converting files. ... > good time saver. ...
    (comp.os.vms)
  • Re: With netbios over tcp disfunctional whats left?
    ... Samba works perfectly here too. ... linux to windows, its windows to windows where trouble begins. ... Just reading some of the docu about, it appears something in the unix ... One problem machine running winxp pro sp/2 doesn't showup in Network ...
    (microsoft.public.windowsxp.general)