VirtualBox

Ticket #313 (closed defect: fixed)

Opened 7 years ago

Last modified 4 years ago

Shared folder not accesible from Windows XP

Reported by: markba Owned by:
Priority: major Component: shared folders
Version: VirtualBox 1.3.8 Keywords: shared folders
Cc: Guest type: Windows
Host type: other

Description

When using Windows XP as guest, shared folder cannot be accessed. When browsing with Windows Explorer, "VirtualBox Shared Folders" is visible, but cannot be opened/has no content.

Host: Ubuntu Feisty, VirtualBox 1.3.8 Guest: Windows XP SP2, Guest Additions 1.3.8 installed

Also tested with Windows XP with no result either. See discussion:  http://www.virtualbox.org/discussion/1/694

Ticket #27 ( http://www.virtualbox.org/ticket/27) describes similar behaviour, but reports that this could be solved when logging in as administrator. Tried this, with no effect.

Change History

comment:1 Changed 7 years ago by michael

Just to check: did you follow the instructions in the user manual precisely? (UserManual.pdf in the VirtualBox installation folder, also accessible from the main VirtualBox window using the help menu). Please note that shared folders are not browsable in Windows.

comment:2 Changed 7 years ago by markba

Well, not quite. I skipped the 'net use' part because I was under the impression that browsing (via the Windows Explorer) to the shared folder seems to be the most logical way. I check using 'net use' later and I'll get back to you.

comment:3 Changed 7 years ago by markba

If this works, I should change the bug title: "Make shared folders browsable in Windows" and this should be a feature enhancement.

In my view, it's not enough to point out to the manual, because this confuses users (see afore mentioned discussion thread). Folder "VirtualBox Shared Folders" should be either removed (apparently this folder always stays empty) or populated.

In my opinion, populating "VirtualBox Shared Folders" can (further) enhance the usability of VirtualBox because users (including me) expect this to be and should be the first choice.

comment:4 Changed 7 years ago by NicoMey

I have the same problem.
I read the user manual and tried "net use x: \10.0.2.2\test" but always get a "system error 53" (network path not found).
By the way: I have to use the direct ip adress, because the hostname "vboxsrv" couldn't be resolved.

comment:5 Changed 7 years ago by michael

You are misspelling "vboxsvr".

comment:6 Changed 7 years ago by khellman

Debian lenny 2.6.18 Windows XP Home with VirtualBox 1.3.8

I had similar problems. Followed the user manual instructions precisely, but net use w:\vboxsvr\WindowsShare wouldn't connect.

I bounced the /etc/init.d/vboxdrv service and all was well.

I thought this was the most pertinent bug for this observation to be recorded.

comment:7 Changed 7 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in 1.4.0.

comment:8 Changed 6 years ago by hari

  • Status changed from closed to reopened
  • Resolution fixed deleted

Why is this ticket closed? The problem still remains with Ubuntu Hardy Heron (8.04.1) and VirtualBox 1.6.4.

comment:9 Changed 6 years ago by j1kk3

Hi, the problem seems to be in the VBoxGuestAdditons 1.6.2 and 1.6.4 at least. See  http://wvarner.blogspot.com/2008/08/virtualbox-164-folders-does-not-work.html for a workaround (install VBoxGuesAdditions 1.6.0) until this is fixed. Worked for me (VBox 1.6.4, Hardy & XP).

comment:10 Changed 6 years ago by frank

  • Component changed from other to shared folders
  • Guest type changed from other to Windows

comment:11 follow-up: ↓ 12 Changed 6 years ago by andykant

This also occurs in VBox 1.6.4 for OS X. I have created three separate XP VM's (converted from the IE6/IE7/IE8 Virtual PC test images created by Microsoft), two of the three VM's had the "VirtualBox Guest Additions Service" fail to install. The two that failed were the IE7 and IE8 images.

The workaround that j1kk3 posted worked for me (which doesn't seem to install services so the change to using services must be where the problem comes).

comment:12 in reply to: ↑ 11 Changed 6 years ago by g3ck0

a workaround for this problem: create a hostinterface for a machine und define a (new) network adapter which is connected with the hostinterface. then you can use the network to exchange data.

testet on: virtualbox 1.6.6 host: windows xp prof (sp3) machine: windows xp prof (sp3)

comment:13 follow-up: ↓ 14 Changed 5 years ago by thedigitalhobo

can you explain that in more detail? i'm just utterly lost in creating shared folder between an XP Pro SP3 machine and the same OS as the guest.

comment:14 in reply to: ↑ 13 Changed 5 years ago by g3ck0

unfortunately i can't show you a screenshot. i hope you understand my explanation! i also explain it for version 2.04 because i have updatet it. i think it will do the same.

when you change the settings of a virtual machine then you have to select the network. there you can define a hostinterface over which your virtual machine can communicate with your host-os. the last step ist to define a network-adapter and set the Attached to to Host Interface. now you can start the virtual machine and use the established network for your data exchange.

one more thing: you have to set a ip for the virtual host interface (in your host-os) and in the virtual machine. not till then the two os can communicate.

comment:15 Changed 4 years ago by sunlover

  • Status changed from reopened to closed
  • Resolution set to fixed

Should be fixed in latest VBox versions. Please use VirtualBox 3.0.12 or 3.1 beta (  http://forums.virtualbox.org/viewtopic.php?f=15&t=24827 ).

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use