qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Doctor Bill <docbill@gmail.com>
To: qemu-devel@nongnu.org, Francois Rioux <francoisrioux@yahoo.com>
Subject: Re: [Qemu-devel] Read/Write to shares on Windows (XP Pro) host from Windows (2000 Adv) guest.
Date: Thu, 25 Aug 2005 08:35:22 -0400	[thread overview]
Message-ID: <23bcb870050825053511c0f8f2@mail.gmail.com> (raw)
In-Reply-To: <20050825022312.75483.qmail@web50509.mail.yahoo.com>

On 8/24/05, Francois Rioux <francoisrioux@yahoo.com> wrote:
> What I manage to do with a certain success is to map network shares of the
> host in the guest (net use z: 10.0.2.2\MyShare in the guest).  I can browse
> and read files from the mapped drive.  However I can't write to it from the
> guest. I received an Access Denied message instead even if the share is set
> so Everyone has Full Control.
>  
> I don't understand why this doesn't work. Is it Windows preventing the write
> is the exchange this a limitation in QEMU or in SLiRP?  As I understand it
> SLiRP translates some tcp headers and acts as a firewall preventing incoming
> 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?  Is
> the network file sharing protocol more complex than that for writes? Or is
> that rather a Windows security issue? 
>   
> Any explanation or workaround would be appreciated. 

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.  

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 command.


Bill

      parent reply	other threads:[~2005-08-25 12:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 13:28 [Qemu-devel] DMA in Windows 2000/XP/2003 Víctor Córcoles López
2005-08-23 23:47 ` Kazu
2005-08-29  6:56   ` Brad Campbell
2005-08-29 17:10     ` Christian MICHON
2005-08-24 12:56 ` Jan Marten Simons
2005-08-24 15:03   ` André Braga
2005-08-25  2:23     ` [Qemu-devel] Read/Write to shares on Windows (XP Pro) host from Windows (2000 Adv) guest Francois Rioux
2005-08-25  3:20       ` Jim C. Brown
2005-08-25  4:26       ` John R. Hogerhuis
2005-08-25  6:38       ` [Qemu-devel] Read/Write to shares on Windows (XP Pro) host fromWindows " Kazu
2005-08-25 17:35         ` Francois Rioux
2005-08-25 17:35         ` Francois Rioux
2005-08-25 12:35       ` Doctor Bill [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23bcb870050825053511c0f8f2@mail.gmail.com \
    --to=docbill@gmail.com \
    --cc=francoisrioux@yahoo.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).