Martin W.

[Martin W. @WisiM15]

@Broadcom @VMware Consistent with this please fix the certificate from https://t.co/epCSgtoMRh.

[Martin W. @WisiM15]

@lancom_systems Schön, dass man in der KB sein Wissen teilt, aber scheinbar nicht in der Lage ist innerhalb von MONATEN mit Kunden zu kommunizieren, es sei denn Sie schmeißen für eine Antwort direkt Geld in die Spardose. Schade, damit fällt einer der Gründe warum man Lancom empfehlen könnte weg.

[Martin W. @WisiM15]

@Telekom_hilft wie wäre es damit in den T@School Tarifen feste IP Adressen einzuführen? Es könnte ja vielleicht sein, dass eine Schule Inhalte für die Schüler bereitstellen will... Schön wenn man jetzt Glasfaser hat, aber ohne macht das keinen Spaß... #DeutscheTelekom #festeIP

[Martin W. @WisiM15]

@XiaomiDE ich wollte schon immer mal Brandlöcher in meinem OSB haben... Wer hat bitte den Dock für den Roborock S5 konstruiert und wie kann das passieren???

[Martin W. @WisiM15]

@AtosUnify NFS is not CIFS... #SDHC #Backup #FX8 #V2

[Martin W. @WisiM15]

@weismichael #OnePlus8Pro natürlich ;) Mal sehen wann 10 in Deutschland ankommt :)

[Martin W. @WisiM15]

@NortonSupport You still have problems! https://t.co/5zgEnLCQAf

[Martin W. @WisiM15]

@NortonSupport Every primary DNS is suspicious! That is really a security problem Norton! You should have tested it on your own, it is so easy to test...

[Martin W. @WisiM15]

@NortonSupport Problem also exists on 199.85.126.10 but not on 199.85.127.10, also on 199.85.126.20 but not on 199.85.127.20, same on 199.85.126.30 and co.

[Martin W. @WisiM15]

@NortonSupport On 198.153.192.40 the problem still persists, while I can't detect it furthermore on 198.153.194.40. So please take a look there!

[Martin W. @WisiM15]

@NortonSupport Couldn't reproduce the error in a short test. So it seems to be fixed or at least better than before. Will see after holidays...

[Martin W. @WisiM15]

@NortonSupport Still not solved... DNS Server is still delivering wrong IP addresses for SSL sites which is really a problem for security, too...

[Martin W. @WisiM15]

@NortonSupport Is the team awaka again? #fast #notnorton

[Martin W. @WisiM15]

@NortonSupport And now? Again two days... But it could be more simple, we already changed DNS provider to solve our problems. So you can take another year.

[Martin W. @WisiM15]

@NortonSupport Germany, near Wuerzburg.

[Martin W. @WisiM15]

@NortonSupport Problem still persists with your DNS servers. So you know that I sent you the error for OVER a week now? #security #fast #notnorton

[Martin W. @WisiM15]

@NortonSupport Again a day over and no solution. When do you think you get it solved finally? Otherwise we have to look for another DNS solution...

[Martin W. @WisiM15]

@NortonSupport Hello, see https://t.co/OLLArVGXNL. 199.85.126.20 has the same problem, 199.85.127.20 seems to be clean. It can't be that difficult, man...

[Martin W. @WisiM15]

@NortonSupport This is ridiculous, seems that someone fixed the specific addresses but not the problem itself... after days! https://t.co/OuVFmuVhkR

[Martin W. @WisiM15]

@NortonSupport Are you sure that Norton is a security company? This problem IS an important security and you don't get it within 24h?