[Samba] Mac OS upgrade upsets access to samba shares

[Helen Nulty]

Mac OS details:
Our client was able to access her network resources without any problem 
until  yesterday.

She is using a high end Macbook Pro. She has the latest full version of 
Dave 7.1 installed.  Her Mac OS X is 10.4.11

When she attempts to connect to these resources she receives the 
following error:

"The Finder cannot complete the operation because some of the data in 
smb://........ could not be read or written. (Error code -36)."

Attempts to connect to the shares have used fully qualified domain names:

smb://server.my.domain/share_name

Her Domain password is correct and working.  We tested it out on a PC.
 
Samba server details:
client is on different subnet from samba server
no evidence on samba logs of connection attempt by client
# smbd -V
Version 3.0.24-SerNet-RedHat

smb.conf:
[global]
        workgroup = MYWG
        realm = MY.DOMAIN
        netbios aliases = SERVER
        server string = SPH IIS File Server
        interfaces = eth2:1, lo, 127.0.0.1
        bind interfaces only = Yes
        security = ADS
        password server = x.x.x.x
        log level = 0 passdb:3 auth:3
        syslog = 0
        syslog only = Yes
        max log size = 50000
        name resolve order = wins bcast
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=20480 
SO_SNDBUF=20480
        wins server = x.x.x.x
        ldap ssl = no
        socket address = x.x.x.x, 127.0.0.1
        load printers = no
        printing = bsd
        printcap name = /dev/null
        disable spoolss = yes
        hosts allow = 127.0.0.1, x.y.0.0/255.255.0.0, 
x.z.0.0/255.255.0.0, x.m.0
.0/255.255.0.0, x.y.n.
        hosts deny = all
        block size = 4096
        veto oplock files = /*.*db/
        strict locking = No

"smb.global" 28L, 755C written                               
[root at dandy ~]# cat smb.global
[global]
        workgroup = MYWG
        realm = MY.DOMAIN
        netbios aliases = SERVER
        server string = SPH IIS File Server
        interfaces = eth2:1, lo, 127.0.0.1
        bind interfaces only = Yes
        security = ADS
        password server = x.x.x.x
        encrypt passwords = Yes
        log level = 0 passdb:3 auth:3
        syslog = 0
        syslog only = Yes
        max log size = 50000
        name resolve order = wins bcast
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=20480 
SO_SNDBUF=20480
        wins server = x.x.x.x
        ldap ssl = no
        socket address = x.x.x.x, 127.0.0.1
        load printers = no
        printing = bsd
        printcap name = /dev/null
        disable spoolss = yes
        hosts allow = 127.0.0.1, x.y.0.0/255.255.0.0, 
x.z.0.0/255.255.0.0, x.m.0.0/255.255.0.0, x.y.n.
        hosts deny = all
        block size = 4096
        veto oplock files = /*.*db/
        strict locking = No


We have googled our brains out and tried using NETBIOS names and ip 
addr's in place of fqdn's. 

Any suggestions out there?

Helen

-- 
Helen P. Nulty
Systems Analyst
UNC-CH School of Public Health
Instructional & Information Systems
CB# 7400
Chapel Hill, NC  27599
ph:  919-966-9136
email:  Helen_Nulty at unc.edu