When i make a team from these 4 VMs…………& set up a LAN the configuration comes to choose a network adapter…..

1> Should i make a new LAN or choose my deault
onboard NIC to get the same bandwidth speed across all my VMs ?

2> Will i have to manually set up IP addresses & Mach addresses to individual VMs ?

I’ve already configured under network editor that my onboard NIC [ Realtek ] as Bridged.

What i don’t get is …. how can i come up with a concept of a virtual switch ? If a virtual switch can be configured under workstation then my prob will be solved ,……… as it will behave exactly like a physical switch in real world.

Thus enabling us to virtually access the same bandwith & not a shared connection between all the VMs.

my host OS is Windows 7 x86
Total RAM 8 GB DDR3 Corsair
core 2 quad 2.96 ghz……
intel VT is present in my board which is Intel DX58SO

Anyways, doesn’t VirtualBox provide DHCP services for virtual machines?

I have Virtual Machine running Window XP Pro 32bit on a host: Windows 7 Pro 64bit.

I need this Virtual Machine to use and publish the actual MAC address of the NIC that’s installed in my host machine. It’s a second card, not used by my host machine. The virtual machine seems to report a made-up MAC. The software I’m trying to run checks the MAC of the NIC for which the software is licensed for. If it’s not the actuall MAC of that NIC, it won’t run.

Help!!!!

Thanks,
Ty

any tutorial or web link that helpful for me.thanks for advanced.

any tutorial or web link that helpful for me.thanks for advanced.

First, since you aren’t running the samba server, I doubt that your samba configuration file is doing anything. You could test this by getting your share mounted and working with it in place and then renaming it to something else, reboot, and do the same things you did before. If it is, in fact, being read, the netbios name parameter appears to be wrong. This would normally be the name of the samba server (i.e. the name of the machine the smb.conf file is on) and therefore would be the name the samba server (which you are not running) would broadcast via netbios to the rest of the workgroup and would respond to when a client on another machine attempted to access samba shares on the server. Since you are not running the server nor sharing anything with the rest of the network, using the same name your Windows machine would already be using via netbios is probably not an issue. It probably will be if you ever start the server, however.

The whole “usershare” feature which your configuration file is configuring is about individual users (as opposed to root) being able to dynamically share folders with other machines on the network, and requires the server to be running to work. It doesn’t have anything to do with accessing shares on other machines so, again, I suspect that the smb.conf file is not playing any role in getting your mount to work.

All in all, these are minor and inconsequential in your scenario but I thought it worth saying something since someone might look at your article and try to apply the principles to another scenario where they might not be so lucky.

One more thing, a bit of speculation as to the reasons for your needing to ping the machine to get the reverse-ping (and sharing) working, I think one possibility is that it is due to you not running the server. Since the Samba server uses the same protocols as Windows to try and look like just another Windows machine on the network, smbfs may be relying on the server to negotiate the link. That seems unlikely, though, since I suspect that smbfs was meant to stand alone without the server. Another possibility is that it is due to the fact that smbfs has been deprecated in favor of the cifs protocol which is apparently, much the same thing but is the result of Microsoft expanding its smb protocol somewhat to work beyond Windows (so that it could be used over the web). Since Vista is, so far, the latest release of Windows, its possible that it doesn’t work as well with smbfs, the older protocol. Finally, it may just be due to Windows’ firewall — it may have ignored your unsolicited pings but accepted them once Windows had initiated a connection with the machine.

Thanks for all the great articles.

- Les

Wonderful…I am searching for this from past 2 days…
atlast i got it in your blog ….
great presentation ……… helps a lot for me…

Thanks So much….
Nagababu

Excellent article. Thanks a lot.
This is really very helpful for my new setup…

Thanks,
Nagababu