I think I have it:
link text
Confirmed this on a 1810G-24 GE, using the last firmware (P.2.22 at this time). The “Auto DoS” feature blocks NFS : ip packets come in, but never come out from the switch.

And to notice : disabling the feature is not sufficient to make it work again. I had to do a hard factory reset (factory reset from the web gui did nothing) to make it work again.

It seems that this option is stickying somewhere in the configuration, even after disabling it !

@Sebastian-Roth
Sorry my mistake… it’s a /19… Mask is 255.255.224.0
Subnet goes from 172.16.0.1 to 172.16.31.254
As I told you other computers in the same network are working fine.
I’m now going to move a non working cpu to a working building to see what happen.
Let see if is a pc harware issue or a network one.
I keep you updated
Regards

Hi I´m trying to create a Snapin pack using this scipt but when I test it I recive an error in Line 2 Character 5; Code: 800A03F2
I’ve no experience scripting and not sure were the failure is:
This is what I have in my .VBS file

Set csv="C:\Program Files (x86)\FOG\tmp\IPSet2301\ComputerList.csv"
for /f "skip=1 delims=, tokens=1-6" %%a in (%csv%) do (
  if /I "%computername%"=="%%a" (
     netsh int ipv4 set address "Wi-Fi" static %%b %%c %%d
    netsh int ipv4 set dnsserver "Wi-Fi" static %%e
    netsh int ipv4 add dnsserver "Wi-Fi" %%f
  )
)

I think I have it:
link text
Confirmed this on a 1810G-24 GE, using the last firmware (P.2.22 at this time). The “Auto DoS” feature blocks NFS : ip packets come in, but never come out from the switch.

And to notice : disabling the feature is not sufficient to make it work again. I had to do a hard factory reset (factory reset from the web gui did nothing) to make it work again.

It seems that this option is stickying somewhere in the configuration, even after disabling it !

Hi @Sebastian-Roth were can i find logs to see what is failing? I’ve check every thing and every where and can’t find config difereces between locations that work and the ones that doesn’t.

Finally if i move the computer to another building it work so it must be a switch issue.
Let see now if i find what it is

@Sebastian-Roth
Sorry my mistake… it’s a /19… Mask is 255.255.224.0
Subnet goes from 172.16.0.1 to 172.16.31.254
As I told you other computers in the same network are working fine.
I’m now going to move a non working cpu to a working building to see what happen.
Let see if is a pc harware issue or a network one.
I keep you updated
Regards

Hi @Sebastian-Roth In first place thanks for your help
They are in the same network 172.16.0.0/27
Server IP is 172.16.5.1 and clients are 172.16.0.x
I enable the DHCP serve during Fog instalation so PXE-DHCP setting should be correct.
My school has many small building and each one has a switch (all of them are the same model-firmware, ect.) all of them conneted to a main one where the server is .
Installation work in some building but not in others.
Logic sais that it must be a network issue but i’ve compared switch configurations and i can’t find any diference.
I´m completly lost

Hi again, I add 2 screenshorts to see if someone can gide me in the right direction:

Re: Stuck on “running post init scripts” when trying to boot into pxe client
I have the same issue but giving permisions and restarting doesnt solve the problem
The fact is that the error happens only in some computers, others works perfect when I deploy the image