This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Reconnecting probe 3508 - troubleshooting
- Previous message (by thread): [atlas] Reconnecting probe 3508 - troubleshooting
- Next message (by thread): [atlas] Reconnecting probe 3508 - troubleshooting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Viktor Naumov
vnaumov at ripe.net
Mon Aug 22 08:09:51 CEST 2016
Hi Michael-John, Check if you can connect from you network to woolsey.atlas.ripe.net and/or oneill.atlas.ripe.net using port 443 wbr /vty On 8/21/16 7:43 PM, Michael-John Turner wrote: > Hi > > I've just reconnected probe 3508 to the network after a number of years > offline (I think it was last online in November 2012?). > > Under the SOS history, I can see that it's making DNS queries successfully > (using the DNS servers it receives by DHCP), but it's not connecting > correctly to the RIPE network. The following is also displayed under SOS > history: "This probe cannot connect on port 443 (HTTPS)". > > Any thoughts on where I can start troubleshooting? For test purposes I've > connected the probe to my LAN, with full internet access. > > Cheers, MJ
- Previous message (by thread): [atlas] Reconnecting probe 3508 - troubleshooting
- Next message (by thread): [atlas] Reconnecting probe 3508 - troubleshooting
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]