Also, accessing services in a Virtual Machine is basically no different then a Physical Machine and the same basic networking protocols and methodologies apply to both so act accordingly. That said there are some things to be aware of in that if the Host is physically actively multihomed then you need to configure the Automatic Bridging Settings as shown in the image below clicking on the Configure Adapters button.
Additionally, in VMware Player 5 if you what to access the full fledged Virtual Network Editor in an officially undocumented manner then in an Administrative Command Prompt set to VMware Player's working directory use the following command.
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone
(Click image to enlarge.)
Image may be NSFW.
Clik here to view.
For Documentation reference to the image above, from the VMware Player 5.0 Release Notes:
Ability to Configure Network Adapters
Previously, the standalone version of VMware Player did not give users a way to select what adapter would be used for a virtual machine. With standalone VMware Player, from the menu bar, you can now select VM > Settings > Network, and use the button next to "Bridged" that says "Configure Adapters."
If you launched VMware Player without admin privileges, the button displays a UAC shield. You can click the button and respond to the UAC prompt. This button displays a dialog box for specifying which adapters can be used for automatic bridging. This is the same dialog box currently used in Workstation, in the Virtual Network Editor, under Bridged > Automatic Settings.
