Hi Sarah, The tagging is done by heuristic that analyzes the probe connection attempts, SOS, timing between them and some other attributes like messages about flash drive. It has to have a quite large window for looking into data and it can take up to a few days for addressing a probe to a special controller if needed and resetting tags. In your case I see that it was disconnected at 2016-02-12 12:26:09. Up till this time your probe had no problem connecting regservers and controllers (tcp/443). After that time I see only SOS (DNS (tcp|udp)/53). That suggests the network problem with the highest probability - DNS is open but tcp/443 is closed. The lowest probability has the hardware problem (flash drive) in this case. Please use the tag as a suggestion where to begin your local diagnostics. If the network is good you can try to reinit the flash drive. wbr /vty On 2/16/16 7:29 PM, sarah.wassermann@student.ulg.ac.be wrote:
Hi,
I have (once again) problems with my probe (probeID: 24102). This time, it got tagged as "system: Firewall problem suspected". The strange thing is that I did not touch anything on my router when this happened and did not change any other configuration... This probe is located in Luxembourg. I now brought it to Belgium and plugged it into the router I have here. Nothing changed. Furthermore, here in Belgium, its 3rd light is slowly blinking, which let's suppose that it gets tuck in the network-testing phase.
Anybody knows how to fix this?
(I already had some problems with that probe ("system: Hardware problem suspected") but I could solve them thanks to a hint given by a user.)
My worst problem is that, due to this issue, we have difficulties earning enough credits for our research... So I would be really happy if this problem could be solved easily :(
Thanks!
Sarah