Download sound card drivers or install DriverPack Solution software for driver scan and update. RDP from the same windows machine to the VBox remote display - DOES NOT get sound installed a local sound card on the server and was able to have the windows 7 guest to play sound on it using ALSA interface, however, when using pulseaudio driver - no sound from the guest going to the local card (paplay did play sounds to the local sound card on.

Oracle VM VirtualBox gives you several options to configure networking of your virtual machines. Every Virtual Machine in your VirtualBox can have up to 8 network adapters and these network adapter can be any of the following six hardware types.

  • AMD PCNet PCI II (Am79C970A)
  • AMD PCNet FAST III (Am79C973) This is the default
  • Intel PRO/1000 MT Desktop (82540EM)
  • Intel PRO/1000 T Server (82543GC)
  • Intel PRO/1000 MT Server (82545EM)
  • Paravirtualized network adapter (virtio-net)

You can also configure each network adapter in your Virtual Machine to operate in one of the following modes:

  • Not Attached
  • Network Address Translation (NAT)
  • NAT Network
  • Bridged Networking
  • Internal Networking
  • Host Only Networking
  • Generic Networking

Let's look at these networking modes in detail and analyse which networking mode to use and how.

Configuring Virtual Machine Network

To configure your Virtual Machine network, Open the Virtual machine Settings and select Network

You can configure up to four network cards from Network section of the settings window. If you need to add more network cards then you can do so from command line using VBoxManage modifyvm command.

  1. To add a network adapter to your Virtual Machine just select the Enable Network Adapter check box.
  2. Depending on the networking mode that you want you can select one of the options(see Virtual Networking Modes section below) from the drop down box with the label Attached to.
  3. You may also change the adapter type, promiscuous mode policy, mac address and cable connected settings from under advanced options.

Virtual Networking Modes

Networking Modes defines the connection between - a Guest Virtual Machine and Host machine, different Guest VMs on the same Virtual Box, Guest VM and other machines on the network and Guest VMs connection to the internet. You select the networking mode by selecting one of the options from the 'Attached to' drop-down list.

Not Attached

In this mode, the network adapter will behave as if no Ethernet cable is attached to it - which means no connection.

NAT

NAT (Network Address Translation) is the default networking mode used when you create a new VM. In this mode VirtualBox uses its built-in DHCP server to assign the IP address 10.0.2.15 to VMs network adapter. When the Guest VM tries to make an outbound connection such as accessing the internet, VirtualBox will translate the IPv4 packets and from the Guest VM and forwards it to its destination and also translates response packet back to the Guest VM.

This networking mode is only used when the Guest VM acts like a client that access a public network (or internet). In this mode you cannot have Guest VM as a server or in other words you cannot initiate a SSH or telnet connection to Guest VM.

When to use NAT mode?

If all you need is internet access from your Guest VM this is the best option as it requires no additional configuration.

For example you have a Guest VM that runs a Linux or a Windows desktop operating system and you want to install additional packages / upgrades etc.,

Do no use NAT mode if the Guest VM runs in server mode (Web server, FTP server etc) as you cannot initiate a connection to the VM.

NAT with Port Forwarding

The main drawback of NAT is that you cannot connect to the Guest VM from another machine on the network. There is a workaround to this problem - Port Forwarding. Port Forwarding will check the inbound packets and forwards it to the Guest VM based on the IP address and port numbers. The source/destination IP address and Port numbers used for Port Forwarding are defined using rules that you can create from Port Forwarding Rules window. To access this windows expand Advanced section and click Port Forwarding

In the Port Forwarding windows click on the + icon to add a new rule. For example you can add a rule which forwards all packets coming in to port 2222 of host to port 22 of Guest VM.

This rule enables you to make a SSH connection (on port 22) to Guest VM from a external machine by simply connecting to the host's IP address and port 2222.

Bridged Networking

In the Bridged networking mode, the virtual Network adapter is bridged to a physical NIC on your host so you can access your Guest VMs just as you access the host.

Media

To enable Bridged Networking, select Bridged Adapter in the Attached to drop down list and then select a host NIC from the drop down corresponding to the Name field.

When to use Bridged Networking

Use Bridged networking if you have Guest VMs that run as servers or clients and you need to make a network connection(SSH, FTP, TCP/IP etc.,) to those VMs from client PCs and other devices on your network.

One drawback with this mode of networking is that if you have multiple NICs and if you switch connections between the NICs then you have to reconfigure the bridge. For example you have a wired and wireless connection and you created the bridge initially with the Wireless adapter. If you move to a location where you do not have wireless access and you switch to a wired connection then you need to reconfigure the bridged to use the wired connection adapter.

Internal Networking

All Virtual machines in a VIrtualBox that use Internal Networking mode connects to an isolated internal network and can talk to each other. Even the Host is not connected to this private network.

Host-Only Networking

In Host-Only Networking the Host and the Guest VMs are on a private network. It is similar to Internal Networking but only difference is in this mode the Host is also connected to the internal network and can provide DHCP services to the Guest VMs.

To configure Host-Only networking you need to first create a VirtualBox Host-only Ethernet Adapter.

In the VirtualBox Manager window, Select File → Preferences. Select Network and click Host-only networks tab.

You can also edit the properties of of the Host-only adapter to set an IP address or configure DHCP

Finally from the Network Settings of the Virtual Machine you select Host-only Adapter in 'Attached to' field and the name of the adapter that you created above.

Generic Networking

Vbox Communication Sound Cards & Media Devices Driver Windows 7

This mode is very rarely used. In this mode you can create a UDP tunnel to interconnect two Virtual Machines running on different hosts or you can create VDE (Virtual Distributed Ethernet) networking which allows you to connect your VM to Virtual Distributed Ethernet switch.

If your host operating system is configured for sound, you can enable sound for a virtual machine. Currently PCM (Pulse Code Modulation) sound output and sound input are supported. That is, VMware GSX Server supports any application that produces sound without using MIDI. Synthesizer sound output, game controllers, and joysticks are not supported.

The virtual sound device is compatible with a Creative Technology Sound Blaster 16 audio device. It supports sound in Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows .NET Server and Linux guest operating systems. (See below for information on using sound in a virtual machine running Windows .NET Server or Windows XP as a guest operating system.)

The sound device is disabled by default and must be enabled in the Configuration Editor.

To enable sound support for a virtual machine:

  1. Configure sound on your host operating system. Refer to the documentation for your particular operating system for instructions.
  2. Select File > Open and open the virtual machine configuration file (.cfg) you want to modify.
  3. Select Settings > Configuration Editor from the console.
  4. From the list of devices, select Sound.
  5. Select the Start Connected option if you want the sound to be enabled when the virtual machine powers on.
  6. Under Device, enter the path to the sound device you want to use.
  7. Click Install.

Note: Your sound card must be working in your host operating system in order to use sound in the virtual machine.

If you do not have sound on your host, or if it is used by another application, an error message appears when you try to run the virtual machine and the sound device is disconnected. Use the Devices menu entry to reconnect it.

Enabling sound for guest operating systems

Cards

You must configure the guest operating system to use the VMware virtual sound device. This device is compatible with a Creative Technology Sound Blaster 16.

For Windows .NET Server and Windows XP guest operating systems:

Windows .NET Server and Windows XP do not automatically detect and install drivers for ISA sound cards, such as the Creative Sound Blaster emulated in a virtual machine. Follow these steps to configure sound in a Windows .NET Server or Windows XP guest operating system:

  1. Click the Printers and Other Hardware link in the Windows Control Panel (Start > Settings > Control Panel).
  2. In the See Also pane, click Add Hardware, then click Next.
  3. Select Yes, I have already connected the hardware, then click Next.
  4. In the Installed Hardware list, select Add a new hardware device, then click Next.
  5. Select Install the hardware that I manually select from a list (Advanced), then click Next.
  6. Select Sound, video and game controllers, then click Next.
  7. Select Creative Technology Ltd. in the Manufacturer list and Sound Blaster 16 or AWE32 or compatible (WDM) in the list of devices, then click Next.
  8. Click Next.
  9. Click Finish.

For Windows 2000 guest operating systems:

Vbox communication sound cards & media devices driver windows 7
  1. Double-click the Add/Remove icon in the Windows 2000 Control Panel.
  2. From the Add/Remove Hardware Wizard dialog box, select Add a New Device and click Next.
  3. From the Find New Hardware screen, select No, I want to select the hardware from a list and click Next.
  4. From the Hardware Type screen, select Sound, video and game controllers from the list and click Next.
  5. From the Select a Device Driver screen, select Creative from the manufacturers list and select Sound Blaster 16 or AWE32 or compatible (WDM) from the models list, then click Next.
  6. From the Start Hardware Installation screen, click Next to install the Sound Blaster 16 drivers.
  7. From the Completing the Add/Remove Hardware Wizard screen, click Finish and reboot the virtual machine. Sound should be working the next time the virtual machine's guest operating system boots.

For Windows 95 and Windows 98 guest operating systems:

Note: If you have never installed a Sound Blaster 16 Card in this Windows system previously, you need a Windows 95 or Windows 98 installation CD-ROM.

  1. Launch Add New Hardware from the Windows Control Panel.
  2. Click Next.
  3. Select Yes for Do you want Windows to search for new hardware?
  4. Click Next.
  5. Click Next again.
  6. Windows should run the auto-detection and say it is ready to finish.
  7. If prompted to do so, insert the Windows CD-ROM into the drive and click OK.
  8. Click Finish.

If you have problems with Windows auto-detection, add the device manually.

  1. Launch Add New Hardware from the Windows Control Panel.
  2. Click Next.
  3. Select No for Do you want Windows to search for new hardware?
  4. Click Next.
  5. Select Sound, video and games controllers.
  6. Click Next.
  7. Select Creative Labs Sound Blaster 16 or AWE-32.
  8. Click Next.
  9. Click Finish.

For Windows NT guest operating systems:

Note: If you have never installed a Sound Blaster 16 Card in this Windows NT system previously, you need a Windows NT 4.0 installation CD-ROM.

Vbox Communication Sound Cards & Media Devices Drivers

  1. Launch Multimedia from the Windows NT Control Panel.
  2. Click the Devices tab.
  3. Click the Add button.
  4. Select the Creative Labs Sound Blaster 1.X, Pro, 16.
  5. Click OK.
  6. Insert the Windows NT 4.0 CD-ROM in the CD-ROM drive when prompted.
  7. Specify D:I386 (or another drive if D: is not your CD-ROM drive).
  8. Click OK.
  9. Configure the Sound Blaster base I/O Address to 220.
  10. Click OK.
  11. Complete the Sound Blaster 16 Configuration.
  12. Click OK.
  13. When prompted to restart, select Restart Now.

For Linux guest operating systems:

Refer to the documentation for your particular Linux distribution. You may need to install additional software packages on your system to support sound. When configuring the sound, use the following parameters:

Vbox Communication Sound Cards & Media Devices Driver Updater

  • IO Port -- 0x220
  • IRQ -- 5
  • 8-bit DMA -- 1
  • 16-bit DMA -- 7

Vbox Communication Sound Cards & Media Devices Driver Download

Known Sound Limitations With VMware Products

  • Sound support is limited to Sound Blaster compatible PCM (Pulse Code Modulation) output. This includes the ability to play .wav, .au and Real Audio formats.
  • MIDI sound is not supported.
  • Game ports/joysticks are not currently supported.
  • Sound does not work well with several games, especially fast, interactive games.
  • VMware GSX Server does not support the DirectSound capabilities of DirectX within a virtual machine.

Troubleshooting Sound

For information on troubleshooting sound issues with VMware GSX Server, see Issues with enabling sound.

Vbox Communication Sound Cards & Media Devices Driver

Related topics:

© 2001-2002 VMware, Inc. All rights reserved.