Yes, Wayne; I guess so…
We spent a couple of days recreating a new image from scratch and it’s working: we’ll use that.
Thanks everybody for the support.
thank you for your support.
If I deploy another image on the same client PC it can succesfully connect to the FOG server (so i don’t think is a problem on the switch or on the cable).
I’ve tried from several PC, some of them are on the same switch that FOG is connected to and some of them are connected to another switch; but the issue remains.
Right, i’ll clean the DB then. Thank you.
Thanks Trevelyan; we actually restarted the Service several time but without luck: the behaviour was the same (unable to contact the fogserver).
We don’t use SSD drive neither on server or client.
I’m wondering if it could be something related to the .NET libraries or to some other kind of restriction on the Microsoft side…
It seems also that the upd-sender process started with
min receivers=5 for the first session (the one set with msClients=7)
min receivers=3 for the second session (the one set with msClients=3)
that means that 2 PC were not depoloyed: in fact they are still waiting on the first PartClone screen.
thank you for the quick reply.
Yes, all the 10 PC in the same group are set with the same Image Id (ID: 9).
I can see the same ID also in the multicastSessions table, column msImage.
just a question: i created a group with 10 pc and I created a multitask deploy job for that group.
Fog created two different row in the multicastSessions table one with 7 msClients and one with 3 msClients.
This is slowing down the whole deploy process (more network traffic, server I/O contention because of the two udp-sender processes).
Is this behaviour normal? I supposed to have just one multicastSessions with 10 clients.
I’m using fog svn 3559 on Centos 6.6.
I’ve tried everything.
I removed the antivirus, disabled the firewall, uninstalled and reinstalled the Service (the IP address was correct). I uninstalled all the additional software too (skype, vlc, chrome, etc…).
I also tried to sniff traffic using Whireshark: I noticed that the client never starts the TCP connection to the server…
Few details to add: