It happens to everyone in this industry. “We need this done RFN!” is the message you get so when things don’t work the first time, the next instinct is to revert back to old ways.
For me, this was the case when I wanted to test sites I was developing in MAMP in Windows browsers. I tried the whole dyndns thing that the user manual outlines, but it didn’t work as I have a shared external IP. I reverted back to my old ways and set up websites on a subdomain of this one for testing. It was a huge pain when changes had to be done and tested quickly since I was constantly FTPing files and importing and exporting databases.
Today I listened to my inner diva (she often complains about doing tedious work) and figured it out, after over three months of doing it the hard way.
- Check your System Preferences > Sharing settings and ensure that Web Sharing is off. You might also want to check your Firewall settings and allow connections for MAMP.

- In VMWare Fusion, set your Network settings to Bridged. This will make it as if your VM and your Mac are peers but won’t restrict your access to external sites on your VM.

- Check your MAMP ports. I went with the MAMP ports 8888 and 8889. You will need this for when you access your site from your VM.

- Edit your hosts file on your Windows VM. Your hosts file is typically here: C:\WINDOWS\system32\drivers\etc and contains mappings. I entered my IP followed by the local name of my website, i.e. if I access my site through http://intactgrowth:8888 on my Mac, “intactgrowth” follows my IP in the hosts file.
That should be it. Much simpler and better than my other idea, which was to download Wamp on my VMs and share my code between two computers (this would’ve meant lots of DB work as well).
It's tough to think of a blurb for myself when I'm also on