On Saturday 02 September 2006 02:01, Paul Abrahams wrote:
Much as I'd like to say that it's all Windows's fault (being a Linux lover, of course), I can't with confidence say that. It may be some Samba weirdness. I don't know how to determine on which side of the divide the fault lies -- whether it's at bottom a Windows problem or a Linux/Samba problem.
Ideas?
While i can't offer a solution, i can offer an insight: As far as Samba is concerned, samba doesn't know whether "Windows itself" or "an application" requests access to a share. Thus, if accessing it via an application doesn't work until you've opened the folder using Explorer, the error must be on the Windows side. The problem would *appear* to be that Windows doesn't send the connect/authentication information unless Explorer opens the folder. Once that's done, the connection info is cached for later use with arbitrary requests (i.e., applications). This would be surprising because such a strong connection between Explorer and network-connected devices goes against the principals of sound software design, but... we just never know with closed source, do we? :) -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts