I fixed this by using the following in login scripts for every share
each domain account was supposed to have:
net use driveletter: /delete
net use driverletter: \\newserver\newsharelocation
This fixed 99% of the invalid shares we had. There were a few people
that had manually mapped drives. I just removed their mappings and added
their mapped drives to their login scripts to set it correctly and that
solved the issue.
I eventually turned this off after I was satisfied all bad mappings had
been resolved. Of course, it was the complaint of a user who uses
offline files heavily that really helped nudge me into turning it off.
The delete command was mucking up his sync process when he logged in
first thing in the morning. Offline files sync as soon as they possibly
can. Login scripts continue run if they are taking a while to complete
despite syncing. The whole delete and recreating of a share seems to
take just long enough so that a share can be delete while syncing is
going on. The sync process gets very moody when you take away its mapped
drive during sync.
Jonathan Johnson wrote:
Please review the Samba HOWTO, chapter 10, "Common Errors" where it
discusses this issue.
http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetworkBrowsing.html#id350945
Jonathan Johnson
Sutinen Consulting, Inc.
www.sutinen.com
Aaron Kincer wrote:
Also, as others have mentioned, Windows and its applications can have
long memories about servers contacted in the past. For example, the
list of recently opened files.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
