I’m having a problem with Samba rev 2.0.7 and Windows XP SP2.
We’ve been running this version of Samba on QNX 4.23 and 4.25 for a while
now but not with XP SP2. With this setup, we receive an “Access is denied”
error message in Windows about 5% of the time. We create small data files
(a couple of K) and use Samba to copy the files to the Windows computer.
The files are closed properly and can be renamed, deleted, and opened in
QNX. If I restart smbd and nmbd I can access the files again.
I have turned off oplocks on the Windows computer and on the QNX computer.
That didn’t help.
My questions - what is causing the access is denied error message? Is there
a newer binary of Samba for QNX 4?
My smb.conf file:
workgroup = WORKGROUP
server string = Machine
max log size = 100
security = user
socket options = TCP_NODELAY
interfaces = 172.16.1.1
netbios name = Machine
min password length = 0
guest account = root
[global]
mangle case = yes
case sensitive = no
preserve case = yes
short preserve case = no
oplocks = False
level2oplocks = False
kernel oplocks = No
[datadir]
comment = Dyno data directory
guest ok = yes
read only = no
writeable = yes
valid users = root
path = /home/data
public = yes
browseable = yes
This started happening recently to me. I have been running Windoze 2000
Pro for a while now with no problem. But after a recent update (it’s
always wanting to “update” to plug “critical security” problems) this
behaviour bcame apparent.
I don’t think it’s samba, as it’s been working fine for years on a QNX4
box. I think something has changed in windoze. What, I don’t know. I am
not a windoze expert and generally only use it to read mail
(thunderbird), browse the web (firefox) and use phindows into my QNX
boxes.
This problem yesterday resulted in me shifting all my mail off the QNX4
samba drive onto a local windoze drive. I didn’t want to do this but I
can’t find a solution.
Like you, a restart of samba (smbd) fixes things, but only for a short
while. But I’m still convinced that the problem is on the windows client
side.
Geoff Roberts
Mark Dornbush wrote:
I’m having a problem with Samba rev 2.0.7 and Windows XP SP2.
We’ve been running this version of Samba on QNX 4.23 and 4.25 for a while
now but not with XP SP2. With this setup, we receive an “Access is denied”
error message in Windows about 5% of the time. We create small data files
(a couple of K) and use Samba to copy the files to the Windows computer.
The files are closed properly and can be renamed, deleted, and opened in
QNX. If I restart smbd and nmbd I can access the files again.
I have turned off oplocks on the Windows computer and on the QNX computer.
That didn’t help.
My questions - what is causing the access is denied error message? Is there
a newer binary of Samba for QNX 4?
My smb.conf file:
workgroup = WORKGROUP
server string = Machine
max log size = 100
security = user
socket options = TCP_NODELAY
interfaces = 172.16.1.1
netbios name = Machine
min password length = 0
guest account = root
[global]
mangle case = yes
case sensitive = no
preserve case = yes
short preserve case = no
oplocks = False
level2oplocks = False
kernel oplocks = No
[datadir]
comment = Dyno data directory
guest ok = yes
read only = no
writeable = yes
valid users = root
path = /home/data
public = yes
browseable = yes
Take a look to
http://www.software.rockwell.com/navigation/news/windowsxpsp2notice.cfm
You are not the only ones afected.
Regards
Joan
Geoff Roberts wrote:
This started happening recently to me. I have been running Windoze 2000
Pro for a while now with no problem. But after a recent update (it’s
always wanting to “update” to plug “critical security” problems) this
behaviour bcame apparent.
I don’t think it’s samba, as it’s been working fine for years on a QNX4
box. I think something has changed in windoze. What, I don’t know. I am
not a windoze expert and generally only use it to read mail
(thunderbird), browse the web (firefox) and use phindows into my QNX
boxes.
This problem yesterday resulted in me shifting all my mail off the QNX4
samba drive onto a local windoze drive. I didn’t want to do this but I
can’t find a solution.
Like you, a restart of samba (smbd) fixes things, but only for a short
while. But I’m still convinced that the problem is on the windows client
side.
Geoff Roberts