From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E8H12-0008Hw-MO for qemu-devel@nongnu.org; Thu, 25 Aug 2005 08:39:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E8H0z-0008Gh-BW for qemu-devel@nongnu.org; Thu, 25 Aug 2005 08:39:30 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E8H0x-00089X-KU for qemu-devel@nongnu.org; Thu, 25 Aug 2005 08:39:27 -0400 Received: from [64.233.184.199] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E8GyJ-0003wJ-P3 for qemu-devel@nongnu.org; Thu, 25 Aug 2005 08:36:44 -0400 Received: by wproxy.gmail.com with SMTP id i31so5936wra for ; Thu, 25 Aug 2005 05:35:22 -0700 (PDT) Message-ID: <23bcb870050825053511c0f8f2@mail.gmail.com> Date: Thu, 25 Aug 2005 08:35:22 -0400 From: Doctor Bill Subject: Re: [Qemu-devel] Read/Write to shares on Windows (XP Pro) host from Windows (2000 Adv) guest. In-Reply-To: <20050825022312.75483.qmail@web50509.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2ad73a0508240803d9d592d@mail.gmail.com> <20050825022312.75483.qmail@web50509.mail.yahoo.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, Francois Rioux On 8/24/05, Francois Rioux wrote: > What I manage to do with a certain success is to map network shares of th= e > host in the guest (net use z: 10.0.2.2\MyShare in the guest). I can brow= se > and read files from the mapped drive. However I can't write to it from t= he > guest. I received an Access Denied message instead even if the share is s= et > so Everyone has Full Control. > =20 > I don't understand why this doesn't work. Is it Windows preventing the wr= ite > is the exchange this a limitation in QEMU or in SLiRP? As I understand i= t > SLiRP translates some tcp headers and acts as a firewall preventing incom= ing > calls but autorizes outgoing calls from the guest out. That's why web > browsing works in user network mode. Should't file transfer work too? I= s > the network file sharing protocol more complex than that for writes? Or i= s > that rather a Windows security issue?=20 > =20 > Any explanation or workaround would be appreciated.=20 I posted something about this in the forum. In my case, I was trying to print to the Windows host. Unfortunately, it looks like the post is no longer there. The solution was simply to add the real IP address and machine name into the lmhost file. Once you do that, you should be able to access samba read-write. Be aware, Windows has a lmhost.sam file by defauft, and hides the .sam extension. Editing that file will have no effect unless it is renamed to just lmhost with no extension. For example, my C:\Windows\lmhost file contains the following: 135.162.253.250 docbill002 When I want to connect via SAMBA I use the hostname not the IP address. Once you do that, write access is determined completely by Windows security= . =20 By default, only the "SharedFolders" and shared printers are writable by guests... Generally, when I want to add guest write access to a folder, I use a cygwin command. For example, I have drive Q: shared as Data. If I want guest to have write access, in addition to setting the shared folder properties I would do: chmod -R ugo+w /cygdrive/q I can than modify \\docbill002\Data as guest as much as I want. Maybe someone on the list can specify the non-cygwin equivalent of this com= mand. Bill