Cannot access SMB share (Freenas) from one computer (Windows Server 2003)
up vote
0
down vote
favorite
I cannot access an SMB share (shared on Freenas) from one computer (running Windows Server 2003). The same share is accessible by other computers. I/ve tried accessing it directly, mounting as a letter drive, or using commands:
net use z: \nasSHARENAME /user:nasUSER PASSWD
(with variations using IP instead of DNS name, /user:IPUSER, /user:USER).
I get error 1326 (wrong user or password).
I've tried accessing different user, I deleted and recreated the user, permissions and share on Freenas etc. The share works fine on other computers, but is stuck on this old Windows Server machine.
The dates on both systems are the same. I can ping the freenas server by dns name or IP and I can list the shares. Local security policy is set to classic (secpol.msc).
What else can I check?
networking network-shares samba windows-server-2003 freenas
asked Jun 9 '17 at 9:37
namq
112
add a comment |
up vote
0
down vote
favorite
I cannot access an SMB share (shared on Freenas) from one computer (running Windows Server 2003). The same share is accessible by other computers. I/ve tried accessing it directly, mounting as a letter drive, or using commands:
net use z: \nasSHARENAME /user:nasUSER PASSWD
(with variations using IP instead of DNS name, /user:IPUSER, /user:USER).
I get error 1326 (wrong user or password).
I've tried accessing different user, I deleted and recreated the user, permissions and share on Freenas etc. The share works fine on other computers, but is stuck on this old Windows Server machine.
The dates on both systems are the same. I can ping the freenas server by dns name or IP and I can list the shares. Local security policy is set to classic (secpol.msc).
What else can I check?
networking network-shares samba windows-server-2003 freenas
asked Jun 9 '17 at 9:37
namq
112
This may be related to the SMB version your FreeNAS is exposing vs what your Server2003 is using as the client...
– Kinnectus
Jun 9 '17 at 9:49
@Kinnectus - I've just checked samba settings on Freenas. There's a "server minimum protocol", which is empty, and "server maximum protocol " which is set to SMB3. I've changed it to CORE and SMB3_11 (min and max available) but it didn't help.
– namq
Jun 9 '17 at 10:15
Ah, according to olddoc.freenas.org/index.php/CIFS leaving the "server minimum protocol" to blank (or the default value) configures for automatic protocol negotiation. I'd put it back to what it was. Sorry!
– Kinnectus
Jun 9 '17 at 10:23
You may need to amend the local security policy: fir3net.com/Microsoft/General/…
– Kinnectus
Jun 9 '17 at 10:26
@Kinnectus - I've tried that, forgot to mention. I'll edit the question. Thanks!
– namq
Jun 9 '17 at 10:48
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I cannot access an SMB share (shared on Freenas) from one computer (running Windows Server 2003). The same share is accessible by other computers. I/ve tried accessing it directly, mounting as a letter drive, or using commands:
net use z: \nasSHARENAME /user:nasUSER PASSWD
(with variations using IP instead of DNS name, /user:IPUSER, /user:USER).
I get error 1326 (wrong user or password).
I've tried accessing different user, I deleted and recreated the user, permissions and share on Freenas etc. The share works fine on other computers, but is stuck on this old Windows Server machine.
The dates on both systems are the same. I can ping the freenas server by dns name or IP and I can list the shares. Local security policy is set to classic (secpol.msc).
What else can I check?
networking network-shares samba windows-server-2003 freenas
asked Jun 9 '17 at 9:37
namq
112
I cannot access an SMB share (shared on Freenas) from one computer (running Windows Server 2003). The same share is accessible by other computers. I/ve tried accessing it directly, mounting as a letter drive, or using commands:
net use z: \nasSHARENAME /user:nasUSER PASSWD
(with variations using IP instead of DNS name, /user:IPUSER, /user:USER).
I get error 1326 (wrong user or password).
I've tried accessing different user, I deleted and recreated the user, permissions and share on Freenas etc. The share works fine on other computers, but is stuck on this old Windows Server machine.
The dates on both systems are the same. I can ping the freenas server by dns name or IP and I can list the shares. Local security policy is set to classic (secpol.msc).
What else can I check?
networking network-shares samba windows-server-2003 freenas
networking network-shares samba windows-server-2003 freenas
asked Jun 9 '17 at 9:37
namq
112
asked Jun 9 '17 at 9:37
namq
112
edited Jun 9 '17 at 10:49
asked Jun 9 '17 at 9:37
namq
112
asked Jun 9 '17 at 9:37
namq
112
asked Jun 9 '17 at 9:37
namq
112
112
This may be related to the SMB version your FreeNAS is exposing vs what your Server2003 is using as the client...
– Kinnectus
Jun 9 '17 at 9:49
@Kinnectus - I've just checked samba settings on Freenas. There's a "server minimum protocol", which is empty, and "server maximum protocol " which is set to SMB3. I've changed it to CORE and SMB3_11 (min and max available) but it didn't help.
– namq
Jun 9 '17 at 10:15
Ah, according to olddoc.freenas.org/index.php/CIFS leaving the "server minimum protocol" to blank (or the default value) configures for automatic protocol negotiation. I'd put it back to what it was. Sorry!
– Kinnectus
Jun 9 '17 at 10:23
You may need to amend the local security policy: fir3net.com/Microsoft/General/…
– Kinnectus
Jun 9 '17 at 10:26
@Kinnectus - I've tried that, forgot to mention. I'll edit the question. Thanks!
– namq
Jun 9 '17 at 10:48
add a comment |
This may be related to the SMB version your FreeNAS is exposing vs what your Server2003 is using as the client...
– Kinnectus
Jun 9 '17 at 9:49
@Kinnectus - I've just checked samba settings on Freenas. There's a "server minimum protocol", which is empty, and "server maximum protocol " which is set to SMB3. I've changed it to CORE and SMB3_11 (min and max available) but it didn't help.
– namq
Jun 9 '17 at 10:15
Ah, according to olddoc.freenas.org/index.php/CIFS leaving the "server minimum protocol" to blank (or the default value) configures for automatic protocol negotiation. I'd put it back to what it was. Sorry!
– Kinnectus
Jun 9 '17 at 10:23
You may need to amend the local security policy: fir3net.com/Microsoft/General/…
– Kinnectus
Jun 9 '17 at 10:26
@Kinnectus - I've tried that, forgot to mention. I'll edit the question. Thanks!
– namq
Jun 9 '17 at 10:48
This may be related to the SMB version your FreeNAS is exposing vs what your Server2003 is using as the client...
– Kinnectus
Jun 9 '17 at 9:49
This may be related to the SMB version your FreeNAS is exposing vs what your Server2003 is using as the client...
– Kinnectus
Jun 9 '17 at 9:49
@Kinnectus - I've just checked samba settings on Freenas. There's a "server minimum protocol", which is empty, and "server maximum protocol " which is set to SMB3. I've changed it to CORE and SMB3_11 (min and max available) but it didn't help.
– namq
Jun 9 '17 at 10:15
@Kinnectus - I've just checked samba settings on Freenas. There's a "server minimum protocol", which is empty, and "server maximum protocol " which is set to SMB3. I've changed it to CORE and SMB3_11 (min and max available) but it didn't help.
– namq
Jun 9 '17 at 10:15
Ah, according to olddoc.freenas.org/index.php/CIFS leaving the "server minimum protocol" to blank (or the default value) configures for automatic protocol negotiation. I'd put it back to what it was. Sorry!
– Kinnectus
Jun 9 '17 at 10:23
Ah, according to olddoc.freenas.org/index.php/CIFS leaving the "server minimum protocol" to blank (or the default value) configures for automatic protocol negotiation. I'd put it back to what it was. Sorry!
– Kinnectus
Jun 9 '17 at 10:23
You may need to amend the local security policy: fir3net.com/Microsoft/General/…
– Kinnectus
Jun 9 '17 at 10:26
You may need to amend the local security policy: fir3net.com/Microsoft/General/…
– Kinnectus
Jun 9 '17 at 10:26
@Kinnectus - I've tried that, forgot to mention. I'll edit the question. Thanks!
– namq
Jun 9 '17 at 10:48
@Kinnectus - I've tried that, forgot to mention. I'll edit the question. Thanks!
– namq
Jun 9 '17 at 10:48
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Use a network sniffer to check if your smb client adds the domain name to the username before trying to authenticate.
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
The OP has already tried to connect by providing the domain name...net use z: \nasSHARENAME /user:nasUSER PASSWD
– Kinnectus
Jun 9 '17 at 10:24
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Use a network sniffer to check if your smb client adds the domain name to the username before trying to authenticate.
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
The OP has already tried to connect by providing the domain name...net use z: \nasSHARENAME /user:nasUSER PASSWD
– Kinnectus
Jun 9 '17 at 10:24
add a comment |
up vote
0
down vote
Use a network sniffer to check if your smb client adds the domain name to the username before trying to authenticate.
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
The OP has already tried to connect by providing the domain name...net use z: \nasSHARENAME /user:nasUSER PASSWD
– Kinnectus
Jun 9 '17 at 10:24
add a comment |
up vote
0
down vote
up vote
0
down vote
Use a network sniffer to check if your smb client adds the domain name to the username before trying to authenticate.
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
Use a network sniffer to check if your smb client adds the domain name to the username before trying to authenticate.
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
answered Jun 9 '17 at 10:01
Edik Mkoyan
112217
112217
The OP has already tried to connect by providing the domain name...net use z: \nasSHARENAME /user:nasUSER PASSWD
– Kinnectus
Jun 9 '17 at 10:24
add a comment |
The OP has already tried to connect by providing the domain name...net use z: \nasSHARENAME /user:nasUSER PASSWD
– Kinnectus
Jun 9 '17 at 10:24
The OP has already tried to connect by providing the domain name...
net use z: \nasSHARENAME /user:nasUSER PASSWD– Kinnectus
Jun 9 '17 at 10:24
The OP has already tried to connect by providing the domain name...
net use z: \nasSHARENAME /user:nasUSER PASSWD– Kinnectus
Jun 9 '17 at 10:24
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1217569%2fcannot-access-smb-share-freenas-from-one-computer-windows-server-2003%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This may be related to the SMB version your FreeNAS is exposing vs what your Server2003 is using as the client...
– Kinnectus
Jun 9 '17 at 9:49
@Kinnectus - I've just checked samba settings on Freenas. There's a "server minimum protocol", which is empty, and "server maximum protocol " which is set to SMB3. I've changed it to CORE and SMB3_11 (min and max available) but it didn't help.
– namq
Jun 9 '17 at 10:15
Ah, according to olddoc.freenas.org/index.php/CIFS leaving the "server minimum protocol" to blank (or the default value) configures for automatic protocol negotiation. I'd put it back to what it was. Sorry!
– Kinnectus
Jun 9 '17 at 10:23
You may need to amend the local security policy: fir3net.com/Microsoft/General/…
– Kinnectus
Jun 9 '17 at 10:26
@Kinnectus - I've tried that, forgot to mention. I'll edit the question. Thanks!
– namq
Jun 9 '17 at 10:48