I have solved my problem. The first problem (connection timeout) comes of the switch, I have change for a router and it works ! The second problem, I have reinstall Windows 10 and it works, I can capture my physical machine !
Thank you for all your help !
Ok, I tied another thing. I have put a router between my VMs and my physical machine. I launch a capture task. And it happens to mount the nfs system file but it don’t pass in mounting partition. So the first problem is solved. Now I have the problem with “mounting partition” when I do a capture task. So I tried to launch another task, I have launch a deploy task, andi it works fine ! So the problem now is when I try to do a capture of my physical machine
Ok, I tried something. I have just put a cable ethernet between my VMs and my physical machine. And it happens to mount the nfs system file. But now when it arrives in “mounting partition” it failed and say “operation not permitted”. There is a picture :
@Tom-Elliott Ok, I will try something Monday, and I say something
Thank you for your help
@george1421 Ok I do the command (sudo iptables -L) and I have the same as you
@Tom-Elliott ok, but if you want to remote, I must have access to internet in my physical machine.
@Tom-Elliott I can’t run this command in my physical machine in cmd. My physical machine turns on Windows 10
@Tom-Elliott where I run this command ?
And my network is a local network. I don’t have access to internet.
@Tom-Elliott The IP address of my physical machine is 192.168.230.23. I can ping my server FOG and my server FOG can ping my physical machine.
@george1421 Ok, for the first command I have this :
For the second command (sudo ipables -L), it says command not found
And for the third command (sestatus). I have to install “policycoreutils” and I have do this. And the result of the command “sestatus” :
@georgI have the same lines as you
@george1421 And when I tried to do the same thing in my physical machine, it doesn’t work
@george1421 I tried with these commands in FOS Engine, with my virtual machine :
mkdir /images
mkdir /images/dev
mount -o nolock,proto=tcp,rsize=32768,intr,noatime 192.168.230.10:/images /images
mount -o nolock,proto=tcp,rsize=32768,intr,noatime 192.168.230.10:/images/dev/ /images/dev
And it works, I can mount
@george1421 I tried to mount what do you said, in a Virtual machine, on which I have already capture his image. But when I execute the command “mount -t nfs 192.168.230.10:/images /mnt”, in FOS engine. It say “connection refused”.
@george1421 I just have one server FOG and it is virtual. I don’t have a Physical server FOG.
Nobody has a solution for my problem ?
@Tom-Elliott My Fogserver is setup in bridged mode
@george1421 But I don’t understand why in virtual it works and in physical it doesn’t work. I can deploy or capture virtual machines without problem, and physical machines I can’t.
@george1421 I tried what you told me to do. But when I do the command for mounting, I have the same error “Connection Timeout” .
@george1421 Yes I did my ping from FOS Engine
For the command showmount, it says that “command not found”