so it's my dedicated host fault? they have to fix it for me?
so it's my dedicated host fault? they have to fix it for me?
Add: when I try to connect trhough SSH from my personal computer it says:
Network error: connection timed out.
What are you trying to connect to? If your server is a guest in a vm that is using NAT and not briding, then the guest has a non routable IP address ( 192.168.x.x? ) which can not be seen by other hosts. The only way to reach it is through the IP address of the host, which has to know it needs to forward the connection to your guest.
there are "two machines":
1- The host one with Windows Webserver 2008.
2- The virtual one with VMware and Debian Etch OS.
I want to connect through SSH on the VM one at my personal computer.
I'm using NAT.
Yes, and the problem is that based on what you say about the VM not supporting briding, #1 and #2 share a single IP address, so you can not connect to #2 without #1 being configured to forward the connection to #2.
Since it's NAT, it's working.
It has internet access and I can connect trhough SSH from the Host (Windows 2008 ) machine, but I can't do that from my personal computer.
Last edited by rafaelvidal; July 19th, 2011 at 06:14 PM.
Using what port and address? As I said before, the guest is borrowing the host's IP address, so to reach the guest, the host must be configured to forward that port to the guest, and you must connect to the host's IP address.
192.168.91.128 Port: 22
by my personal computer it doesn't work.
I try the host IP
example:
188.16.163.14 Port: 22
That is because 192.168.x.x addresses are local only addresses; they can not be accessed over the Internet.
That wasn't a complete sentence. Did you try this? Did it work? If not, then your host is not configured to forward port 22 to your guest. Presumably there are other guests that also want to use port 22, so this probably will not be possible, so you will have to have the host forward some other port instead.
what we are trying to tell you, is that NAT won't work, unless you:
1) run your virtual service on a port that is not in use by the host (eg, since the host runs ssh on 22, you cannot use 22 on your guest).
2) you must forward the port on your VM nat to the guest:
(VirtualBox)
http://www.aviransplace.com/2008/06/...ding-with-nat/
(VMWare)
http://www.conetrix.com/Blog/post/Po...using-NAT.aspx
Things are rarely just crazy enough to work, but they're frequently just crazy enough to fail hilariously.
Bookmarks