My host (XP) is on the network 192.168.4.0.
My virtual machine (Fedora) is in the network 10.0.2.0 (NAT)

When I try to gain access via ssh from my virtual machine to one of the clients on the 192.168.4-network, I succeed.

ssh 192.168.4.8 (success)

When I try to gain access via ssh from one of the clients on the 192.168.4-network to my virtual machine, it doesn't work.

ssh 10.0.2.15 (fail)

There is a webserver on my fedora virtual machine that I would like to access from the 192.168.4.0 -network, but that doens't work.

Anyone knows why I fail to talk to my virtual Fedora ? Cause the opposite way works fine.

Well it depends why it isn't working. Do you know if the virtual machine has a firewall runnin?

What is the exact message when you try to ssh in?

ssh 10.0.2.15 takes forever...

port 80 is open, also ssh is permitted on the firewall of my fedora virtual machine.

edit : after minutes of trying I get :
connect to host 10.0.2.15 port 22 : connection timed out

What's port 80 got to do with it? ssh works on port 22

To access the webserver...

So you are trying to connect from another machine to a machine that is running a virtual server on it. What should happen is the machine needs to have a port open like 22 open and then be able to forward that port to the virtual server port 22. Now if the the host machine is running ssh on port 22 then set the virtual to another port or vice a versa. Then you can forward that port to the virtual.

Brian

Focus on one issue at a time - you start talking about ssh and then throw http in as an aside. Keep issues clear

Fedora 8 is running as virtual machine on windows XP pro with VirtualBox (virtualisation soft). The virtual machine uses NAT to be able to connect to the outside world.

Isn't NAT responsible for mapping packets that arrive at my host (XP) to my virtual machine (Fedora) ? I suppose that al the routes in the ip-tables are set correct ?!

Don't tell me I need to open port 22 on my XP host to be able to speak to my virtual machine. Does it work like that ?
XP and his ports normally have nothing to do with packets that are destinated for my virtual machine, no ?!

I've added a route on host 192.168.4.8 that tells to forward packets for the 10.0.2.0-network directly to host 192.168.4.123 (my XP host that is running the virtual Fedora), but that didn't help much.

Thx all for your reply.

If the network clients are going via your windows machine then of course the windows host needs to allow port 22 through. Maybe I'm not following your setup, but this is what I understand from the OP

So for every service that I want to run (web, ftp, ssh,...) on my virtual machine Fedora, the corresponding ports need to be open on my hostmachine XP ?

change the ip address of your virtual machine - put it on the same network as others (i.e. give it 192.168.4.13 address)

I'm working with Network Address Translation. What difference does it make whether I put it in a B-class subnet or a C-class ?

Only if I understand your setup correctly and you're routing through the windows box

Setup network as nat requires mapping ports from the external IP and external port of the host server to the guest OS, IP, and port. Same setup like a plain generic store bought router. If you set the network to bridge then it is seen as directly on the same network. No portforwarding required there.

Brian

Please can you run a "sudo /etc/init.d/iptables status" and copy and paste the results here, remember to place code tags around them.

Also run a "sudo /etc/init.d/sshd status" and confirm that sshd is actually running. If sshd is not then type "sudo /etc/init.d/sshd start". There will be a few minor configuration changes needed if that's the case as ssh won't come back-up should the VM need rebooting/restarting.

If your logging in as root you won't need the sudo parts, if you aren't you need privilages to run sudo.