Tag Info

New answers tagged

0

Try to disable the Floppy Disk Controller in the VM's BIOS. Anyway, why do you edit your VMs by hand? Don't do this. A kitten is harmed every time you edit a VMX file by hand.


0

Is FreeBSD firewall allowing EXTERNAL connections on port 80? You have not specified that you've checked this in your question. Also make sure you have bind your server not only to localhost:80, but to 192.168.0.13:80 or *:80 in general as well


2

If you're installing any OS in 2014 on modern hardware without 64-bit capabilities, you're making a bad design decision. Even with the hardware RAM/CPU footprint you're describing for your VMware Workstation setup, it makes sense to utilize 64-bit versions of your operating system for forward compatibility, future-proofing and the very clear requirement ...


-2

64bit is slower and takes more RAM than 32 bit. 64bit addresses larger than 4GB RAM faster than 32bit can address it (and more smoothly). Individual programs can address more RAM natively on a 64bit system. As you already know you can't run a 64bit guest on a 32bit system. Updated for your comment below: My answer above was giving a 'vs' answer because ...


1

Thanks for information above - this is what worked for me for Windows 2003: Uninstall VMWare tools when booted in VMWare workstation (I didn't do this on first attempt and I had problems with some services not starting and I was unable to remove VMWare tools when booted under Virtual Box) Combined vmdk file into 1 file (as vmdk had been created with ...


5

You can use nmcli & nmtui If you are using "minimal installation" then all other rpm for web development you need to install separately. For status of your nic /ip as follow ip a sh This is how all servers should be setup. Absolutely bare bones and then add only the services/applications that define its role.


1

I could not use the host's Cntlm server in the client because I was using the wrong source IP address. If VMware is using NAT (which is how my virtual machine is configured), Cntlm has to listen to the host's IP address in the virtual VMware network, not to the host's IP in the corporate network. The following commands were executed on the host. $> ...


0

If you are using Virtualbox then you need to add the extension. The extension enables the PXE lib from intel. Plus extra USB features. You also need to make sure that the connection type is bridged (for direct access to network). I had some issues with having a connection without having it bridged. Go here: https://www.virtualbox.org/wiki/Downloads and ...


0

Create a backup of file /etc/sysconfig/iptables (in case you screw it up) Edit file /etc/sysconfig/iptables Copy the line for SSH (port 22) and paste below this line. Add the port 80 or any other port you want to the new line. Save the file Note: BE VERY CAREFUL EDITING THIS FILE!!!


3

You probably used iptables -A you should have used iptables -I. As a default, CentOS has drop rule at the end of the INPUT chain, -A puts a rule at the end of a chain after the drop so kit never gets evalated. You should go read some documentation on the tools you're attempting to use, it's not as easy as it looks.


1

1.Enable promiscuous mode vmware If you want all users to be able to set the virtual Ethernet adapter (/dev/vmnet0 in our example) to promiscuous mode, run the following command on the host operating system as root: chmod a+rw /dev/vmnet* To grant selected other users read and write access to the VMnet device, you can create a new group, add the ...



Top 50 recent answers are included