Bug 4507 - net shares behaving erratically
net shares behaving erratically
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: winbind
3.0.24
x86 Windows XP
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-12 11:13 UTC by John Engleman
Modified: 2007-04-12 11:13 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Engleman 2007-04-12 11:13:46 UTC
some established shares have started to act up.

smb.conf contains the following:
[global]
   workgroup = cfn
   server string = linserv1
   password level = 8
   username level = 8
   log file = /var/log/samba/log.%m
   max log size = 50
   name resolve order = wins lmhosts bcast
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   local master = No
   wins server = 10.10.10.49
   username map = /etc/samba/smbusers
   password server = 10.10.10.40
   security = user
   template shell = /bin/false
   winbind use default domain = true

[pgms]
        comment = dataflex source files
        path = /u/pgms
        valid users = Passport, dflex, john
        writeable = yes
        browseable = no

[fdat]
        comment = Dataflex Data
        path = /u/fdat
        valid users = Passport, dflex, john
        writable = yes
        browseable = no

[Attendance]
        comment = Attendance Raw Data
        path = /u/fdat/external/attend/records
        writeable = yes
        browseable = no
        valid users = Passport, attend, john

The windows gui will link one but not the other. Both paths have the same owner & group & permissions of drwxrwxrwx

In a cmd window, net use gives the following results:

C:\test>net use g: \\linserv1\pgms
The command completed successfully.

C:\test>net use h: \\linserv1.cfn\pgms
The command completed successfully.

C:\test>net use i: \\linserv1\fdat
System error 3 has occurred.

The system cannot find the path specified.

C:\test>net use i: \\linserv1.cfn\fdat
The command completed successfully.

smbstatus shows:
Samba version 3.0.24-4.fc5
PID     Username      Group         Machine
-------------------------------------------------------------------
 4531   john          adm           cfn104       (10.10.10.56)
 4533   john          adm           cfn104       (10.10.10.56)

Service      pid     machine       Connected at
-------------------------------------------------------
pgms         4531   cfn104        Thu Apr 12 10:32:01 2007
pgms         4533   cfn104        Thu Apr 12 10:32:17 2007
fdat         4531   cfn104        Thu Apr 12 10:32:41 2007
fdat         4533   cfn104        Thu Apr 12 10:33:06 2007

No locked files

log.smb has:

[2007/04/12 10:33:43, 0] lib/util_sock.c:get_peer_addr(1229)
  getpeername failed. Error was Transport endpoint is not connected

and log.cfn104 has:

[2007/04/12 10:32:01, 1] smbd/service.c:make_connection_snum(950)
  cfn104 (10.10.10.56) connect to service pgms initially as user john (uid=500,
gid=4) (pid 4531)
[2007/04/12 10:32:17, 1] smbd/service.c:make_connection_snum(950)
  cfn104 (10.10.10.56) connect to service pgms initially as user john (uid=500,
gid=4) (pid 4533)
[2007/04/12 10:32:41, 1] smbd/service.c:make_connection_snum(950)
  cfn104 (10.10.10.56) connect to service fdat initially as user john (uid=500,
gid=4) (pid 4531)
[2007/04/12 10:33:06, 1] smbd/service.c:make_connection_snum(950)
  cfn104 (10.10.10.56) connect to service fdat initially as user john (uid=500,
gid=4) (pid 4533)

the share [attend] has all the same characteristics with the following symtoms:

computer cfn104 can connect without the domain name where computer cfn150 cannot.

The network has two windows 2003 AD servers, one is a pdc the other is a sdc
I have samba running on two Fedora 5 x86 servers.

I have not been able to trace this back to a windows AD & wins problem but I can't rule it out either. The samba logs & smbstatus do not seem to give me any valid clues as to the problem.

Interestingly enough, I copied the contents of [fdat] to [fdat1] and do not have problems with [fdat1]