I have a problem when I want to capture an image of my physical machine. I have a DHCP Server, it turns on Windows Server 2012. I put the options 66 and 67 in my DHCP Server. I have a virtual Server FOG, the FOG’s version is 1.3.5.
And my problem is that, when I want to capture or deploy with Wake On Lan in my physical machine. The machine starts fine in Wake On Lan. But when it arrives in the part for mounting the file system, an error comes and say “connection timeout”. I don’t know what’is the problem. See the attached image for the exact error I am getting !

]]>https://forums.fogproject.org/topic/9977/problem-with-deployment-in-a-physical-machine-connection-timeoutRSS for NodeFri, 22 Feb 2019 14:10:38 GMTTue, 25 Apr 2017 11:07:07 GMT60I have a problem when I want to capture an image of my physical machine. I have a DHCP Server, it turns on Windows Server 2012. I put the options 66 and 67 in my DHCP Server. I have a virtual Server FOG, the FOG’s version is 1.3.5.
And my problem is that, when I want to capture or deploy with Wake On Lan in my physical machine. The machine starts fine in Wake On Lan. But when it arrives in the part for mounting the file system, an error comes and say “connection timeout”. I don’t know what’is the problem. See the attached image for the exact error I am getting !

]]>https://forums.fogproject.org/post/93251https://forums.fogproject.org/post/93251Tue, 25 Apr 2017 11:51:51 GMTNo, I already have imaged with this FOG Server but in virtual. I have imaged virtual machines, but now I want imaged with Wake On Lan and I must image in a physical machine.

192.168.230.10 is my fog server’s address, I’m sure. But I have a switch connected between my FOG Server and my physical machine. I don’t know if the problem come here.

Here is the results :

]]>https://forums.fogproject.org/post/93253https://forums.fogproject.org/post/93253Tue, 25 Apr 2017 12:12:47 GMTIt’s possible a firewall is blocking the port, which would cause it to timeout.

I want you to schedule another capture or deploy (doesn’t matter) but before you hit the button to schedule the task, make sure you check the debug option. Then pxe boot the target computer. This feature will drop the pxe booting computer to a command prompt after a few pages of text. This is the command prompt of the FOS engine (customized linux OS for capture and deploying on the target computer).

Once at the command prompt see if you can ping the fog server.
If that works then we can try to nfs mount the fog server.

See if the FOS engine has the showmount command. In this case you want showmount -e <fog_server_ip>

]]>https://forums.fogproject.org/post/93265https://forums.fogproject.org/post/93265Tue, 25 Apr 2017 12:51:25 GMT@george1421 Yes I did my ping from FOS Engine
For the command showmount, it says that “command not found”
]]>https://forums.fogproject.org/post/93270https://forums.fogproject.org/post/93270Tue, 25 Apr 2017 12:58:59 GMT@Andre OK from FOS do this

mkdir /mnt
mount -t nfs <fog_server_ip>:/images/dev /mnt
ls -la /mnt

The idea is to connect from the FOS back to the fog server using nfs.

]]>https://forums.fogproject.org/post/93276https://forums.fogproject.org/post/93276Tue, 25 Apr 2017 13:51:15 GMT@george1421 I tried what you told me to do. But when I do the command for mounting, I have the same error “Connection Timeout” .
]]>https://forums.fogproject.org/post/93353https://forums.fogproject.org/post/93353Wed, 26 Apr 2017 06:04:38 GMT@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.
]]>https://forums.fogproject.org/post/93354https://forums.fogproject.org/post/93354Wed, 26 Apr 2017 06:33:27 GMTThis sounds an aweful lot like the nic of the fogserver is setup in Nat mode vs. bridged mode. I say this because of the “it works in virtual systems, but not on physical machines.”
]]>https://forums.fogproject.org/post/93357https://forums.fogproject.org/post/93357Wed, 26 Apr 2017 09:04:05 GMT@Tom-Elliott My Fogserver is setup in bridged mode
]]>https://forums.fogproject.org/post/93358https://forums.fogproject.org/post/93358Wed, 26 Apr 2017 09:18:16 GMTNobody has a solution for my problem ?
]]>https://forums.fogproject.org/post/93604https://forums.fogproject.org/post/93604Sat, 29 Apr 2017 09:13:53 GMT@Andre There has to be something we are not seeing here.

Lets just recap where we are here.

You have a new fog server that is running FOG 1.3.5 that is a physical server (not really relevant that its physical)

Your fog server’s IP address is 192.168.230.10

Your target computer IS talking to the FOG server because it can check in, plus FOS does load and is running.

NFS is sharing the proper directories.

NFS is timing out in that it can’t connect.

Possible issues.

The firewall is running on the FOG server blocking nfs mounting.

selinux is not set to permissive on the FOG server.

There is some kind of screening router between the target computer and FOG server

Not all of the nfs services are running on the FOG server

Since there is a second fog server in the environment maybe it is playing a part in the target computer’s booting process that is unknown to us.

Since the target computer can’t seem to mount the nfs share on the physical fog server and you have a second virtual fog server, I would try to mount the nfs shares on the phy fog server from the vm fog server to confirm that nfs is working on the phy fog server.

from the vm fog server

mount -t nfs 192.168.230.10:/images /mnt
ls -la /mnt
umount /mnt

The above command should mount the images share on the phy fog server, list the contents of the directory and then unmount the images directory. When you run this command I would expect to see something like this:

]]>https://forums.fogproject.org/post/93605https://forums.fogproject.org/post/93605Sat, 29 Apr 2017 11:47:21 GMT@george1421 I just have one server FOG and it is virtual. I don’t have a Physical server FOG.
]]>https://forums.fogproject.org/post/93676https://forums.fogproject.org/post/93676Tue, 02 May 2017 06:10:21 GMT@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”.
]]>https://forums.fogproject.org/post/93677https://forums.fogproject.org/post/93677Tue, 02 May 2017 06:23:22 GMT@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

]]>https://forums.fogproject.org/post/93679https://forums.fogproject.org/post/93679Tue, 02 May 2017 06:44:32 GMT@george1421 And when I tried to do the same thing in my physical machine, it doesn’t work
]]>https://forums.fogproject.org/post/93680https://forums.fogproject.org/post/93680Tue, 02 May 2017 06:52:52 GMT@Andre This is not logical.

The key to look for is the space, star ( * ) right after the share name. This restricts nfs access to specific hosts. The start means everyone.

]]>https://forums.fogproject.org/post/93686https://forums.fogproject.org/post/93686Tue, 02 May 2017 09:38:29 GMT@georgI have the same lines as you
]]>https://forums.fogproject.org/post/93688https://forums.fogproject.org/post/93688Tue, 02 May 2017 09:44:55 GMT@Andre Well then…