6 Mar
2017
6 Mar
'17
11:23 p.m.
Am 02.03.2017 00:39:08, "Conrad Kostecki" <ck+atlasripe@bl4ckb0x.de> schrieb:
Any ideas? I've found the cause. It was a small typo for the assigned DNS server via DHCP. After setting the correct one, the probe is now working correctly.
But it's strange, because the wrong DNS is also reachable via ThinkPad, but is in a different subnet. It should have worked with the probe. Anyway, it's working now. Cheers Conrad