VMware Player works on internal network but not on public

[robmypro99]

Hey guys, I am trying to get the SourceForge Enterprise Edition 4.4 working, and it comes with VMware player. I installed it, and it works fine internally (i.e. 192.168.0.209 but I am not able to access it from outside my network. I use a service called "no ip", and can use other applications with it. But I am a bit confused as to how to configure my router to make this work. The documentation for SourceForge lists 3 ports to open and forward (22, 25, 443) so I forwarded them to 192.168.0.209. But when I access the site using my.domain.com:443 (or 22/25) the site is not found.

I have never tried doing this with vmware, so maybe it is something basic. Anyone have any ideas? BTW, the OS for SourceForge is CentOS. Again, it all works fine using 192.168.0.209 on my internal network.

Thanks for the help guys.

[continuum]

Hi and welcome

please run vmnetcfg.exe and post a screenshot.
Also we need to know how the network card of the VM is configured. Bridged, vmnet1 or vmnet8 ?

how many nics does your host have ?

[robmypro99]

Thanks for the help! I didn't find vmnetcfg.exe so where can I get this from? It wasn't in the vmware player folders. I have the network configured for Bridged, and I have 2 network cards, although one is disabled.

[continuum]

that will not work

you must run the setup again - from a cmd

VMware-player-3.1.3-324285.exe /e tempdir

then find network.cab in tempdir and extract it with 7zip,rar or your  favorite tool

then you find a vmnetcfg.exe that needs to be copied to  the installatio directory

[robmypro99]

Here is the screen shot...

[continuum]

good
now select vmnet0 and then in the dropdown select a networkcard of your host.

when that is done the network becomes predictable

[robmypro99]

Okay I have done that. What should I do next?

[continuum]

we do not know how your network is configured

if you post ipconfig /all from host  and tell us what the VM uses "vmnet0, vmnet1 or vmnet8 we can tell you more

[robmypro99]

Here is a screen shot from the host.

[robmypro99]

How can I check whether the VM uses "vmnet0, vmnet1 or vmnet8?

Thanks again for the help!

[continuum]

attach the vmx-file please

[robmypro99]

Sorry, where do I get this file from? Sorry I am really new at this!

[robmypro99]

I think I found it.

[continuum]

you have configured your VM to use bridged network - see this line

ethernet0.connectionType = "bridged"

[robmypro99]

So what should I do to fix this? SourceForge installation docs said to use this option.

[robmypro99]

Here's a bit more information about my network setup, Ulli. The host is a Windows 2003 Server connected via Cat5 to my DSL Router (Qwest Motorola 3347). With No_IP i use name.name.com (example) which then points to the dynamic IP address on my system. There is an application on the host that sends the information from my server to No_IP which keeps this in sync. So since the internal IP address that I access the SourceForge application from (VM) is 192.168.0.209 I created some entries in my router to forward ports 22, 25 and 443 to this IP address (based on installation instructions). The VM actually runs on the host, with an IP address 192.168.0.175.

I know the application runs on 192.168.0.209 because when I enter that in my browser the application comes up.

Any ideas?

[continuum]

did you configure vmnet0 to use your Intel Nic instead of automatic bridging ?

If yes -  the vmware related work is done.
The rest is finetuning of your router

you should be able to ping the guest from the host,
pinging from guest to host should also work

[robmypro99]

I really wish I knew more about this Ulli! Let's take this a step at a time!

"did you configure vmnet0 to use your Intel Nic instead of automatic bridging?"

How do I check this to verify?

"You should be able to ping the guest from the host,
pinging from guest to host should also work"

So just ping 192.168.0.209 from the host PC?

Again Ulli, thank you very much for helping me.

[robmypro99]

Here is the latest screen shot from running vmnetcfg.exe.

[continuum]

when we spoke about vmnetcfg.exe earlier I told you what to do with vmnet0

if you want me to check post a screenshot again

ping is always the first start to troubleshoot network problems