49 lines
2.9 KiB
Markdown
49 lines
2.9 KiB
Markdown
Hallo,
|
|
wir nutzen oben genannte Storage Box für den Datenaustausch mit verschiedenen Kunden.
|
|
Einer der Kunden kann seit dem 25. Juli nicht mehr von seinem Firmennetzwerk darauf zugreifen.
|
|
|
|
Wir haben auf dem Linux Server beim Kunden folgende Tests durchgeführt:
|
|
|
|
cargodb@cargodb:~$ sftp -v -oPort=22 u248962-sub1@u248962.your-storagebox.de
|
|
OpenSSH_8.2p1 Ubuntu-4ubuntu0.3, OpenSSL 1.1.1f 31 Mar 2020
|
|
debug1: Reading configuration data /etc/ssh/ssh_config
|
|
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/_.conf matched no files
|
|
debug1: /etc/ssh/ssh_config line 21: Applying options for _
|
|
debug2: resolving "u248962.your-storagebox.de" port 22
|
|
debug2: ssh_connect_direct
|
|
debug1: Connecting to u248962.your-storagebox.de [78.47.94.120] port 22.
|
|
debug1: connect to address 78.47.94.120 port 22: Connection refused
|
|
debug1: Connecting to u248962.your-storagebox.de [2a01:4f8:2b01:db::2] port 22.
|
|
debug1: connect to address 2a01:4f8:2b01:db::2 port 22: Network is unreachable
|
|
ssh: connect to host u248962.your-storagebox.de port 22: Network is unreachable
|
|
Connection closed.
|
|
|
|
cargodb@cargodb:~$ nc -zv u248962-sub1@u248962.your-storagebox.de 22
|
|
nc: getaddrinfo for host u248962-sub1@u248962.your-storagebox.de port 22: Name or service not known
|
|
|
|
cargodb@cargodb:~$ tcptraceroute u248962.your-storagebox.de 22
|
|
Selected device ens160, address 192.168.83.3, port 52113 for outgoing packets
|
|
Tracing the path to u248962.your-storagebox.de (78.47.94.120) on TCP port 22 (ssh), 30 hops max
|
|
1 192.168.83.254 0.233 ms 0.175 ms 0.242 ms
|
|
2 82-198-218-38.briteline.de (82.198.218.38) 1.470 ms 1.103 ms 2.286 ms
|
|
3 10.200.48.254 0.930 ms 0.915 ms 0.776 ms
|
|
4 82-198-192-194.briteline.de (82.198.192.194) 1.092 ms 1.114 ms 0.902 ms
|
|
5 82-198-216-168.briteline.de (82.198.216.168) 1.101 ms 1.168 ms 1.034 ms
|
|
6 ae0-201.cr11.bre04.lwlcom.net (31.209.93.121) 1.543 ms 1.650 ms 1.528 ms
|
|
7 ae0-30.cr10.bre09.lwlcom.net (185.146.230.97) 7.713 ms 7.440 ms 11.215 ms
|
|
8 ae0-10.cr11.bre09.lwlcom.net (185.146.230.53) 7.647 ms 7.652 ms 7.617 ms
|
|
9 ae0-20.cr10.bre03.lwlcom.net (185.146.230.99) 7.530 ms 7.716 ms 7.505 ms
|
|
10 ae7-90.cr10.bre11.lwlcom.net (185.146.230.34) 7.723 ms 7.661 ms 7.578 ms
|
|
11 ae7-100.cr10.lut01.lwlcom.net (185.146.230.39) 7.446 ms 7.509 ms 7.673 ms
|
|
12 ae6-100.cr10.fra03.lwlcom.net (185.146.230.27) 7.980 ms 7.281 ms 7.981 ms
|
|
13 ae2-100.cr10.fra04.lwlcom.net (185.146.230.51) 7.287 ms 7.392 ms 7.406 ms
|
|
14 213-133-121-205.clients.your-server.de (213.133.121.205) 10.464 ms 10.542 ms 10.573 ms
|
|
15 core24.fsn1.hetzner.com (213.239.224.85) 16.458 ms 16.381 ms 16.338 ms
|
|
16 mx10k1.dc3.fsn1.hetzner.com (213.239.254.142) 16.632 ms 16.687 ms 24.837 ms
|
|
17 static.120.94.47.78.clients.your-server.de (78.47.94.120) 16.526 ms !p 16.509 ms !p 16.505 ms !p
|
|
|
|
Können Sie anhand dieser Daten erkennen worin das Problem besteht? Andere Kunden können die Storage Box problemlos nutzen.
|
|
|
|
Vielen Dank für Ihre Hilfe
|
|
Mit freundlichen Grüßen
|
|
Ralph Soika
|