• 0

VMware Player 5 & Debian 7 NGINX


Go to solution Solved by ichi,

Question

Class

Hello!

 

I would like ask, since I'm pretty unfamiliar with the VMware Player 5. I just injected a virtual machine (.vmdk), with Debian 7 & NGINX, PHP and fastCGI running on it. I want to test out some websites, etc on this virtual server. Currently I have it bridged to the host, and my question is how can I access pages served by this virtual web server on the host (Win7)?

 

I think the main problem is that I don't know VMware works. Is there any settings, config which I missed?

 

Thanks in advance.

 

PS: at the moment of screenshot ETH was turned of, due to I know know, NAT or bridges is the proper solution.

post-121358-0-75086100-1393338258.png

Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0
ichi

Ah, so bridged is the answer. But sadly my network does not allow bridged VM-s, so this not possible. Sadly, while I messed around yesterday I somehow figured this out, coz with bridged I get dropped from my network. :(

 

BTW - I'm not using VMware Player that often to be honest, so yeah, installed it more then 1 years ago, then 5 was the newest version, and since the update function is blocked by my proxy service. But to be asking the right questions: Is 6 better then 5?

 

If you can't use bridged (or even NAT) and also you only need to access the VM from the host machine, then setting it as host-only will do. You'll be able to connect to the VM through the private network.

 

VMware Player 6 is obviously better... it has a "6" on the box  :D well it actually has better support for newer OS versions and hardware, and some extra features and performance improvements.

You might not notice any of that but it certainly isn't worse than 5 anyway, and being free it doesn't hurt to upgrade.

Link to post
Share on other sites
  • 0
+BudMan

If it was bridged to your host then your VM network interface should have an IP on your hosts network.. From what you show there is no IP address on the VMs eth0 - so no your not going to be able to access anything on that vm over a network.

 

BTW - something I never understand why would you be using player 5 - 6 has been out for quite some time.  Its not like it not free and you don't want to pay for the upgrade ;)

  • Like 1
Link to post
Share on other sites
  • 0
Class

If it was bridged to your host then your VM network interface should have an IP on your hosts network.. From what you show there is no IP address on the VMs eth0 - so no your not going to be able to access anything on that vm over a network.

 

BTW - something I never understand why would you be using player 5 - 6 has been out for quite some time.  Its not like it not free and you don't want to pay for the upgrade ;)

 

Ah, so bridged is the answer. But sadly my network does not allow bridged VM-s, so this not possible. Sadly, while I messed around yesterday I somehow figured this out, coz with bridged I get dropped from my network. :(

 

BTW - I'm not using VMware Player that often to be honest, so yeah, installed it more then 1 years ago, then 5 was the newest version, and since the update function is blocked by my proxy service. But to be asking the right questions: Is 6 better then 5?

Link to post
Share on other sites
  • 0
Class

If you can't use bridged (or even NAT) and also you only need to access the VM from the host machine, then setting it as host-only will do. You'll be able to connect to the VM through the private network.

 

VMware Player 6 is obviously better... it has a "6" on the box  :D well it actually has better support for newer OS versions and hardware, and some extra features and performance improvements.

You might not notice any of that but it certainly isn't worse than 5 anyway, and being free it doesn't hurt to upgrade.

 

Well, upgrade has to wait.

 

So, I started the host only connection, but, since obviously 192.168.xxx.yyy that was choosen by default wasn't really the right IP since there is actually a PC in my host network that runs with that. So now I tried to choose and IP address that is most likely not in my network and is fairly extreme: 1.1.1.1

 

Can I access this VM address in a browser, without interrupting my real networks connectivity?

post-121358-0-96936200-1393416494.png

Link to post
Share on other sites
  • 0
+BudMan

"Ah, so bridged is the answer. But sadly my network does not allow bridged VM-s"

 

And what network is that??  That makes Zero sense - its your machine right, how is it not your network?  Are you at a school or something?

 

Installed a Year ago and your just now trying to use a vm on it?

Link to post
Share on other sites
  • 0
ichi

Well, upgrade has to wait.

 

So, I started the host only connection, but, since obviously 192.168.xxx.yyy that was choosen by default wasn't really the right IP since there is actually a PC in my host network that runs with that. So now I tried to choose and IP address that is most likely not in my network and is fairly extreme: 1.1.1.1

 

Can I access this VM address in a browser, without interrupting my real networks connectivity?

 

192.168.x.x not being the right IP is not obvious at all, that depends on your network's mask. 

Your network is probably 192.168.0.x or 192.168.1.x with a 255.255.255.0 netmask, while the VM should have a 192.168.122.x IP (or similar).

 

Check you host's network configuration, you should have at least one virtual adapter there (likely vmnet0) with an assigned IP address. If you configure your VM's network adapter as NAT or host-only it should have an IP address in the same network as the host's vmnetx.

 

If VMware is assigning IPs in the range of your actual network to the virtual adapters then something's wrong with your VMware Player install.

Link to post
Share on other sites
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Copernic
      VirtualBox 6.1.22
      by Razvan Serea



      VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software.

      Some of the features of VirtualBox are:

      Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 6.1.22 changelog:

      VMM: Improved performance of 64-bit Windows and Solaris guests when Hyper-V is used on recent Windows 10 hosts VMM: Fixed frequent crashes of 64-bit Windows Vista and Server 2003 guests when Hyper-V is used GUI: Fixed regression where user was not able to save unset default shortcuts (bug #20305) Storage: Fixed regression in LsiLogic SAS controller emulation caused VM crash (bug #20323) Linux Guest Additions: Fixed issue when it was not possible to run executables from mounted share (bug #20320) Download: VirtualBox 6.1.22 | 103.0 MB (Open Source)
      Download: VirtualBox 6.1.22 Extension Pack | 10.6 MB
      View: VirtualBox Home Page | VirtualBox Screenshot

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Copernic
      VirtualBox 6.1.20
      by Razvan Serea



      VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software.

      Some of the features of VirtualBox are:

      Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 6.1.20 changelog:



      VMM: Fixed extremely poor VM performance depending on the timing of various actions (regression in 6.1.0) VMM: Fixed guest OS hanging under certain circumstances when Hyper-V is present (bug #20141) VMM: Fixed Guru Meditation error when using a nested hypervisor under certain circumstances (bug #20175) VMM: Fixed a SMAP related host panic affecting Solaris 11.4 systems with Intel Haswell CPUs or later (bug #16068) OCI: Add cloud-init support for export to OCI and for OCI instance creation GUI: Fixed "Delete all files" leaving behind Logs/VBoxUI.log (bug #20235) Audio: Multiple fixes and enhancements Audio: Fixed detection of duplex audio devices on macOS (5.0 regression; bug #20171) Network: Fixed link status reporting for "not attached" adapters Network: Fixed connectivity issues with e1000 in OS/2 guests (6.1.18 regression; bug #20148) Network: Fixed VxWorks e1000 driver compatibility issue (bug #20182) Network: Fixed GUI checks for port forwarding rules rejecting IPv6 with "Nat Network" (bug #14847) DHCP: Don't crash in the presence of fixed address assignments (bug #20128) Serial: Fixed possible VM hang when using the a serial port in disconnected mode (bug #19854) Webcam: Fixed interoperability with v4l2loopback and fixed a crash under certain circumstances (bug #20176) NVMe: Fixed sporadic Windows VM hang or reboot on high CPU load VBoxManage: Allow changing network adapter attachment of a saved VM with "modifyvm" vboximg-mount: Fix for argument processing to honor the '--root' option (6.0 regression; bug #20073) Linux host and guest: Support kernel versions 5.11 (bug #20198) and 5.12 Linux host: Maximum MTU size increased to 16110 for host-only adapters on Linux kernels 4.10+ (bug #19122) Linux Guest Additions: Fix vboxvideo module compilation for kernel version 5.10.x Linux Guest Additions: Fixed kernel module build for RHEL 8.4 beta and CentOS Stream (bug #20289) Download: VirtualBox 6.1.20 | 103.0 MB (Open Source)
      Download: VirtualBox 6.1.20 Extension Pack | 10.6 MB
      View: VirtualBox Home Page | VirtualBox Screenshot

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Copernic
      VMware Workstation Player 16.1.1
      by Razvan Serea



      VMware Player is the easiest way to run multiple operating systems at the same time on your computer.
      With its user-friendly interface, VMware Player makes it effortless for anyone to try out Windows 10, Chrome OS or the latest Linux releases, or to create virtual "sandboxes" to test pre-release software in. VMware Player can also be used to run a virtual copy of an old PC so that you can recycle the old machines you have under your desk or stored in the closet.

      Run multiple operating systems simultaneously on a single computer Experience the benefits of preconfigured products without any installation or configuration hassles Share data between host computer and virtual machine Run 32- and 64-bit virtual machines Use 3rd-party pre-configured virtual machines and images Share data between the host computer and virtual machine Broad host and guest operating system support Support for USB 2.0 devices Gain easy access to virtual machines via an intuitive home page interface VMware Workstation Player 16.1.1 fixes:

      In this release of VMware Workstation Player, the VMNet driver related security improvements as suggested by BoB driverThru have been implemented. Resolved Issues:

      Microsoft console debugger is included in OVFTool in VMware Workstation - The functionality provided by Microsoft console debugger has been changed and Microsoft console debugger is no longer included with Workstation distribution. This issue is resolved. Download: VMware Workstation Player 16.1.1 | 215.0 MB (Free for personal use)
      View: VMware Player Website

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Copernic
      VMware Workstation Pro 16.1.1
      by Razvan Serea



      VMware Workstation provides a seamless way to access all of the virtual machines you need, regardless of where they are running. Remotely connect to virtual machines running on VMware vSphere, ESXi or another copy of VMware Workstation. Workstation’s web interface lets you access local and server hosted virtual machines from your PC, smart phone, tablet or any device with a modern browser. Run applications on multiple operating systems including Linux, Windows and more at the same time on the same PC without rebooting. Evaluate and test new operating systems, applications and patches in an isolated environment.

      Take Your Productivity to the Next Level

      Run applications on multiple operating systems including Linux, Windows and more at the same time on the same PC without rebooting. Evaluate and test new operating systems, applications and patches in an isolated environment. Demonstrate complex software applications on a single laptop in a repeatable, reliable manner. Consolidate multiple computers running web servers, database servers, etc. onto a single machine. Build reference architectures for evaluation before deploying into production. Simply drag and drop to move your virtual machines from your PC to vSphere, or the cloud. VMware Workstation Pro 16.1.1 fixes:

      In this release of VMware Workstation Pro, the VMNet driver related security improvements as suggested by BoB driverThru have been implemented. Product Support Notices:

      Deprecation of the Shared virtual machine feature - The Shared virtual machine feature (VMware Workstation as server) is being deprecated. It will remain in its present form for the remainder of the VMware Workstation 16 product life. This feature will be not available in a future release. Resolved Issues:

      Microsoft console debugger is included in OVFTool in VMware Workstation - The functionality provided by Microsoft console debugger has been changed and Microsoft console debugger is no longer included with Workstation distribution. This issue is resolved. Download: VMware Workstation Pro 16.1.1 | 622.0 MB (Shareware)
      View: VMware Website

      Get alerted to all of our Software updates on Twitter at @NeowinSoftware

    • By Usama Jawad96
      Microsoft: Customer data was not accessed in Solorigate attack
      by Usama Jawad

      In 2020, there was a major global cyberattack, spanning across the United States' federal departments, the UK, the European Parliament, and thousands of other organizations. It was reported to have been triggered by supply chain attacks on three major firms: SolarWinds, Microsoft, and VMware, where attackers were able to access private documents and emails. The attack was dubbed "Solorigate" by Microsoft with President Brad Smith calling it "a moment of reckoning". Now, the company has shared a final update on its Solorigate investigation.

      Image via Splashtop Microsoft Corporate Vice President of Security, Compliance, and Identity Vasu Jakkal has concluded that while nation-state actors were able to compromise some initial security procedures, they were then stopped by a "unified team of human and digital defenders". She also clarified that the company has found no proof of customer data or production services being breached. Furthermore, the investigation confirmed that Microsoft software was not used to attack other identities.

      Microsoft states that multiple factors aided in limiting the scope of this attack and these should be embraced by other security teams and organizations moving forward as well. These include adopting a Zero Trust security model with multi-factor authentication for credentials, and cloud technologies like Azure Active Directory and Microsoft 365 Defender. Lastly, Jakkal has emphasized that it is paramount that companies and teams work together to strengthen collective defenses.

      The Microsoft Security Response Center (MSRC) went on to say that:

      MSRC highlighted that even though the attack was discovered in December 2020 with organizations racing to mitigate the threat, its analysis shows that the malicious actor attempted access in January 2021 as well. It has clarified that across all of its services, the attacker was able to view and download only a small number of code files for Azure, Intune, and Exchange. None of the code files breached contained any live credentials being used in production environments.