Re: [Samba] Tree connect failed: ERRDOS - ERRnomem

sorry for the long lag in reply...my grandmother passed so I've been down i=
n
TN for her services.

leavenode.20.eatallspam@spamgourmet.com wrote:

You don't see a slowdown or even jobs failing (oom-killer) when you receive
the samba "out of memory" messages?

no....very strange

.....

I tried deleting browse.dat but this didn't make a difference. I don't
have wins.dat, gencache.tdb, or connections.tdb. Should I?????


Actually yes, maybe these files are not built until a first connection has
been established to a new server. Run updatedb and "locate" them afterwards=
..
.....

okay I found them....

[global]
panic action =3D /usr/share/samba/panic-action %d
netbios name =3D alfalfa
workgroup =3D OAKWOOD
server string =3D Fileserver
guest account =3D nobody


Try a "smbclient -L alfalfa -U nobody" and see if that works from the shell=
..
"nobody" should be able to "browse".

this works.

I can also

colin@Alfalfa:/$ smbclient -L buckwheat
Password:
Domain=3D[OAKWOOD] OS=3D[Windows 5.1] Server=3D[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
IPC$ IPC Remote IPC
SharedDocs Disk
share Disk
ADMIN$ Disk Remote Admin
C$ Disk Default share
Domain=3D[OAKWOOD] OS=3D[Windows 5.1] Server=3D[Windows 2000 LAN Manager]

Server Comment
--------- -------

Workgroup Master
--------- -------

but when I try
colin@Alfalfa:/$ smbclient //buckwheat/share
Password:
Domain=3D[OAKWOOD] OS=3D[Windows 5.1] Server=3D[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_INSUFF_SERVER_RESOURCES


After I found browse.dat, wins.dat, connections.tdb, and gencache.tdb...

colin@Alfalfa:/var/run/samba$ sudo invoke-rc.d samba stop
Stoping Samba daemons: nmbd smbd.
colin@Alfalfa:/var/run/samba$ sudo rm -f connections.tdb
gencache.tdb/var/lib/samba/wins.dat /var/cache/samba/browse.dat
colin@Alfalfa:/var/run/samba$ sudo invoke-rc.d samba start
Starting Samba daemons: nmbd smbd.

and now I can't even connect to or list the shares on any of my clients

colin@Alfalfa:/var/run/samba$ smbclient -L buckwheat
Connection to buckwheat failed
colin@Alfalfa:/var/run/samba$ smbclient //buckwheat/share
Connection to buckwheat failed
colin@Alfalfa:/var/run/samba$ smbclient //darla/share
Connection to darla failed

But I can still list shares on the server. I can also access all shares fro=
m
windows clients except those on Buckwheat(the aflicted client)

log file =3D /var/log/samba/log.%m
max log size =3D 5000
security =3D user
domain logons =3D yes


You are certain your domain trust stands?
If it does, you should be able to "smbclient //winclient/c$ -U root" and gi=
ve
the root password, and connect to the admin share of your clients. Or, if y=
ou
login to the windows client with root credentials, you should also have loc=
al
admin rights on the winbox or at least permission to change domain
membership.

I should have tried that before I deleted those files, because smbclient i=
s
no longer working (see above)


logon home =3D
logon path =3D
logon script =3D %U.bat
encrypt passwords =3D true
passdb backend =3D smbpasswd guest


Rather omit the guest here.

invalid users =3D bin adm sync shutdown halt mail news uucp operator
socket options =3D TCP_NODELAY SO_RCVBUF=3D8192 SO_SNDBUF=3D8192
interfaces =3D 192.168.111.0/24 <http://192.168.111.0/24>
local master =3D yes
os level =3D 255


Don't use such high levels. You may get adverse effects. Usually 64 is far
enough.

Okay fixed conf...

domain master =3D yes
preferred master =3D yes
wins support =3D yes
dns proxy =3D no
name resolve order =3D wins lmhosts hosts
unix password sync =3D false
passwd program =3D /usr/bin/passwd %u
passwd chat =3D *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n .
add machine script =3D /usr/sbin/useradd -d /dev/null -g 100 -s
/bin/false -M %u

[netlogon]
comment =3D Network Logon Service
path =3D /home/samba/netlogon


By all means, make sure the netlogon path is accessible/readable for the
clients. You have to consider the filesystem permissions.


It is

Actually I am uncertain where your problem lies, but it's something
netbios-name-resolution related. You should use "nbtstat -a <nebiosname>" o=
n
windows-clients, and "nmblookup -a <netbiosname> -S" on the linux. You may
substitute "-A <ip-of-host>" if names don't work.
Make sure your dns setup or your /etc/hosts does not point to the same IPs
using different names. Often some setup with different dns/netbios names
makes nothing but a big mess in the end.

Good Luck again, and come back with your solution (hopefully).

nbstat and nmblookup look okay

colin@Alfalfa:~$ nmblookup -a darla -S
querying darla on 192.168.111.255 <http://192.168.111.255>
192.168.111.3 <http://192.168.111.3> darla<00>
Looking up status of 192.168.111.3 <http://192.168.111.3>
DARLA <00> - M <ACTIVE>
DARLA <20> - M <ACTIVE>
OAKWOOD <00> - <GROUP> M <ACTIVE>
OAKWOOD <1e> - <GROUP> M <ACTIVE>

MAC Address =3D 00-11-95-03-FE-54

colin@Alfalfa:~$ smbclient -L darla
Connection to darla failed
colin@Alfalfa:~$ nmblookup -a buckwheat -S
querying buckwheat on 192.168.111.255 <http://192.168.111.255>
192.168.111.2 <http://192.168.111.2> buckwheat<00>
Looking up status of 192.168.111.2 <http://192.168.111.2>
BUCKWHEAT <00> - M <ACTIVE>
OAKWOOD <00> - <GROUP> M <ACTIVE>
BUCKWHEAT <20> - M <ACTIVE>
OAKWOOD <1e> - <GROUP> M <ACTIVE>

MAC Address =3D 00-01-29-F9-39-1B

colin@Alfalfa:~$ smbclient //darla/c$ -U root
Connection to darla failed

And once again nothing I did produced anything interesting in the logs!!!!
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba