• Advertisement
Sign in to follow this  

cant connect to a virtual os running a basic tcp server

This topic is 1879 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

virtual os is 192.168.1.103 and thats running the TCP server
i ported forward 8888 192.168.1.103 on the router
client is now set to connect to 192.168.1.103
cant connect
so something is up

now i have it working now with the virtual os set to bridged, but if i change the client to connect to my real isp ip now its not connecting to the server thats running on the virtual os?, i have port forwarded the right ip and port Edited by Anddos

Share this post


Link to post
Share on other sites
Advertisement

It's hard to tell without knowing what virtualization software you're using, what OS you're using, and what networking configuration you're using for the virtual machine.

 

My *guess* is that the virtual machine is actually running on a private NAT inside the VM, This is, for example, the default set-up for VMWare Workstation. What this means is that only the machine hosting the VM will see the VM network. "ping 192.168.1.103" from the host machine should get to the VM in this case. If this is the case, either switch to bridged networking and configure it correctly for your network infrastructure, or set up port forwarding *on the host machine* in addition to your router, if your VM host software supports that.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement