On 9/13/11 2:22 PM, frosty wrote:
Update: Got it working, but not via a letter-mapped
drive. Got the \\computername\sharename\directoryname
version to work, after (1) adding a new User on the
Win server; (2) Logging into Windose as that User;
(3) Going to Control Panel > User Accounts, selecting
the new user, and clicking "Manage my Network Passwords";
(4) Clicking the "Add" button to add a password for a
User on the Mac (which was already set up on the Mac);
(5) In Computer Management > Services and Applications >
Services, double-clicking "UniData Database Services 7.2"
and clicking the "Logon" tab; (7) Changing the radio
button to "This Account:" (8) Inserting the new User
from step 1 and the password; (9) Restarting Unidata
Service. A few restarts here and there, some wailing
and gnashing of teeth.

Thanks to all who contributed!

--
frosty

Exactly. Net USE will show the mappings currently defined.

I find the full UNC path works better than the sharename. Not sure how
well that will work across to a Mac. IIRC you can setup a mapping
using !net use... that will work - but only for that session. You may
be able to put it into the users environment to make it consistent
(not sure how). Of course, anything that ends up prompting for user/
password will fail as the UDT session can't interpret it. It's easiest
if the user you logged into UD with has the proper permissions on the
remote system as they are used when connecting.

Good luck.
Colin
Calgary, Canada

On Sep 14, 10:10*am, frosty wrote:

On 9/14/11 3:16 PM, frosty wrote:
Update to the update:

It turns out that running the uniData service as the
privileged User is not necessary; only logging into
uniData as that User. So ignore steps 5--9. And add
"Log into uniData as the privileged User".


--
frosty

On 9/14/11 3:35 PM, Colin wrote:
"!net USE" returns "There are no entries in the list."
Which is not a problem as I'm not using the letter-
mapped drive.

I find the same, thanks.

Works great, thanks. Looks like the uniData permissions
don't have anything to do with how the uniData service is
run and everything to do with the (Windows) User. So all
I have to do is log into uniData as a Windows User that
can see the Mac share at \\computername\sharename\directory
and all's well.

--
frosty

On Sep 14, 2:55*pm, frosty <fros... (AT) bogus (DOT) invalid> wrote:

This is probably a stupid suggestion but....

Your mv database is running on server / machine X and you are sitting
at PC Y
If you are connected to your mv database and go to DOS *through your
connection* then Net Use ONLY sees the drives that that server has
mapped.
It cannot see the drives that your local PC has mapped for itself.

That is I'm at the '>' TCL prompt, I type DOS or whatever I pop to the
D:\UV\Account
prompt

I now type NET USE at that point. It does not query my *locally
defined* mapped drives.
It queries those drives you've mapped by going into the computer room,
logging into that server / PC running the actual MV and mapping drives
by typing on *that* keyboard.

W

On 9/15/11 10:55 AM, wjhonson wrote:
What is this "DOS" to which you refer? =`;^> (j/k)

I've had (limited) success using \\computername\sharename\directory
style of path, and no success using the letter mapped drive, so
have given up on the latter.

--
frosty

On 9/15/11 10:55 AM, wjhonson wrote:
What is this "DOS" to which you refer? =`;^> (j/k)

I've had (limited) success using \\computername\sharename\directory
style of path, and no success using the letter mapped drive, so
have given up on the latter.

--
frosty

On Sep 15, 11:06*am, frosty <fros... (AT) bogus (DOT) invalid> wrote:
DOS was created by some pointy-nosed smarmy-faced upstart now nouveau
rich billionaire and the people he stepped on, on the way up. Unix on
the other hand was created by some guy hiding in a closet who no one's
ever heard of since.

You're also going to have permission issues with various directories
depending on how you've setup both the directory permission and your
user groups.