spiceworks

[spyros 0]

Hello i have set up spiceworks on a server and everytime i am trying to inventory scan my network spice block the communication . I found a solution from client side .When i disabled the personal firewall inventory worked . I create a rule on the client and this worked but when i create this rule on the server to publish it to all clients (clients got the update) didnt work out . Do you have any suggestion ? I created the rule to allow all traffic from and to the server . 

 

Kind regards,

Spyros Ntouroukis

[Marcos 5,074]

On a machine with the communication blocked, you can run the Firewall troubleshooting wizard to get a list of recently blocked connections which will allow for creating the appropriate rule with one click. You can then apply the rule to all machines via a policy.

[spyros 0]

i did that i already whitelist it from the client but i would like to publish a rule from the server . when i create the same rule on the server and the client receive it  still the communication is blocked.

[Marcos 5,074]

Please post a screen shot of the rule that you've created. Maybe you specified both the local and remote port but the remote port changes and thus shouldn't be specified.

[spyros 0]

this is the rule i have create on server . also i permit IDS

this is the rule the wizard create on client.

 

. check also my logs 

[Marcos 5,074]

On a computer where the communication is blocked:
- enable advanced network protection logging in the advanced setup -> tools -> diagnostics
- reproduce the problem (ie. make sure the communication is blocked)
- disable advanced logging
- gather logs with ESET Log Collector and provide me with the generated archive.

[spyros 0]

Goodmorning Marco ,

I would like to thank you for the time you spent on my case.I have collect log files  please find it attached .

BR

ees_logs.zip

[spyros 0]

is there any chance i could collect rule from client and import to the server ?

[Marcos 5,074]

Just for clarification, is Spiceworks installed on 192.168.1.9? The workstation has the IP address 192.168.101.64 and the subnet mask is 255.255.255.0 so they are not in the same subnet.

Only SYN packets like these with the IP address of the machine were blocked by the firewall which should not cause any issues. Moreover, TCP port 7680 is used by WUDO (Windows Update Delivery Optimization) to distribute updates in Windows LANs.

As to your question, you can request client's configuration in client details and then convert it to a policy.

[spyros 0]

Goodmorning marco ,

 

192.168.1.9 this is my spiceworks server , subnet 101 is know at my network. I created the rule at a computer then i went to eset and convert that rule to policy .  looks like its working . i will give you feedback maybe tomorrow when eset server-clients will be synchronized and also i will perform scan on the network.

 

(https://support.eset.com/kb6517/?locale=en_US&viewlocale=en_US)

Regards,

Spyros Ntouroukis

 

[Marcos 5,074]

I wonder if you could share the rule you had to create to allow the communication.

[spyros 0]

i will do it when i will "deploy" and the rule is working 100% 

Edited June 5, 2019 by spyros