'net use' fails with netbios, succeeds with IP

[johnny.dr]

Yo all! I have a N4F folder shared to one user I created. I've been trying to access my N4F box via Win8 file explorer. When I open the NAS share, it asks for a username and password. So I enter this info but it always fails. Next I tried the net use command. It fails using the N4F netbios name but succeeds if I use the IP. What gives? NAS4Free v9.1.0.1 (573)

Code: Select all

C:\>net use * \\NAS\Pictures /user:johnny
System error 1219 has occurred.
Multiple connections to a server or shared resource by teh same user, using more than one user name, are not allowed.  Disconnect all previous connections to the server or shared resource and try again.

but if use the NAS IP instead, it works fine:

Code: Select all

C:\>net use * \\192.168.3.250\Pictures /user:johnny
Enter the password for 'johnny' to connect to '192.168.3.250': mypassword
The command completed successfully.

[al562]

Hi Johnny.dr,

Welcome to the NAS4Free forum. Below is information you may find helpful.

Please read and follow the Forum Rules & Guidelines and the FAQs.
By doing so you will:

• Understand what information you should provide when you ask a question or report a problem/bug. By providing all information upfront you will get faster and better answers; that's what you want right?
• Find the answer to your problem in the FAQs or use the Advanced search to search the forum.
• Help us understand your problem and allow us to provide an accurate answer/solution without asking additional questions.
• Help the community by keeping the forum clean, focused and professional.
• Remember to use WebGUI Tab> Help|Report Generator when creating new topics/threads.
• If you have not, then please read the latest Setup & User Guide.

None of your issues are NAS4Free related, but I will try to help anyway.

When I open the NAS share, it asks for a username and password. So I enter this info but it always fails.

Why do you want to do this? Don't you know Windows automatically uses the credentials of the logged in user for authentication? Just create a user on the server exactly like the user on the client. It will stop failing when you configure everything exactly the way Microsoft intends you to.

Next I tried the net use command.

It fails using the N4F netbios name but succeeds if I use the IP. What gives?

Bill Gates is what gives.

System error 1219 has occurred.

Please read Multiple Credentials in a Single Windows NT Session. This is the way Windows works, please also read Error message when you use user credentials to connect to a network share from a Windows-based computer: where they state outright this behavior is by design.

So you can implement their solution if you are so inclined, or just have matching usernames and passwords, your choice. Please let us know how you make out.

Wishing yo very good luck,
Al

[raulfg3]

post your SMB NAS config.

Remember that SMB2 and AIO at same time is dissapointed due errors.

[johnny.dr]

Thanks guys for being willing to help.

So I didn't realize network connections use my machine logon credentials by default. I'm using Win8 with a Microsoft account login (user@emailservice.com). The following is the output of net users command:

Code: Select all

C:\>net users
User accounts for \\STUDY
----------------------------------------------------------
Administrator          Donette               Guest
Johnny

I assume 'Johnny' is the local username connected to my microsoft login credentials. I added a 'Johnny' user to N4F using the same password. I am still prompted for login credentials when trying to browse the NAS via File Explorer.

win8_n4f_users.png

raulfg3, below is the output of /var/etc/smb.conf:

Code: Select all

[global]
encrypt passwords = yes
netbios name = NAS
workgroup = WORKGROUP
server string = NAS File Server
security = user
max protocol = NT1
dns proxy = no
# Settings to enhance performance:
strict locking = no
read raw = yes
write raw = yes
oplocks = yes
max xmit = 65535
deadtime = 15
getwd cache = yes
socket options = TCP_NODELAY SO_SNDBUF=64240 SO_RCVBUF=64240 
# End of performance section
unix charset = UTF-8
store dos attributes = yes
local master = no
domain master = no
preferred master = no
os level = 0
time server = no
guest account = ftp
map to guest = Never
display charset = LOCALE
max log size = 100
syslog only = yes
syslog = 1
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
log level = 1
dos charset = CP437
smb passwd file = /var/etc/private/smbpasswd
private dir = /var/etc/private
passdb backend = tdbsam
idmap config * : backend = tdb
idmap config * : range = 10000-39999
aio read size = 4096
aio write size = 4096

[Pictures]
comment = Pictures
path = /zpool1/Pictures/
writeable = yes
printable = no
veto files = /.snap/.sujournal/
hide dot files = yes
guest ok = no
inherit permissions = yes
vfs objects = 
#vfs objects = netatalk

[al562]

Hi Johnny.dr,

Ahhaaaa! The game is a foot, or Parcheesi, I guess it depends on your preferred fetish .

I'm using Win8 with a Microsoft account login

While I have networked Windows 8 machines none of them yet use a Microsoft account to login, they all use local accounts ( I don't expect to use a Microsoft account for a while) so I have not seen this behavior yet. Interesting, I am not sure what it would send in this case, but I cannot imagine Microsoft is so stupid as to break such an ancient protocol. Then again this is the 21st century, a time which will certainly be known in future history books as the "Quality Control-Less Ages". Also don't discount the idea that MS may want to try to force everyone into the cloud .

Based on the posted .png I will assume you also tried johnny.dr and it too did not work (good idea to eliminate the "J" as part of the problem), though you might want to try changing it to johnny on both server and client just to be sure.

The quick way for you to get around this is to try to permanently map a drive to your share using the IP address. Have it remember the credentials and connect automatically. At least that way you do it once and forget about it. Not optimal, but should work.

Let us know how it turns out.

Rgards,
Al

[johnny.dr]

Hey Al, I've found that by creating a local windows8 account and creating a user with the same credentials on the N4F box, I can browse network shares without pesky permissions requests. So it looks like my main issue is that the username associated with Microsoft account login cannot be known for certain. Next i'm going to try changing the local account to use a Microsoft account login & see if the username credential persists. I'll post back with results.

I also came across an article discussing Windows Credential Manager. For anyone else experiencing similar issues, you might give it a try to see if it will help solve your problem.
http://www.techrepublic.com/blog/window ... ndows/2734

[nas_py_lord]

Hey Al, I've found that by creating a local windows8 account and creating a user with the same credentials on the N4F box, I can browse network shares without pesky permissions requests. So it looks like my main issue is that the username associated with Microsoft account login cannot be known for certain. Next i'm going to try changing the local account to use a Microsoft account login & see if the username credential persists. I'll post back with results.

I also came across an article discussing Windows Credential Manager. For anyone else experiencing similar issues, you might give it a try to see if it will help solve your problem.
http://www.techrepublic.com/blog/window ... ndows/2734

I'm having your same problem, and created the local account with same credentials as the nas box, but it doesnt show up on file explorer. Im testing nas4free on a virtual machine, dont know if maybe thats the problem in first place...

[alexey123]

What problem??
I have worked net use without problem

I add in auxparameter for smb

interfaces = 10.0.0.1/24
socket address = 10.0.0.1
wins support = yes

And configure dhcp for XP, but define WINS. NetBIOS setup is default
My dhcp server on nas4free work as

[johnny.dr]

Hey Al, I've found that by creating a local windows8 account and creating a user with the same credentials on the N4F box, I can browse network shares without pesky permissions requests. So it looks like my main issue is that the username associated with Microsoft account login cannot be known for certain. Next i'm going to try changing the local account to use a Microsoft account login & see if the username credential persists. I'll post back with results.

I also came across an article discussing Windows Credential Manager. For anyone else experiencing similar issues, you might give it a try to see if it will help solve your problem.
http://www.techrepublic.com/blog/window ... ndows/2734

After changing the account back to a Microsoft account, I couldn't access the server shares...again. Rather than switch back to a local account, I just added my NAS credentials to the Windows credential manager...worked like a charm. I hope this helps anyone else experiencing similar issues.

http://windows.microsoft.com/en-us/wind ... atic-logon