Problem with deployment in a physical machine / connection timeout
-
The
passwdcommand would be on the machine you’re trying to image from.If your machine that IS connected to the internet is able to communicate to your fogserver and your computer trying to be imaged, then the local network doesn’t need internet.
-
@Tom-Elliott I can’t run this command in my physical machine in cmd. My physical machine turns on Windows 10
-
@Andre You’re trying to image it? You would boot it like you’re doing an imaging task.
Make the task a debug by checking the “Schedule as Debug” before confirming the tasking.
-
@Tom-Elliott ok, but if you want to remote, I must have access to internet in my physical machine.
-
@Andre NO internet is not required. As long as the machine you’re talking to me with here has internet AND can communicate with the FOG Server at the same time, the physical machine does not need internet.
-
@Andre OK I’m getting lost here (sorry only one small cup of coffee so far).
Lets get some terminology defined here so I can understand what is going on.
We have a FOG server that is running on a vm. That shall be called the FOG or fog server.
We have a target computer that is what we are wanting to capture and deploy from. That shall be call FOS or the target computer (I don’t care if its physical, virtual or imaginary).
What is confusing is that we have an original fog server that I think keeps getting mixed into the conversation.
-
@Andre said in Problem with deployment in a physical machine / connection timeout:
For the second command (sudo ipables -L), it says command not found
For this command you are missing a letter. Its
sudo iptables -LThis one is important to know because this is the firewall on the fog server.Your other commands are showing that nfs is up and operational on the FOG server.
And selinux is disabled. So we’ve almost ruled out the FOG server for being at fault here.
Looking at the IP addresses involved here, the FOG server is at IP address 192.168.230.10 and the target computer is at 192.168.230.23. So they are on the same subnet which rules out some kind of screening router between the two devices (FOG and FOS-target).
-
@george1421 Ok I do the command (sudo iptables -L) and I have the same as you
-
@Andre What OS is the physical computer that hosts the virtual FOG server running?
-
@Quazz Windows 10.
The Virtual Host is VMWare Workstation.
The VMWare VM is Running, now, Ubuntu 16.04 (or should be last I talked.)
The problem is something specific to NFS based on my troubleshooting.
To test, I actually simply disabled the nfs service and tested, Immediately the System fails to connect. Other virtual machines have no problem communicating, just physical machines seem to not be able to get through.
We’ve turned off the firewall on the machine entirely so Windows is not blocking the connections. The network was tested with Host-only->Bridged, and NAT. Bridged is the appropriate thing to use, but while we were testing it was worth the extra effort.
I suspect the problem is something with return to the physical machine rather than a problem with the VM, Windows OS or not. There is a switch that the devices communicate through and I’m suspecting it’s this causing our problems.
@Andre do you have a “dummy” switch you could place between the FOG Server nic and the Main machine? You’d likely want to change the VM Nic to use NAT and make sure it’s setting the same machine to the same IP as your fog server is expecting. Essentially I’d like to remove the current switch from the scene almost altogether as I suspect the switch is preventing back communication.
-
@Tom-Elliott Ok, I will try something Monday, and I say something
Thank you for your help
-
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 :
-
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
-
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 !
