virtualbox.org

Hi all

i am newbie to linux. Recently i have installed virtual box 2.2.2 version in my linux host ( RHEL 5 )...then i installed windows xp as a guest. I have selected bridged adapter option in settings tab. Now i can communicate to the whole network ( telnet, rlogin, ssh (using putty ) from my windows guest. But my linux host is the samba server. I cant able to see the samba share in my windows guest os. i have given a separate ip for my linux nic (eth1 ) and windows nic.
But there is no telnet, ftp connection from my guest os ( windows ) to host os ( linux )...I am very new user to virtual box and linux...I have tried a lot
and now i found this forum. Plz help me

KingstoN

Try "net use" command instead of GUI.

Disable filewall on Guest and configure file sharing.

Try some standard network troubleshooting. Can you access other machines on the network from the Guest and Host? Can the other machines access the Guest and Host? Can the Guest ping the Host and vice versa?

FIREWALL and SELINUX is disabled in my linux guest. But problem persists.

I can ping from host to guest and vice versa. But i configured samba in my linux guest. When i tried to see that on my windows host , there is nothing in "view workgroup computers"

One more thing, i shared one folder from my linux guest ( /tmp/samba ) through virtual box shared folders. Then i started my guest os ( windows ). Through command prompt i have given the following command

net use x: \\windowsxp\share (windowsxp - in guest os name and share is my shared folder)

Then it asks for the windowsxp user, i gave a valid windows user name ; then it demands for a password, i gave the proper password. Then it gives "system error 5 is occured" Access denied"

KingstoN

Shared Folders are access through the GA, then connect to \\vboxsrv\<sharename>.

What happens if you type the name of the Samba server, or it's IP address in the addressbar? Anything with that? And what about the other tests I told you?

I heard that term Guest Additions...But i didnt try that...that software has to be installed in my host os or my guest os...pls explain me...
My users are not beginners in this environment..if it is accessible in Graphical Mode than it will be better..

I can ping from my host to guest and vice versa. Its communicating with all my clients except its host. ( Telnet, ftp, rlogin and samba nothing works )

For the GA question, you might do yourself some good to check the VirtualBox FAQ and Manual . Would have saved you an embarrassing question . It's so obvious.

As for the GUI part with networking. If it's Windows, there is always a GUI option. It's called the Explorer with the Extra > Map Network Drive option. You can type the full path there, or browse the network for it.
And if the VM will be running on a different machine than the Samba server, there aren't many issues you need to fix for this, as it's currently the issue of Host <> Gues connectivity. You can try adding a NIC attached to Host Only, configure it in a different range that your own network and connect through that.

hi i have switched over to hosts only configuration....i have given a ip to the "vboxnet0" adapter in 192.168.0. series...and i have given a another in the same range for my windows guest....but still am having the same problem with my linux-windows

if anybody can tell me the basic steps to configure the bridged network between the linux host and windows xp guest.....

sorry for my english

Ok, so your Bridged worked right from the start, that's good. Now for the Host-Only network, you need to make sure that it's in a different range than your own network. The default range set in the Preferences, 192.168.56.x is fine for that, unless you happen to use that range . Now you need to make sure the IP of the Host is what you want it. Let's say it ends with .2. Now, after booting the Guest, accessing 192.168.56.2 should bring you to the Host.

will the kernel 2.6.18-8 is ok for the latest version of VBox 2.2.2 or i have to add any module for that? or is it required to upgrade my kernel to a newer version?

The kernel is pretty old, but should not be the problem. There are other reports that users were not able to access the Host through Bridged settings. To get this working properly, set the Host-Only as shown in the screenshots. If the range I used conflicts with the one on your network, you need to change it of course. This should give you access to the Host using the IP 172.25.0.1.