I have a couple of directories set up to be visible to Windows via Samba. On the Windows machine, they initially show up in the Network Drives as "Disconnected Network Drive" (under "My Computer"). (The Linux machine is booted first.) Most programs then have difficulty accessing the contents of these drives. However, if I open one of these drives under "My Computer", it is no longer disconnected and the Windows programs can access its contents just fine. 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? Paul
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
On Friday 01 September 2006 20:01, Paul Abrahams wrote:
I have a couple of directories set up to be visible to Windows via Samba. On the Windows machine, they initially show up in the Network Drives as "Disconnected Network Drive" (under "My Computer"). (The Linux machine is booted first.) Most programs then have difficulty accessing the contents of these drives. However, if I open one of these drives under "My Computer", it is no longer disconnected and the Windows programs can access its contents just fine.
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?
Paul
Hi Paul, I've seen this type of behavior from Windows XP in the past on a "all Windows" network. I do not think Samba is at fault in this. I am not exactly sure what the cause of the problem is, but I suspect it lies within the application in question. Jesse
On Friday 01 September 2006 8:20 pm, Jesse L. Purdom wrote:
On Friday 01 September 2006 20:01, Paul Abrahams wrote:
I have a couple of directories set up to be visible to Windows via Samba. On the Windows machine, they initially show up in the Network Drives as "Disconnected Network Drive" (under "My Computer"). (The Linux machine is booted first.) Most programs then have difficulty accessing the contents of these drives. However, if I open one of these drives under "My Computer", it is no longer disconnected and the Windows programs can access its contents just fine.
I've seen this type of behavior from Windows XP in the past on a "all Windows" network. I do not think Samba is at fault in this. I am not exactly sure what the cause of the problem is, but I suspect it lies within the application in question.
I see the problem with more than one application (Quicken being one but not the only one). But if you've seen the same behavior on an all-Windows network, then indeed the problem must be on the Windows side. It's a nuisance but at least there's a workaround. Paul
On Friday 01 September 2006 08:40 pm, Paul Abrahams wrote:
On Friday 01 September 2006 8:20 pm, Jesse L. Purdom wrote:
On Friday 01 September 2006 20:01, Paul Abrahams wrote:
I have a couple of directories set up to be visible to Windows via Samba. On the Windows machine, they initially show up in the Network Drives as "Disconnected Network Drive" (under "My Computer"). (The Linux machine is booted first.) Most programs then have difficulty accessing the contents of these drives. However, if I open one of these drives under "My Computer", it is no longer disconnected and the Windows programs can access its contents just fine.
check out the "net" command from a windows console. Look at the "persistent" command modifier. net use h: \\server\share /persistent:yes or once you have things connected the way you want net use /persistent:yes I hope this helps you out ... however ... I think I need a shower now ;-) -- Louis Richards
participants (4)
-
Jesse L. Purdom -
Louis Richards -
Paul Abrahams -
stephan beal