OpenSuSE 11.2: no longer access to NAS-shares

meyeo · November 15, 2009, 12:25pm

Since upgrading to 11.2 I get a ‘Timeout on server X’ when trying to access my NAS-shares in KDE.
Other shares on windowsmachines work just fine.

When using smbclient I get:

smbclient -L ////NAS
WARNING: Ignoring invalid value ‘NT’ for parameter ‘max protocol’
Enter user’s password:
Receiving SMB: Server stopped responding
session request to NAS failed (Call returned zero bytes (EOF))

Any pointers would be appreciated.

user · November 16, 2009, 12:31am

On Sun November 15 2009 05:26 am, meyeo wrote:

>
> Since upgrading to 11.2 I get a ‘Timeout on server X’ when trying to
> access my NAS-shares in KDE.
> Other shares on windowsmachines work just fine.
>
> When using smbclient I get:
>> smbclient -L ////NAS
>> WARNING: Ignoring invalid value ‘NT’ for parameter ‘max protocol’
>> Enter user’s password:
>> Receiving SMB: Server stopped responding
>> session request to NAS failed (Call returned zero bytes (EOF))
>
> Any pointers would be appreciated.
>
>
mayeo;
For testing only try disabling the firewall. Then try:


smbclient -L //<IP of NAS> -U<username>%<password>

Post back the results.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

user · November 16, 2009, 12:34am

On Sun November 15 2009 05:31 pm, PV wrote:

> On Sun November 15 2009 05:26 am, meyeo wrote:
<snip>
>>
>> Any pointers would be appreciated.
>>
>>
> mayeo;
> For testing only try disabling the firewall. Then try:
>


> smbclient -L //<IP of NAS> -U<username>%<password>
>

> Post back the results.
mayeo;
In the above <username> <password> are the username and password for the NAS.
Sorry I forgot to mention that with my first post.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

meyeo · November 16, 2009, 1:19am

There is no password on the NAS set.
It’s a TEAC HD-35 with firmware NAS-BASIC47, LOADER 67
Disabling the firewall gives the same result.

user@linuxbox:/> smbclient -L ////192.168.1.3
WARNING: Ignoring invalid value 'NT' for parameter 'max protocol'
Enter user's password:
Receiving SMB: Server stopped responding
session request to 192.168.1.3 failed (Call returned zero bytes (EOF))
tree connect failed: NT_STATUS_END_OF_FILE

Many thanks again.

user · November 16, 2009, 2:12am

On Sun November 15 2009 06:26 pm, meyeo wrote:

>
> There is no password on the NAS set.
> It’s a TEAC HD-35 with firmware NAS-BASIC47, LOADER 67
> Disabling the firewall gives the same result.
>
>
>
>
> Code:
> --------------------
> user@linuxbox:/> smbclient -L ////192.168.1.3
> WARNING: Ignoring invalid value ‘NT’ for parameter ‘max protocol’
> Enter user’s password:
> Receiving SMB: Server stopped responding
> session request to 192.168.1.3 failed (Call returned zero bytes (EOF))
> tree connect failed: NT_STATUS_END_OF_FILE
> --------------------
>
>
>
> Many thanks again.
>
>
meyeo;

The above is coming from your /etc/samba/smb.conf. There is normally no
reason to set “max protocol”. Can you please post the contents
of /etc/samba/smb.conf? Use substitute values for any sensitive IP’s, Domain
Names etc.

It might help if you read:
http://opensuse.swerdna.org/suselanprimer.html

While testing keep the firewall down.
Make sure to create samba users with:


su
smbpasswd -a <username>

Username must be a valid linux user but the password provided need NOT be the
login password.

–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green

meyeo · November 16, 2009, 7:28am

This is the smb.conf-file:

[global]
usershare max shares = 100
workgroup = WORKGROUP
map to guest = Bad User
restrict anonymous = no
guest ok = yes
domain master = no
max protocol = NT
acl compatibility = winnt
ldap ssl = No
server signing = Auto
add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
security = share
server string = linuxbox

log level = 1

[homes]
case sensitive = no
strict locking = no
msdfs proxy = no
read only = no

[homepage]
path = /home/meyeo/Documents/Homepage/
read only = no

[documents]
path = /home/meyeo/Documents/
read only = no

[data1]
path = /data1/

[pics]
path = /pics/
read only = no
inherit permissions = yes
case sensitive = no
strict locking = no
msdfs proxy = no


[movies]
path = /movies/


path = /mp3/
read only = no

[MOVIES2]
path = /movies2/
read only = no

[VIDEO]
path = /video/

I run into trouble with Samba now and then, mostly after an upgrade.
The Linux-shares on the linuxbox work just fine.
It’s the access to the Windows-shares on other machines and the NAS that give me headaches. I guess the deviations from Swerdna’s files must have crept in while fiddling to get access to those shares.

user · November 16, 2009, 9:02am

On Mon November 16 2009 12:36 am, meyeo wrote:

>
> This is the smb.conf-file:
>
>
> Code:
> --------------------
> [global]
> usershare max shares = 100
> workgroup = WORKGROUP
> map to guest = Bad User
> restrict anonymous = no
The above should be 0, 1 or 2. 0 is the default.
> guest ok = yes
> domain master = no
> max protocol = NT
The above is not a valid value, the proper value would be nt1. Just leave it
at the default since the protocol will be determined by the negotiations of
the machine you are connecting to.
> acl compatibility = winnt
The above defaults to Auto and is the recommended value.
> ldap ssl = No
The above is only valid if you have a ldap server.
> server signing = Auto
I think it would be best to leave the above to the default “disabled”
> add machine script = /usr/sbin/useradd -c
Machine -d /var/lib/nobody -s /bin/false %m$
The above is not needed unless you are configuring a Domain Controller.
> security = share
> server string = linuxbox
>
> log level = 1
>
> [homes]
> case sensitive = no
> strict locking = no
> msdfs proxy = no
> read only = no
>
> [homepage]
> path = /home/meyeo/Documents/Homepage/
> read only = no
>
> [documents]
> path = /home/meyeo/Documents/
> read only = no
>
> [data1]
> path = /data1/
>
> [pics]
> path = /pics/
> read only = no
> inherit permissions = yes
> case sensitive = no
> strict locking = no
> msdfs proxy = no
>
>
> [movies]
> path = /movies/
>
>
> path = /mp3/
> read only = no
>
> [MOVIES2]
> path = /movies2/
> read only = no
>
> [VIDEO]
> path = /video/
> --------------------
>
>
> I run into trouble with Samba now and then, mostly after an upgrade.
> The Linux-shares on the linuxbox work just fine.
> It’s the access to the Windows-shares on other machines and the NAS
> that give me headaches. I guess the deviations from Swerdna’s files must
> have crept in while fiddling to get access to those shares.
>
>
meyeo;
I have made a few comment on your smb.conf above. For details please see:
man smb.conf

IMHO you would be best off starting with a known good smb.conf as in Swerdna’s
HowTo. You might want to add the following two parameters:


lanman auth = Yes
client lanman auth =Yes
name resolve order = bcast host lmhost

I suggest these just in case your NAS requires lanman. From your earlier post
it sounds like the NAS does not respond to smbclient.

Receiving SMB: Server stopped responding
session request to 192.168.1.3 failed (Call returned zero bytes (EOF))
tree connect failed: NT_STATUS_END_OF_FILE

Can you even ping the NAS?
Are all machines on the 192.168.1. sub network?
Are all machines in the workgroup: “WORKGROUP”
Does smbclient connect to any other machine in your network?

–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green

meyeo · November 16, 2009, 10:15pm

I made the changes you suggested.
The output varies a bit now.

user@linuxbox:/> smbclient -L ////192.168.1.3
Enter user's password:
Receiving SMB: Server stopped responding
session request to 192.168.1.3 failed (Call returned zero bytes (EOF))
protocol negotiation failed: NT_STATUS_END_OF_FILE
user@linuxbox:/> smbclient -L ////192.168.1.3
Enter user's password:
Receiving SMB: Server stopped responding
session request to 192.168.1.3 failed (Call returned zero bytes (EOF))
Receiving SMB: Server stopped responding
cli_chain_cork failed
session setup failed: Call returned zero bytes (EOF)

Yes, no problem
Yes, they are
Yes, all are in the same subnetwork.
Yes, it connects to shares on two other WinXP-machines with no problem. Also from these machines and a Mac the NAS is perfectly accessible (as it was before I upgraded to 11.2).

meyeo · November 16, 2009, 10:55pm

Correction!
In a last attempt I rebooted the NAS again. (Had done it before, but not after I made the changes in smb.conf)
Everything works again.
Many thanks!

user · November 17, 2009, 12:17am

On Mon November 16 2009 03:56 pm, meyeo wrote:

>
> Correction!
> In a last attempt I rebooted the NAS again. (Had done it before, but
> not after I made the changes in smb.conf)
> Everything works again.
> Many thanks!
>
>
meyeo;
Congratulations. It’s good that it works since I was fresh out of ideas.

P. V.
“We’re all in this together, I’m pulling for you.” Red Green

OpenSuSE 11.2: no longer access to NAS-shares

Post back the results.

> Post back the results. mayeo; In the above <username> <password> are the username and password for the NAS. Sorry I forgot to mention that with my first post.

> > Correction! > In a last attempt I rebooted the NAS again. (Had done it before, but > not after I made the changes in smb.conf) > Everything works again. > Many thanks! > > meyeo; Congratulations. It’s good that it works since I was fresh out of ideas.

> Post back the results.
mayeo;
In the above <username> <password> are the username and password for the NAS.
Sorry I forgot to mention that with my first post.

>
> Correction!
> In a last attempt I rebooted the NAS again. (Had done it before, but
> not after I made the changes in smb.conf)
> Everything works again.
> Many thanks!
>
>
meyeo;
Congratulations. It’s good that it works since I was fresh out of ideas.