Jump to content

  • Log In with Google      Sign In   
  • Create Account


cant connect to a virtual os running a basic tcp server


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
1 reply to this topic

#1 Anddos   Members   -  Reputation: 485

Like
0Likes
Like

Posted 24 December 2012 - 12:37 PM

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, 25 December 2012 - 12:33 AM.

:)

Sponsor:

#2 hplus0603   Moderators   -  Reputation: 5155

Like
0Likes
Like

Posted 26 December 2012 - 05:57 PM

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.


enum Bool { True, False, FileNotFound };




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS