I have setup samba(file and print sharing) for KVM i will include the
information in case it is useful. In this setup i have two network cards
one for the external network, and one for a LAN. The LAN is bridged with
the KVM network. The samba is then shared for the bridge. 

smb.conf
---------------------------------------------
[global]
	workgroup = afafa
	server string = Samba Server Version %v
	interfaces = lo, br0
	bind interfaces only = Yes
	log file = /var/log/samba/log.%m
	max log size = 50

[samba_share]
	path = /afaf/afadfd/afaf
	valid users = afdsa
	read only = No

[printers]
	comment = All Printers
	path = /var/spool/samba
	printable = Yes
-----------------------------------------------------

I created the user with the comand 

pdbedit -a -u jon

And i allowed samba to pass through the firewall.

On I side note for the file share to work, need to change the SELINUX
settings.

jon

On Wed, 2011-07-20 at 17:13 -0700, Yasha Karant wrote:
> Has anyone successfully made samba work using the vboxnet virtual 
> internal LAN of VirtualBox to allow a MS Win client to print to the 
> Linux CUPS printer under SL 6?
> 
> If so, I greatly would appreciate a copy of your samba configuration file.
> 
> With my configuration file, I get errors such as:
> 
> Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.4-68.el6_0.2]
> tree connect failed: NT_STATUS_LOGON_FAILURE
> 
> using smbclient from the linux side.  This failure also happens when I 
> use 127.0.0.1 as the allowed IP address (ifconfig -a shows lo on this 
> address), not just the IP of vboxnet0 that does not exist except when 
> VirtualBox is running a guest OS.
> 
> Also, if you have had success, how did you setup the password file for 
> samba in terms of encryption, password program, etc.?  I have attempted 
> to use both swat and webmin, as well as manual editing, but still cannot 
> get samba to work.  Note that I do NOT want samba on any external IP 
> address, but only on an internal network.
> 
> I had gotten samba to work with VMWare a number of years ago, but my 
> notes from that epoch are not solving the current problems.  For lack of 
> licensing funding, I cannot run VMWare workstation at this time.
> 
> Yasha Karant