Hi Viktor, Sorry for my long silence.
I tried everything related to the USB drive you suggested, but nothing helped. Even worse, the probe corrupted one of my USB drives and I had to recover it with diskpart. (The USB drive worked fine just before the test, but it became unreadable afterwards and I had only 1 GB at my disposal, whereas it was a USB drive with a capacity of 16 GB) Do you have any other ideas to fix this probe or should I simply order a new one? Thanks! Sarah ----- Mail original ----- De: "Viktor Naumov" <[email protected]> À: "sarah wassermann" <[email protected]> Cc: [email protected], [email protected] Envoyé: Lundi 7 Mars 2016 08:46:26 Objet: Re: [atlas] probe tagged as "system: Firewall problem suspected" Hi Sarah, Did you try to boot the probe without USB drive plugged in and replugging it back in 10 minutes while being powered? Did you try to replace the USB drive with a new one with capacity >= 4G? If you tried everything please write to [email protected] it will create a ticket and we will look further what we can do together about it. Cheers! /vty On 3/6/16 12:25 PM, [email protected] wrote: > Hi Viktor, > > I tried all your pieces of advice, but my probe is still disconnected (with > 3rd light slowly blinking). > I also attempted to connect it to my router in Liège, on which another probe > is also connected and working fine, but even there the probe didn't come back > to life. > > Thanks to several generous credit-donations, I don't need credits anymore, > but can I send the probe somewhere so that it can be fixed? There are not > that many probes here in Luxembourg and I would be happy to host a working > probe to help extend the network! > > Best regards, > > Sarah > > ----- Mail original ----- > De: "Viktor Naumov" <[email protected]> > À: "sarah wassermann" <[email protected]> > Cc: [email protected] > Envoyé: Mercredi 17 Février 2016 10:53:02 > Objet: Re: [atlas] probe tagged as "system: Firewall problem suspected" > > 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, [email protected] 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 >>
