OS X Server/SMB share Drive Mapping Protocol, Windows 7?

[nicholasb]

I have an OS X server running 10.6.3 and an SMB share set up.

I have a Windows Vista workstation that maps to //192.168.2.10/Fin giving it a drive letter S:

I have 3 x Parallels desktops newly installed with Windows 7 running.

I need to set up the drive letters to map in the same way so I can share a database between the clients.

The native Windows Vista machine always maps the drive without fail.

What is the naming convention to achieve the same thing under Windows 7?

When I try and authenticate it brings up a dialogue (Windows Authentication) asks me what my username and password is.

If I log in with a diradmin account it's fine. Any 'normal account it throws me back every time, asking What is your Username and password?

Goddam it. I simply enter the diradmin account credentials and it's fine. Any normal account it starts asking me what domain I am in and so on and so forth. The direct IP address does not work ie \\192.168.2.10\%username%

Do I have to put in the FQDN or some other such nonsense, I've tried already and no dice with this.

I need to sandbox the share to a group and restrict access. The Parallels machines don't have logins they just go to the Desktop under Windows 7.

I want users to either authenticate against the share, or leave the share open with full read write access to the Windows clients. It is to run the Sage accounting software so this has it's own log in anyway.

I can ping the server from Parallels I know it can be reached. Is there anything I need to do regarding the network settings? Maybe bridge the connection or something instead. The good mapping on Vista is not running through any hypervisor, is this the problem.

Driving me mad. 3 x Windows 7, Sage, Mapped Network drive. Shouldn't be hard so why is it such a struggle to authenticate or keep this mapping active?

Any help greatly appreciated.

Nicholas

 

[StanE]

You should be able to use the following:

net use s: \\Server\Share /useromain\Username /pers:yes

Where "Server" is the windows domain name of the server
Where "Share" is the name of the share on the particular server
Where "Domain" is the windows domain name the server is in
Where "Username" is the windows user name of the account you want to have access to the share.

/pers:yes should make the mapping permanent. Use /pers:no if you want to have a script perform the mapping every time and you do not want to see an error message that the drive letter is already in use (it is remembered between sessions)

Let me know if you have a problem. This works for me with Win 7 and OSX Lion.

Stan