Hi all,
Wondering if anyone can help me here? Having just upgraded from Samba
3.0.2a to Samba 3.0.4, I've found that Veritas Backup Exec 8.6 is no
longer able to browse my shares. A quick "make revert" and everything
is
back as it should be. The things I see in the samba log are like this:
[2004/05/19 12:46:40, 1] smbd/service.c:make_connection_snum(619)
titanium (192.168.1.39) connect to service Archive initially as user
ZA\backup (uid=0, gid=10000) (pid 23218)
[2004/05/19 12:46:40, 0] smbd/service.c:make_connection(771)
titanium (192.168.1.39) couldn't find service c$
[2004/05/19 12:46:40, 1] smbd/service.c:close_cnum(801)
titanium (192.168.1.39) closed connection to service Archive
[2004/05/19 12:47:01, 1]
nsswitch/winbindd_group.c:winbindd_getgroups(1032)
user 'root' does not exist
[2004/05/19 12:47:23, 1]
nsswitch/winbindd_group.c:winbindd_getgroups(1032)
user 'root' does not exist
[2004/05/19 12:47:58, 0] lib/util_sock.c:get_peer_addr(978)
getpeername failed. Error was Transport endpoint is not connected
If a make a share called c$ then I get:
titanium (192.168.1.39) connect to service c$ initially as user
ZA\backup (uid=10064, gid=10001) (pid 22969)
[2004/05/19 12:42:23, 1]
nsswitch/winbindd_group.c:winbindd_getgroups(1032)
user 'root' does not exist
[2004/05/19 12:42:28, 0] smbd/connection.c:register_message_flags(220)
register_message_flags: tdb_fetch failed
[2004/05/19 12:42:43, 1] smbd/service.c:close_cnum(801)
titanium (192.168.1.39) closed connection to service Archive
[2004/05/19 12:42:49, 1] smbd/service.c:close_cnum(801)
titanium (192.168.1.39) closed connection to service c$
[2004/05/19 12:42:49, 1] smbd/service.c:make_connection_snum(619)
But any attempts to access the share via Backup Exec results in a
password prompt that will not accept valid accounts.
Everything works fine in Windows Explorer.
Any ideas?
Thanks!
