Débit / Ouverture de port BOX

[reverse62]

Bonjour.
Je n'arrive pas à sortir avec TEAMVIEWER sur tablette.
D'après le site TEAMVIEWER, l'aplli utilise le port 5938
J'ai beau ouvrir ce port en UPD/TCP sur la box, je n'arrive pas à sortir.
Type NAT : Cone restrictif sur les ports
En passant par une box Bouygues, pas de problème.

Une idée?

Autre sujet, mon débit en filaire sur port 1Gb/s ne dépasse pas les 300mb/s voir 100mb/s par moment (test speedtest) pour un ping environs 15ms

merci

[thedark]

Bonjour,
Ça fonctionne sur PC ?

Cordialement

[reverse62]

Bonjour.

Oui, mais sur PC l'appli passe par le 80 si les autres sont fermés.

[Hugues]

Pas besoin d'ouvrir des ports avec TeamViewer, suffit d'avoir internet, le souci vient surement d'ailleurs.

[reverse62]

Bonjour, lors des tests speedtest / nperf, qui plafonnent a 60mbs montant et descedant je m'apercois que mon isp est reconnu comme oxid telecom association??

[reverse62]

En complément
2 tests débits nperf/speedtest
J'ai forcé Axione étant dans le 62 sur réseau Axione
(https://i.postimg.cc/Y99DGY8g/Capture2.png)
(https://i.postimg.cc/tgtGt3hM/Capture1.png)

et un tracert
(https://i.postimg.cc/pTjvhwsK/Capture3.png)

Le tout en filaire

Toujours pas de Teamviewer sur Android...

[ShovelHead]

Bonjour, lors des tests speedtest / nperf, qui plafonnent a 60mbs montant et descedant je m'apercois que mon isp est reconnu comme oxid telecom association??

https://forum.caps.services/index.php?action=post;quote=79001;topic=6173.15

[Vincent O]

Je n'arrive pas à sortir avec TEAMVIEWER sur tablette.

Notre support technique utilise régulièrement TeamViewer pour prendre contrôle à distance sur des Pure (donc Android). Pas besoin de configuration spécifique, ça marche sans aucune redirection de port, les ports 5938 / 443 / 80 ne sont utilisés que pour des connexions sortantes. Si vous aviez un parefeu il faudra autoriser l'application / rajouter une règle autorisant le traffic sortant; mais pas besoin de redirection de port sur le routeur (c'est seulement pour les connexions entrantes en IPv4 derrière un NAT qu'il le faut). C'est tout l'intérêt de TeamViewer contrairement à d'autres solutions (VNC, RDP...).

Par contre, le support a dû rester avec la version 12 sur les ordinateurs. La version 13 n'arrivait pas à se connecter aux Android. Si jamais ça ne marche pas, vous pouvez essayez de désactiver l'IPv6 au cas où et de changer de serveurs DNS (même si je ne comprends pas pourquoi ça marcherait pour le support et pas dans votre cas). Si ça ne marche toujours pas, il faudra faire une capture réseau pour voir ce qu'il se passe.

[reverse62]

Bonsoir,
J'utilise la version 14
J'ai toujours ma bbox et j'arrive a sortir sans probleme sur son resau (meme tablette/appli donc).
J'ai essayé les dns google, ca ne change rien.
Dans le log teamviewer j'ai ceci:

2018/11/24 21:00:24.345 7175-7194 I/TeamViewer CTcpConnectionBase[1]::HandleConnectTimeout(). Connect timed out to router10.teamviewer.com:5938
2018/11/24 21:00:24.346 7175-7192 W/TeamViewer CProcessCommandHandlerKeepAlive[1]::HandleKeepAliveConnect(): Connect to KeepAliveServer failed
2018/11/24 21:00:24.346 7175-7194 W/TeamViewer CTcpConnectionBase[1]::HandleConnect: Connect aborted to dest-ip router10.teamviewer.com:5938 with error system:125.
2018/11/24 21:00:24.346 7175-7192 E/TeamViewer KeepAliveSessionOutgoing::ConnectFailureHandler(): KeepAliveConnect to router10.teamviewer.com failed

D'ailleurs je n'arrive pas a ping l'adresse... timeout
Mais j'arrive a ping l'ip 37.252.254.175
....

[Vincent O]

D'ailleurs je n'arrive pas a ping l'adresse... timeout
Mais j'arrive a ping l'ip 37.252.254.175

Il y a une bonne vingtaine d'IP associées à ce nom

Code Sélectionner Étendre

$ host router10.teamviewer.com
router10.teamviewer.com is an alias for router10.rlb.teamviewer.com.
router10.rlb.teamviewer.com has address 217.146.8.68
router10.rlb.teamviewer.com has address 188.172.198.141
router10.rlb.teamviewer.com has address 37.252.224.71
router10.rlb.teamviewer.com has address 169.51.77.230
router10.rlb.teamviewer.com has address 37.252.254.175
router10.rlb.teamviewer.com has address 217.146.2.141
router10.rlb.teamviewer.com has address 37.252.253.103
router10.rlb.teamviewer.com has address 169.50.154.227
router10.rlb.teamviewer.com has address 178.255.155.170
router10.rlb.teamviewer.com has address 217.146.4.132
router10.rlb.teamviewer.com has address 37.252.255.203
router10.rlb.teamviewer.com has IPv6 address 2a03:8180:1402:7b::3
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:1:351:37:252:224:71
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:1f:351:217:146:2:141
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:8:351:188:172:198:141
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:1b:351:37:252:254:175
router10.rlb.teamviewer.com has IPv6 address 2a03:8180:1601:61::6
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:1a:351:37:252:253:103
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:1c:351:37:252:255:203
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:b:351:178:255:155:170
router10.rlb.teamviewer.com has IPv6 address 2a00:11c0:2a:351:217:146:4:132

J'ai testé à partir d'un de nos serveurs et j'arrive à toutes les contacter (ping et port TCP 5938) :

Code Sélectionner Étendre

$ sudo nmap -iL foo -sS -p 5938 -oG -
# Nmap 7.40 scan initiated Sat Nov 24 22:18:07 2018 as: nmap -iL foo -sS -p 5938 -oG -
Host: 217.146.8.68 (RS-BEG-ANX-R001.teamviewer.com) Status: Up
Host: 217.146.8.68 (RS-BEG-ANX-R001.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 188.172.198.141 (GB-LON-ANX-R010.teamviewer.com) Status: Up
Host: 188.172.198.141 (GB-LON-ANX-R010.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 37.252.224.71 (SI-LJU-ANX-R004.teamviewer.com) Status: Up
Host: 37.252.224.71 (SI-LJU-ANX-R004.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 169.51.77.230 (NO-OSL-IBM-R005.teamviewer.com) Status: Up
Host: 169.51.77.230 (NO-OSL-IBM-R005.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 37.252.254.175 (RU-MOW-ANX-R012.teamviewer.com) Status: Up
Host: 37.252.254.175 (RU-MOW-ANX-R012.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 217.146.2.141 (UA-IEV-ANX-R010.teamviewer.com) Status: Up
Host: 217.146.2.141 (UA-IEV-ANX-R010.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 37.252.253.103 (IT-PMO-ANX-R004.teamviewer.com) Status: Up
Host: 37.252.253.103 (IT-PMO-ANX-R004.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 169.50.154.227 (NL-AMS-IBM-R002.teamviewer.com) Status: Up
Host: 169.50.154.227 (NL-AMS-IBM-R002.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 178.255.155.170 (IT-MIL-ANX-R007.teamviewer.com) Status: Up
Host: 178.255.155.170 (IT-MIL-ANX-R007.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 217.146.4.132 (HU-BUD-ANX-R001.teamviewer.com) Status: Up
Host: 217.146.4.132 (HU-BUD-ANX-R001.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 37.252.255.203 (RU-SPB-ANX-R008.teamviewer.com) Status: Up
Host: 37.252.255.203 (RU-SPB-ANX-R008.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
# Nmap done at Sat Nov 24 22:18:08 2018 -- 11 IP addresses (11 hosts up) scanned in 1.70 seconds

$ sudo nmap -iL bar -6 -sS -p 5938 -oG -
# Nmap 7.40 scan initiated Sat Nov 24 22:18:17 2018 as: nmap -iL bar -6 -sS -p 5938 -oG -
Host: 2a03:8180:1402:7b::3 (NL-AMS-IBM-R002.teamviewer.com) Status: Up
Host: 2a03:8180:1402:7b::3 (NL-AMS-IBM-R002.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a00:11c0:1f:351:217:146:2:141 (UA-IEV-ANX-R010.teamviewer.com) Status: Up
Host: 2a00:11c0:1f:351:217:146:2:141 (UA-IEV-ANX-R010.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a00:11c0:8:351:188:172:198:141 (GB-LON-ANX-R010.teamviewer.com) Status: Up
Host: 2a00:11c0:8:351:188:172:198:141 (GB-LON-ANX-R010.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a00:11c0:1b:351:37:252:254:175 (RU-MOW-ANX-R012.teamviewer.com) Status: Up
Host: 2a00:11c0:1b:351:37:252:254:175 (RU-MOW-ANX-R012.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a03:8180:1601:61::6 (NO-OSL-IBM-R005.teamviewer.com) Status: Up
Host: 2a03:8180:1601:61::6 (NO-OSL-IBM-R005.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a00:11c0:1a:351:37:252:253:103 (IT-PMO-ANX-R004.teamviewer.com) Status: Up
Host: 2a00:11c0:1a:351:37:252:253:103 (IT-PMO-ANX-R004.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a00:11c0:1c:351:37:252:255:203 (RU-SPB-ANX-R008.teamviewer.com) Status: Up
Host: 2a00:11c0:1c:351:37:252:255:203 (RU-SPB-ANX-R008.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a00:11c0:b:351:178:255:155:170 (IT-MIL-ANX-R007.teamviewer.com) Status: Up
Host: 2a00:11c0:b:351:178:255:155:170 (IT-MIL-ANX-R007.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
Host: 2a00:11c0:2a:351:217:146:4:132 (HU-BUD-ANX-R001.teamviewer.com) Status: Up
Host: 2a00:11c0:2a:351:217:146:4:132 (HU-BUD-ANX-R001.teamviewer.com) Ports: 5938/open/tcp//teamviewer///
# Nmap done at Sat Nov 24 22:18:20 2018 -- 10 IP addresses (9 hosts up) scanned in 3.20 seconds
#


Je continue à regarder.

[Vincent O]

Directement depuis votre KBox :

Code Sélectionner Étendre

>ping 217.146.8.68
PING 217.146.8.68 (217.146.8.68) from <caché>: 56 data bytes
64 bytes from 217.146.8.68: seq=0 ttl=122 time=48.000 ms
64 bytes from 217.146.8.68: seq=1 ttl=122 time=47.000 ms
64 bytes from 217.146.8.68: seq=2 ttl=122 time=47.000 ms
64 bytes from 217.146.8.68: seq=3 ttl=122 time=47.000 ms

--- 217.146.8.68 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 47.000/47.250/48.000 ms

>ping 188.172.198.141
PING 188.172.198.141 (188.172.198.141) from <caché>: 56 data bytes
64 bytes from 188.172.198.141: seq=0 ttl=119 time=17.000 ms
64 bytes from 188.172.198.141: seq=1 ttl=119 time=17.000 ms
64 bytes from 188.172.198.141: seq=2 ttl=119 time=16.000 ms
64 bytes from 188.172.198.141: seq=3 ttl=119 time=16.000 ms

--- 188.172.198.141 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 16.000/16.500/17.000 ms

>ping 37.252.224.71
PING 37.252.224.71 (37.252.224.71) from <caché>: 56 data bytes
64 bytes from 37.252.224.71: seq=0 ttl=116 time=39.000 ms
64 bytes from 37.252.224.71: seq=1 ttl=116 time=37.000 ms
64 bytes from 37.252.224.71: seq=2 ttl=116 time=37.000 ms
64 bytes from 37.252.224.71: seq=3 ttl=116 time=37.000 ms

--- 37.252.224.71 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 37.000/37.500/39.000 ms

>ping 169.51.77.230
PING 169.51.77.230 (169.51.77.230) from <caché>: 56 data bytes
64 bytes from 169.51.77.230: seq=0 ttl=115 time=44.000 ms
64 bytes from 169.51.77.230: seq=1 ttl=115 time=44.000 ms
64 bytes from 169.51.77.230: seq=2 ttl=115 time=44.000 ms
64 bytes from 169.51.77.230: seq=3 ttl=115 time=43.000 ms

--- 169.51.77.230 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 43.000/43.750/44.000 ms

>ping 37.252.254.175
PING 37.252.254.175 (37.252.254.175) from <caché>: 56 data bytes
64 bytes from 37.252.254.175: seq=0 ttl=119 time=54.000 ms
64 bytes from 37.252.254.175: seq=1 ttl=119 time=52.000 ms
64 bytes from 37.252.254.175: seq=2 ttl=119 time=53.000 ms
64 bytes from 37.252.254.175: seq=3 ttl=119 time=52.000 ms

--- 37.252.254.175 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 52.000/52.750/54.000 ms

>ping 217.146.2.141
PING 217.146.2.141 (217.146.2.141) from <caché>: 56 data bytes
64 bytes from 217.146.2.141: seq=0 ttl=119 time=47.000 ms
64 bytes from 217.146.2.141: seq=1 ttl=119 time=47.000 ms
64 bytes from 217.146.2.141: seq=2 ttl=119 time=47.000 ms
64 bytes from 217.146.2.141: seq=3 ttl=119 time=47.000 ms

--- 217.146.2.141 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 47.000/47.000/47.000 ms

>ping 37.252.253.103
PING 37.252.253.103 (37.252.253.103) from <caché>: 56 data bytes
64 bytes from 37.252.253.103: seq=0 ttl=120 time=48.000 ms
64 bytes from 37.252.253.103: seq=1 ttl=120 time=48.000 ms
64 bytes from 37.252.253.103: seq=2 ttl=120 time=48.000 ms
64 bytes from 37.252.253.103: seq=3 ttl=120 time=48.000 ms

--- 37.252.253.103 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 48.000/48.000/48.000 ms

>ping 169.50.154.227
PING 169.50.154.227 (169.50.154.227) from <caché>: 56 data bytes
64 bytes from 169.50.154.227: seq=0 ttl=116 time=22.000 ms
64 bytes from 169.50.154.227: seq=1 ttl=116 time=21.000 ms
64 bytes from 169.50.154.227: seq=2 ttl=116 time=21.000 ms
64 bytes from 169.50.154.227: seq=3 ttl=116 time=21.000 ms

--- 169.50.154.227 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 21.000/21.250/22.000 ms

>ping 178.255.155.170
PING 178.255.155.170 (178.255.155.170) from <caché>: 56 data bytes
64 bytes from 178.255.155.170: seq=0 ttl=120 time=23.000 ms
64 bytes from 178.255.155.170: seq=1 ttl=120 time=22.000 ms
64 bytes from 178.255.155.170: seq=2 ttl=120 time=22.000 ms
64 bytes from 178.255.155.170: seq=3 ttl=120 time=22.000 ms

--- 178.255.155.170 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 22.000/22.250/23.000 ms

>ping 217.146.4.132
PING 217.146.4.132 (217.146.4.132) from <caché>: 56 data bytes
64 bytes from 217.146.4.132: seq=0 ttl=119 time=39.000 ms
64 bytes from 217.146.4.132: seq=1 ttl=119 time=38.000 ms
64 bytes from 217.146.4.132: seq=2 ttl=119 time=39.000 ms
64 bytes from 217.146.4.132: seq=3 ttl=119 time=39.000 ms

--- 217.146.4.132 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 38.000/38.750/39.000 ms

>ping 37.252.255.203
PING 37.252.255.203 (37.252.255.203) from <caché>: 56 data bytes
64 bytes from 37.252.255.203: seq=0 ttl=119 time=58.000 ms
64 bytes from 37.252.255.203: seq=1 ttl=119 time=183.000 ms
64 bytes from 37.252.255.203: seq=2 ttl=119 time=83.000 ms
64 bytes from 37.252.255.203: seq=3 ttl=119 time=62.000 ms

--- 37.252.255.203 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 58.000/96.500/183.000 ms

>ping 2a03:8180:1402:7b::3
PING 2a03:8180:1402:7b::3 (2a03:8180:1402:7b::3) from <caché>: 56 data bytes
64 bytes from 2a03:8180:1402:7b::3: seq=0 ttl=118 time=18.000 ms
64 bytes from 2a03:8180:1402:7b::3: seq=1 ttl=118 time=18.000 ms
64 bytes from 2a03:8180:1402:7b::3: seq=2 ttl=118 time=18.000 ms
64 bytes from 2a03:8180:1402:7b::3: seq=3 ttl=118 time=18.000 ms

--- 2a03:8180:1402:7b::3 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 18.000/18.000/18.000 ms

>ping 2a00:11c0:1f:351:217:146:2:141
PING 2a00:11c0:1f:351:217:146:2:141 (2a00:11c0:1f:351:217:146:2:141) from <caché>: 56 data bytes
64 bytes from 2a00:11c0:1f:351:217:146:2:141: seq=0 ttl=113 time=54.000 ms
64 bytes from 2a00:11c0:1f:351:217:146:2:141: seq=1 ttl=113 time=53.000 ms
64 bytes from 2a00:11c0:1f:351:217:146:2:141: seq=2 ttl=113 time=53.000 ms
64 bytes from 2a00:11c0:1f:351:217:146:2:141: seq=3 ttl=113 time=53.000 ms

--- 2a00:11c0:1f:351:217:146:2:141 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 53.000/53.250/54.000 ms

>ping 2a00:11c0:8:351:188:172:198:141
PING 2a00:11c0:8:351:188:172:198:141 (2a00:11c0:8:351:188:172:198:141) from <caché>: 56 data bytes
64 bytes from 2a00:11c0:8:351:188:172:198:141: seq=0 ttl=119 time=16.000 ms
64 bytes from 2a00:11c0:8:351:188:172:198:141: seq=1 ttl=119 time=16.000 ms
64 bytes from 2a00:11c0:8:351:188:172:198:141: seq=2 ttl=119 time=16.000 ms
64 bytes from 2a00:11c0:8:351:188:172:198:141: seq=3 ttl=119 time=15.000 ms

--- 2a00:11c0:8:351:188:172:198:141 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 15.000/15.750/16.000 ms

>ping 2a00:11c0:1b:351:37:252:254:175
PING 2a00:11c0:1b:351:37:252:254:175 (2a00:11c0:1b:351:37:252:254:175) from <caché>: 56 data bytes
64 bytes from 2a00:11c0:1b:351:37:252:254:175: seq=0 ttl=119 time=54.000 ms
64 bytes from 2a00:11c0:1b:351:37:252:254:175: seq=1 ttl=119 time=52.000 ms
64 bytes from 2a00:11c0:1b:351:37:252:254:175: seq=2 ttl=119 time=53.000 ms
64 bytes from 2a00:11c0:1b:351:37:252:254:175: seq=3 ttl=119 time=53.000 ms

--- 2a00:11c0:1b:351:37:252:254:175 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 52.000/53.000/54.000 ms

>ping 2a03:8180:1601:61::6
PING 2a03:8180:1601:61::6 (2a03:8180:1601:61::6) from <caché>: 56 data bytes
64 bytes from 2a03:8180:1601:61::6: seq=0 ttl=115 time=41.000 ms
64 bytes from 2a03:8180:1601:61::6: seq=1 ttl=115 time=41.000 ms
64 bytes from 2a03:8180:1601:61::6: seq=2 ttl=115 time=41.000 ms
64 bytes from 2a03:8180:1601:61::6: seq=3 ttl=115 time=41.000 ms

--- 2a03:8180:1601:61::6 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 41.000/41.000/41.000 ms

>ping 2a00:11c0:1a:351:37:252:253:103
PING 2a00:11c0:1a:351:37:252:253:103 (2a00:11c0:1a:351:37:252:253:103) from <caché>: 56 data bytes
64 bytes from 2a00:11c0:1a:351:37:252:253:103: seq=0 ttl=118 time=122.000 ms
64 bytes from 2a00:11c0:1a:351:37:252:253:103: seq=1 ttl=118 time=121.000 ms
64 bytes from 2a00:11c0:1a:351:37:252:253:103: seq=2 ttl=118 time=122.000 ms
64 bytes from 2a00:11c0:1a:351:37:252:253:103: seq=3 ttl=118 time=121.000 ms

--- 2a00:11c0:1a:351:37:252:253:103 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 121.000/121.500/122.000 ms

>ping 2a00:11c0:1c:351:37:252:255:203
PING 2a00:11c0:1c:351:37:252:255:203 (2a00:11c0:1c:351:37:252:255:203) from <caché>: 56 data bytes
64 bytes from 2a00:11c0:1c:351:37:252:255:203: seq=0 ttl=119 time=52.000 ms
64 bytes from 2a00:11c0:1c:351:37:252:255:203: seq=1 ttl=119 time=55.000 ms
64 bytes from 2a00:11c0:1c:351:37:252:255:203: seq=2 ttl=119 time=66.000 ms
64 bytes from 2a00:11c0:1c:351:37:252:255:203: seq=3 ttl=119 time=256.000 ms

--- 2a00:11c0:1c:351:37:252:255:203 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 52.000/107.250/256.000 ms

>ping 2a00:11c0:b:351:178:255:155:170
PING 2a00:11c0:b:351:178:255:155:170 (2a00:11c0:b:351:178:255:155:170) from <caché>: 56 data bytes
64 bytes from 2a00:11c0:b:351:178:255:155:170: seq=1 ttl=114 time=146.000 ms
64 bytes from 2a00:11c0:b:351:178:255:155:170: seq=2 ttl=114 time=594.000 ms
64 bytes from 2a00:11c0:b:351:178:255:155:170: seq=3 ttl=114 time=145.000 ms

--- 2a00:11c0:b:351:178:255:155:170 ping statistics ---
4 packets transmitted, 3 packets received, 25% packet loss
round-trip min/avg/max = 145.000/295.000/594.000 ms

>ping 2a00:11c0:2a:351:217:146:4:132
PING 2a00:11c0:2a:351:217:146:4:132 (2a00:11c0:2a:351:217:146:4:132) from <caché>: 56 data bytes
64 bytes from 2a00:11c0:2a:351:217:146:4:132: seq=0 ttl=119 time=36.000 ms
64 bytes from 2a00:11c0:2a:351:217:146:4:132: seq=1 ttl=119 time=35.000 ms
64 bytes from 2a00:11c0:2a:351:217:146:4:132: seq=2 ttl=119 time=36.000 ms
64 bytes from 2a00:11c0:2a:351:217:146:4:132: seq=3 ttl=119 time=35.000 ms

--- 2a00:11c0:2a:351:217:146:4:132 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 35.000/35.500/36.000 ms

>



[Vincent O]

D'ailleurs je n'arrive pas a ping l'adresse... timeout
Mais j'arrive a ping l'ip 37.252.254.175
....

Vous testez à partir d'où, un ordinateur derrière la KBox ? Pourriez-vous faire une capture d'écran du "ping de l'adresse" qui timeout, et faire un tracert aussi ? À partir de la KBox elle même ça passe. Je ne peux malheureusement pas tester si les ports sont accessibles à partir de la KBox v2. Par contre j'ai testé chez d'autres clients du même subnet et ça marchait, donc ce n'est pas une pool d'IP blacklisté ou un problème de routage sur le réseau lui même.

[reverse62]

Je ne sais pas comment ni pourquoi mais la je passe apres la 3eme ou 2eme tentative.
J'ai répété plusieurs fois et ca passe...

[reverse62]

Je voudrais bien, mais la le ping passe sur l'adresse ..
A ne rien comprendre...

[reverse62]

Bonjour.
Ce matin, de nouveau impossible de se connecter.
Hier soir avec la méthode des 2/3 tentatives ca fonctionnait....