You might want to use NAT networking instead of bridged networking. Networking can be fidgety sometimes when working with VMWare or any other virtualization software for that matter.-Shades
Really? Granted I'm not that familiar with VMware as I've always used the MS (Virtual PC/Hyper-V) offering. But for a cursory search it appears that VMware's "bridged networking" is equivalent to Hyper-V's "Shared Virtual Switch", which I've used extensively. Our productions systems have 20 virtual servers running on a virtual switch, some of which have public IPs and some are behind the router's NAT ...(yes, that is two different virtual switched)... and I've never had a problem with any of it.
Now granted this could be a VMware quirk I'm unaware of (I am honestly curious about this), but it seems to me - from a networking standpoint - that having the route to a hosted service double NAT'ed would be much more problematic to maintain.
The error description is not too clear. Are you very sure nothing else is blocking the port(s) required by Owncloud/IIS?-Shades
I was actually headed here myself being that 8080 probably is not allowed by the Windows firewall by default. Also if for some reason they have a port hardcoded somewhere in the code it could be failing to find itself for that functionality. Page refresh and a netstat -n on the server might bring that to light.
------------------------------------------------------------------------------------------------------------
@SuperboyAC - Please keep in mind that anything I say in here going forward will be tainted by my prejudicial assertion that Apache does not belong on Windows. Having spent the last decade as an IIS admin, I just wanted to be fair coming out of the gate in case anyone ends up geting that impression later on in the thread.
