Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Fleet Admiral
Fleet Admiral
2720 views

Accessing users home dir from W7 using net use

Hi!
Probably I'm doing something wrong. OES11SP1 on SLES11SP2. User home dir accessible using net use from Windows XP, but not from Windows 7. Already tried to change LmCompatibilityLevel in registry (to 1), but didn't help. I recall, some year ago I had same problem from W7 (64bit) and then I installed Novell Client, now I'm trying to wo the client, should be possible?
More thanks, Alar.
Labels (2)
0 Likes
17 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

On 10.10.2013 13:56, NovAlf wrote:
>
> Hi!
> Probably I'm doing something wrong. OES11SP1 on SLES11SP2. User home dir
> accessible using net use from Windows XP, but not from Windows 7.
> Already tried to change LmCompatibilityLevel in registry (to 1), but
> didn't help. I recall, some year ago I had same problem from W7 (64bit)
> and then I installed Novell Client, now I'm trying to wo the client,
> should be possible?
> More thanks, Alar.


If you can or can't access a share on OES11 without the Novell CLient
depends on if you have configured and enabled CIFS on the server.

Note that "Net Use" is an universal command, and uses the Novell CLient
too *if* it is installed. Many People believe "Net Use" would somehow be
Microsoft Network specific, but it isn't. It uses whatever network
client is isnstalled and able to access the resource.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Fleet Admiral
Fleet Admiral

Hi again and thanks!
Ahjaa, I forgot totally that on this WXP device is Novell Client already installed.
CIFS is on server running, but in default state, I mean, as it was during OES initial setup.
Any hints? 😃
More thanks, Alar.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 10.10.2013 14:36, NovAlf wrote:
>
> Hi again and thanks!
> Ahjaa, I forgot totally that on this WXP device is Novell Client already
> installed.
> CIFS is on server running, but in default state, I mean, as it was
> during OES initial setup.


That's likely not enough. I suggest consulting the documentation for all
necessary steps to make CIFS work. 😉 There are quite some prerequisites
like Universal Passwords and such...

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Fleet Admiral
Fleet Admiral

Hi and thanks!
My nose is in doc's right now, not sure I read it out. 😃
Anyway, error I get in W7 (wo. Novell Client installed) using net use is "System error 86 has occurred. The specified network password is not correct.".
But when with NC installed everything is fine with server current conf, something NC does add to Windows device?
More thanks, Alar.
0 Likes
Fleet Admiral
Fleet Admiral

Enable Universal Password is true.
Alar.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 10.10.2013 15:26, NovAlf wrote:
>
> Enable Universal Password is true.


That's the client, and not too relevant.
Universal Passwords have to be configured (password policy!), enabled
(password policy assigned to users) and properly set (e.g somehow the
universal password itself must have been filled) in your eDirectory tree.

Your error suggests it isn't in your tree...

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Fleet Admiral
Fleet Admiral

In cifs.log I see
Oct 10 16:57:35 <server> CIFS[6714]: WARNING: CODIR: SESNotLoggedIn: User: <user> not found, Client: <windows_dev_IP>, nwErr: -601, cifsErr: 0
Alar.
0 Likes
Fleet Admiral
Fleet Admiral

Thank You!
Oh yes, walked out of room and ... this error above and ... in CIFS conf was selected root container, but not this one I had these users. Oooo, yes! Totally blind. I knew it is something looking at my wide eyes open, but I can't spot it.
More thanks, Alar.
0 Likes
Fleet Admiral
Fleet Admiral

Ahjaa, this registry change in W7 is still mandatory, seems to.
Alar.
0 Likes
Fleet Admiral
Fleet Admiral

Ahjaa, one - probably little out of topic - interesting thing still yet. From W7 device I can use "net use <IP>", but not "net use <DN>", something to-do with IPv6, I suppose. On WXP it's ok using <DN>.
System error 67 has occurred.
The network name cannot be found.
Alar.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

On 10.10.2013 16:46, NovAlf wrote:
>
> Ahjaa, one - probably little out of topic - interesting thing still yet.
> From W7 device I can use "net use <IP>", but not "net use <DN>",
> something to-do with IPv6, I suppose. On WXP it's ok using <DN>.
> System error 67 has occurred.
> The network name cannot be found.
> Alar.


Do you have your servers *cifs* name (which is likely different from the
regular server name) added to your local DNS? That should do it.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.