Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Client is mac osx running VMware Fusion. Virtual machine is Fedora. Apache is configured and running. The actual site content is stored in a shared folder between the mac and the VM. In the mac terminal I can ping the domain name (which is configured to route back to the internal IP using the hosts file), and the IP directly, however cannot view the site in browser, nor get the standard apache "it works" page, but a time out. Tried from the mac terminal to telenet on port 80, time out again. Have checked firewall settings.

Any ideas or thoughts welcome.

If further clarification is needed I will provide as I can. I have to confess I currently am only learning this stuff so may have missed something seemingly obvious, but our server guys have looked over this and can't figure out the problem, althought haven't been able to have direct access to the mac but have accessed the virtual machine terminal via reverse ssh.

Thanks in advance

share|improve this question

closed as not a real question by MDMarra, Chris S, Holocryptic, Zoredache, mailq Dec 9 '11 at 21:44

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

I'm trying to get my head around your configuration. Is the IP address you see on the Fedora host the same IP that the domain name resolves to when you ping it? – Jason Tan Aug 14 '10 at 13:18
@Jason. Yes the domain resolves to the correct IP. – Relequestual Aug 16 '10 at 13:30
Currently had to put this problem down and work on other projects for the next 2 weeks, so won't be able to confirm a solution for at least 2-3 weeks. Cheers. – Relequestual Aug 16 '10 at 13:31

Can the VM ping outward to the rest of the network? If so, you might consider verifying the NIC type and ensuring it is set for what you desire (NAT versus bridged).

share|improve this answer
yup the VM can ping outward to the rest of the world. How would I go about verifying the NIC type? I'm not sure how it was configured in the first place. – Relequestual Aug 16 '10 at 13:27
"IP of the VM is" that sounds like it is in NAT mode under VMWare. You should be able to change that within the VM's definition/configuration profile under the "Networking" section/configuration to "bridged" in order to enable true/full two-way communications to/with the VM. – user48838 Aug 17 '10 at 7:24

1)What is the ip address of your virtual machine?

2)What is the ip address of your workstation?

If you want to access to a Web Server of a Virtual Machine, you first need to succesfully ping the virtual machine.

The default NIC setting for a VMWare Fusion virtual Machine is NAT then you need to add a static route for arrive to this machine, or more simply you can change the NIC adapter of your Virtual Machine to Bridge mode, then you have your virtual machine in your real ethernet LAN network and you can access it as any other machine in your network...

Check also the firewall in fedora for allowing connection on port 80...

share|improve this answer
IP of the VM is Can ping in both directions. Did state I could ping the VM in my question. I will have a look around at the NIC options for VMWare Fusion. Cheers – Relequestual Aug 16 '10 at 13:29

Not the answer you're looking for? Browse other questions tagged or ask your own question.