Re: [Samba] Disconnected network drive
Hi Oliver, On Saturday 16 December 2006 4:54 pm, Oliver Schulze L. wrote: > Found this nice info: > > Net Config Server /autodisconnect:-1 Is that specifically: C:> net config server /autodisconnect: -1 or is the syntax a little different? The capital letters left me wondering. Thanks. Paul -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Disconnected network drive
Thanks for the tip about the registry, I found this interesting articles: http://support.microsoft.com/kb/138365/en-us http://support.microsoft.com/kb/297684/EN-US/ From here: http://lists.samba.org/archive/samba/1999-July/013511.html HTH Oliver Adam Williams wrote: If I recall correctly there is some registry tweak which relates to this. -- Oliver Schulze L. | Get my e-mail after a captcha in: Asuncion - Paraguay | http://tinymailto.com/oliver -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Disconnected network drive
Found this nice info: Net Config Server /autodisconnect:-1 Credits: http://lists.samba.org/archive/samba/1999-July/013511.html HTH Oliver Paul Abrahams wrote: I have a couple of Linux directories that are being exported via Samba running under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) drive letter. In the "My Computer" list they initially show up as "Disconnected Network Drive". If I attempt to access a file within one of them, the access fails with an indication that the drive does not exist. (For example, if the drive letter is H:, doing "H:" from a C> prompt gives that message.) However, if in Windows I click on the drive, I get to see its contents and the status changes to "Network Drive". At that point the drive contents become available to my Windows applications. I get this behavior on three different machines, all running Windows XP. In the Windows drive mapping, I've checked the "Reconnect at Logon" box, but that makes no difference. I'm guessing that the problem is on the Linux side since each Windows machine can access exported directories from other Windows machines without any difficulty. It's only the drives exported from Linux that have the problem. I can of course work around the problem by opening up My Computer when I start the Windows machine and clicking on the drive in question, but that should not be necessary. Is this a known problem? Is there a workaround or a fix? Paul -- Oliver Schulze L. | Get my e-mail after a captcha in: Asuncion - Paraguay | http://tinymailto.com/oliver -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Disconnected network drive
On Tue, 2006-11-28 at 18:30 -0500, Paul Abrahams wrote: > I have a couple of Linux directories that are being exported via Samba > running > under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) > drive letter. In the "My Computer" list they initially show up as > "Disconnected Network Drive". If I attempt to access a file within one of > them, the access fails with an indication that the drive does not exist. > (For example, if the drive letter is H:, doing "H:" from a C> prompt gives > that message.) However, if in Windows I click on the drive, I get to see > its contents and the status changes to "Network Drive". At that point the > drive contents become available to my Windows applications. This disconnected thing normal, and controlled on the Windows side. Just ignore it. Use UNCs not [stupid legacy] drive letters. If I recall correctly there is some registry tweak which relates to this. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Disconnected network drive
At 06:30 PM 11/28/2006 -0500, Paul Abrahams wrote: I have a couple of Linux directories that are being exported via Samba running under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) Me too, only mine is SuSE 9.3 drive letter. In the "My Computer" list they initially show up as "Disconnected Network Drive". Mine too. If I attempt to access a file within one of them, the access fails with an indication that the drive does not exist. Not mine. Sometimes they change from "Disconnected network drive" to "Network drive" upon access, sometimes they don't. But I never get errors. They are always accessible. (For example, if the drive letter is H:, doing "H:" from a C> prompt gives that message.) However, if in Windows I click on the drive, I get to see its contents and the status changes to "Network Drive". At that point the drive contents become available to my Windows applications. Put a new shortcut in your startup menu on the Winders machine. Make the command line consist of F: where F: is a drive letter of the Samba drive. After you create the shortcut, right click it again and choose properties. Select "minimized" instead of "normal window" on the "shortcut" tab. When you get around to it after bootup/login, close the minimized window this shortcut opens. I get this behavior on three different machines, all running Windows XP. In the Windows drive mapping, I've checked the "Reconnect at Logon" box, but that makes no difference. I always specify reconnect at Logon. But the username and password on the Winders machine are exactly the same as the samba username/password (I don't use a PDC) and before I made that change, I had similar problems. I'm guessing that the problem is on the Linux side since each Windows machine can access exported directories from other Windows machines without any difficulty. It's only the drives exported from Linux that have the problem. [Philosophy] Reality is that which, when you stop believing in it, doesn't go away. --Phillip K. Dick, 1928-1982 --... ...-- -.. . -. . --.- --.- -... [EMAIL PROTECTED] (remove "nospam") N9QQB (amateur radio) "HEY YOU" (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters 43° 7' 17.2" N by 88° 6' 28.9" W, Elevation 815', Grid Square EN53wc WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Disconnected network drive
I have the same trouble Already tried deadtime and other options. If someone can help us. Paul Abrahams wrote: I have a couple of Linux directories that are being exported via Samba running under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) drive letter. In the "My Computer" list they initially show up as "Disconnected Network Drive". If I attempt to access a file within one of them, the access fails with an indication that the drive does not exist. (For example, if the drive letter is H:, doing "H:" from a C> prompt gives that message.) However, if in Windows I click on the drive, I get to see its contents and the status changes to "Network Drive". At that point the drive contents become available to my Windows applications. I get this behavior on three different machines, all running Windows XP. In the Windows drive mapping, I've checked the "Reconnect at Logon" box, but that makes no difference. I'm guessing that the problem is on the Linux side since each Windows machine can access exported directories from other Windows machines without any difficulty. It's only the drives exported from Linux that have the problem. I can of course work around the problem by opening up My Computer when I start the Windows machine and clicking on the drive in question, but that should not be necessary. Is this a known problem? Is there a workaround or a fix? Paul -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Disconnected network drive
I have a couple of Linux directories that are being exported via Samba running under SuSE 10.0. On the Windows side, each of them is assigned a (mapped) drive letter. In the "My Computer" list they initially show up as "Disconnected Network Drive". If I attempt to access a file within one of them, the access fails with an indication that the drive does not exist. (For example, if the drive letter is H:, doing "H:" from a C> prompt gives that message.) However, if in Windows I click on the drive, I get to see its contents and the status changes to "Network Drive". At that point the drive contents become available to my Windows applications. I get this behavior on three different machines, all running Windows XP. In the Windows drive mapping, I've checked the "Reconnect at Logon" box, but that makes no difference. I'm guessing that the problem is on the Linux side since each Windows machine can access exported directories from other Windows machines without any difficulty. It's only the drives exported from Linux that have the problem. I can of course work around the problem by opening up My Computer when I start the Windows machine and clicking on the drive in question, but that should not be necessary. Is this a known problem? Is there a workaround or a fix? Paul -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
