[ripe.net #1087678] problem with connection to network
Hello, Thanks for your email and update. I can confirm the probe is back online and reporting without issue. If you do have any further questions, please do not hesitate to contact us. Thank you for taking the time to host an Atlas probe. Kind Regards, Alastair Strachan RIPE Atlas Team ============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 ============================================================= On Mon May 27 18:33:28 2013, sdimonius@gmail.com wrote:
Hello and thanks for reply!
Now probe is work. I was read all FaQ, but nothing help.
The network is efficient for 100%.
Experiments help me. First i remove external memory, boot from built in, and then attach usb flash, after 10 mins probe connect to network.
Hello,
Thanks for your email and update.
It would appear there is something on the network that is blocking
27.05.2013 16:23, Alastair Strachan пишет: the probe from connecting outside the network.
If a probe has been assigned a Static IP and for some reason that is
not reachable, the probe will automatically fall back to DHCP. As this is not happening, there must be something blocking it.
The probe is currently configured via DHCP, again, this is not
allowing the probe to connect outside your network.
Please ensure port 443 is fully open and all firewall/security rules
have been adjusted accordingly. Please take a look at our FAQ for more troubleshooting steps: https://atlas.ripe.net/about/faq/
If you do have any further questions, please do not hesitate to
contact us.
Thank you for taking the time to host an Atlas probe.
Kind Regards,
Alastair Strachan
RIPE Atlas Team
============================================================ Take
the RIPE NCC Survey 2013 and tell the RIPE NCC what you think!
Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 =============================================================
On Sun May 26 16:01:00 2013, sdimonius@gmail.com wrote:
Hello!
I have problem with my probe v3 (ID 11003, FW 4520).
First i used DHCP (at Home, for tests), all was worked fine.
Then i reconfigure my probe to Static IP (by manual). Static IP necessary to install my probe 24/7/365 in server room. We don't use DHCP.
But probe can't connect to network...
I brought probe to home, connect to DHCP network. Router give IP to probe. But probe still disconnected on atlas.ripe.net at least 3 hours...
LEDs: 1 - ON 2 - OFF 3 - Slow blink 4 - ON 5 - ON
Power reset - no result. Try to change Router cfg (ip, dns, mask) - no result. Probe still disconnected.
I read, that if set static IP - probe try to test setting.
By LEDs - "Network test"? But 3+ hours "Network test"?
DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work without problems on full autoconfiguration (IP, mask, gateway, DNS)
Can you help me?
P.S. Sorry for my english, i'm from Ukraine
hi, Well,ok. thanks 1st question: - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? (If that's matter, I use Astaro Security Gateway software appliance as router) 28.05.2013, в 15:37, Alastair Strachan <atlas@ripe.net> написал(а):
Hello,
Thanks for your email and update.
I can confirm the probe is back online and reporting without issue.
If you do have any further questions, please do not hesitate to contact us.
Thank you for taking the time to host an Atlas probe.
Kind Regards,
Alastair Strachan
RIPE Atlas Team
============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 =============================================================
On Mon May 27 18:33:28 2013, sdimonius@gmail.com wrote:
Hello and thanks for reply!
Now probe is work. I was read all FaQ, but nothing help.
The network is efficient for 100%.
Experiments help me. First i remove external memory, boot from built in, and then attach usb flash, after 10 mins probe connect to network.
Hello,
Thanks for your email and update.
It would appear there is something on the network that is blocking
27.05.2013 16:23, Alastair Strachan пишет: the probe from connecting outside the network.
If a probe has been assigned a Static IP and for some reason that is
not reachable, the probe will automatically fall back to DHCP. As this is not happening, there must be something blocking it.
The probe is currently configured via DHCP, again, this is not
allowing the probe to connect outside your network.
Please ensure port 443 is fully open and all firewall/security rules
have been adjusted accordingly. Please take a look at our FAQ for more troubleshooting steps: https://atlas.ripe.net/about/faq/
If you do have any further questions, please do not hesitate to
contact us.
Thank you for taking the time to host an Atlas probe.
Kind Regards,
Alastair Strachan
RIPE Atlas Team
============================================================
Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think!
Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 =============================================================
On Sun May 26 16:01:00 2013, sdimonius@gmail.com wrote:
Hello!
I have problem with my probe v3 (ID 11003, FW 4520).
First i used DHCP (at Home, for tests), all was worked fine.
Then i reconfigure my probe to Static IP (by manual). Static IP necessary to install my probe 24/7/365 in server room. We don't use DHCP.
But probe can't connect to network...
I brought probe to home, connect to DHCP network. Router give IP to probe. But probe still disconnected on atlas.ripe.net at least 3 hours...
LEDs: 1 - ON 2 - OFF 3 - Slow blink 4 - ON 5 - ON
Power reset - no result. Try to change Router cfg (ip, dns, mask) - no result. Probe still disconnected.
I read, that if set static IP - probe try to test setting.
By LEDs - "Network test"? But 3+ hours "Network test"?
DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work without problems on full autoconfiguration (IP, mask, gateway, DNS)
Can you help me?
P.S. Sorry for my english, i'm from Ukraine
hi, Well,ok. thanks 1st question: - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? (If that's matter, I use Astaro Security Gateway software appliance as router) 28.05.2013, в 15:37, Alastair Strachan <atlas@ripe.net> написал(а):
Hello,
Thanks for your email and update.
I can confirm the probe is back online and reporting without issue.
If you do have any further questions, please do not hesitate to contact us.
Thank you for taking the time to host an Atlas probe.
Kind Regards,
Alastair Strachan
RIPE Atlas Team
============================================================ Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think! Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 =============================================================
On Mon May 27 18:33:28 2013, sdimonius@gmail.com wrote:
Hello and thanks for reply!
Now probe is work. I was read all FaQ, but nothing help.
The network is efficient for 100%.
Experiments help me. First i remove external memory, boot from built in, and then attach usb flash, after 10 mins probe connect to network.
Hello,
Thanks for your email and update.
It would appear there is something on the network that is blocking
27.05.2013 16:23, Alastair Strachan пишет: the probe from connecting outside the network.
If a probe has been assigned a Static IP and for some reason that is
not reachable, the probe will automatically fall back to DHCP. As this is not happening, there must be something blocking it.
The probe is currently configured via DHCP, again, this is not
allowing the probe to connect outside your network.
Please ensure port 443 is fully open and all firewall/security rules
have been adjusted accordingly. Please take a look at our FAQ for more troubleshooting steps: https://atlas.ripe.net/about/faq/
If you do have any further questions, please do not hesitate to
contact us.
Thank you for taking the time to host an Atlas probe.
Kind Regards,
Alastair Strachan
RIPE Atlas Team
============================================================
Take the RIPE NCC Survey 2013 and tell the RIPE NCC what you think!
Participants will be entered into prize draws to win an iPad. https://www.ripe.net/survey2013 =============================================================
On Sun May 26 16:01:00 2013, sdimonius@gmail.com wrote:
Hello!
I have problem with my probe v3 (ID 11003, FW 4520).
First i used DHCP (at Home, for tests), all was worked fine.
Then i reconfigure my probe to Static IP (by manual). Static IP necessary to install my probe 24/7/365 in server room. We don't use DHCP.
But probe can't connect to network...
I brought probe to home, connect to DHCP network. Router give IP to probe. But probe still disconnected on atlas.ripe.net at least 3 hours...
LEDs: 1 - ON 2 - OFF 3 - Slow blink 4 - ON 5 - ON
Power reset - no result. Try to change Router cfg (ip, dns, mask) - no result. Probe still disconnected.
I read, that if set static IP - probe try to test setting.
By LEDs - "Network test"? But 3+ hours "Network test"?
DHCP work correctly (Router - Zyxell Keenetic, last firmware), PC work without problems on full autoconfiguration (IP, mask, gateway, DNS)
Can you help me?
P.S. Sorry for my english, i'm from Ukraine
On 5/28/13 10:50 , Dmitriy Kazimirov wrote:
hi, Well,ok. thanks 1st question: - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? (If that's matter, I use Astaro Security Gateway software appliance as router)
Hi, For getting consistent results it would be best to configure the router to use just one connection for the probe. I think it is best to get the current probe to be stable for a while before asking for a second probe.
On 5/28/13 10:50 , Dmitriy Kazimirov wrote:
hi, Well,ok. thanks 1st question: - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? (If that's matter, I use Astaro Security Gateway software appliance as router)
Hi, For getting consistent results it would be best to configure the router to use just one connection for the probe. I think it is best to get the current probe to be stable for a while before asking for a second probe.
participants (5)
-
Alastair Strachan -
Dmitriy Kazimirov
-
Dmitriy Kazimirov -
Philip Homburg
-
Philip Homburg