Alle Beiträge von admin

WLAN Profile unter WIN 10 löschen.

Wenn Win 10 mal nicht zu einem eigentlich bekannten WLAN verbinden will, kann man so die vorhandenen WLAN Profile anzeigen…
  1. Kommandozeile öffnen: Windows Taste drücken und CMD eingeben.
  2. WLAN Profile anzeigen: „netsh wlan show profiles“

… und das Betroffene dann löschen: „netsh wlan delete profile name=“PROFILNAME“

Dann einfach neu connecten.

Vorsätze für 2017: Mehr lesen.

Nico hatte sich im letzten Jahr den Vorsatz genommen, mehr zu lesen. Find ich toll, will ich auch. 52 Bücher in einem Jahr sind für mich allerdings vollkommen utopoisch, aber ich habe mir ein paar seiner Bücher abgeschaut und wollte hier meine Leseliste für 2017 festhalten. Eine willkürliche Auswahl, to be continued.

  1. How to read a book.

    Als theoretische Basis. Mal schauen ob ich es noch kann 😉
  2. Originals: How Non-Conformists Move the World
  3. The life changing magic of not giving a f**k
  4. Auerhaus
  5. Konklave.

Da kommt dann sicherlich noch das ein- oder andere dazu. Inspiration, was es so zu lesen gibt, gibt es z.b. dann auch auf sowas wie Goodreads.

Seer – Quick Look for Windows 10

On my journey on a switch from OS X to Windows 10 one of the missing bits in the daily usage was the „Quick Look“ / Preview feature in OS X. Its annoying having to double click in explorer lists, just to see whats in the  file.

Throwing in seer, which does exactly that – its customizable with shortcuts and extendable via plugins (autocad, office etc.).

seer2.JPG

The office plugin isn’t the best to be honest, the natve picture, pdf etc. previes are working as expected: fast and stable.

And then I found MobaXterm

The only thing which was sticking me to OS X was the abiltiy to use the terminal for ssh connections and native stuff.

Well, I just found mobaxterm for windows which is SO_MUCH_MORE than just a terminal, its a joke I didn’t find out earlier about it. Its a cygwin wrapper, but only roughly 20MB.

Its not only a full blown xterm, but it´s

  • build in graphical sftp client which follows the terminal (!) (dragndrop)
  • tabbed ssh terminal
  • Lean Texteditor
  • VNC client
  • graphical SSH tunnel builder
  • Network Scanner
  • Portscanner
  • Network Packets capturing
  • and much more

I have to say I am truly impressed – its a huge productivity boost for me.

Hint, if you need to find the bin folder: echo „/bin PATH = $(cygpath -w /bin)“

Connecting from a Windows 10 client through L2TP/IPSEC to OSX Server

In a series of posts I am documenting my switch from an osx only world to a windows 10 client. This time: connecting to a L2TP/IPSEC VPN to a server running OS X Server 10.6.8 where the setup is like this:

Screenshot 2016-12-11 15.57.59.png

So let`s begin on the windows 10 side:

  • create a new VPN network connection in the network center
  • right click properties -> General: add a hostname
  • Options -> set PPP options
    network1.JPG
  • Security Settings
    network2.JPG
  • note the pre-shared key, you’ll set it in the os x server settings later on.
  • Now follow exactly these steps in order to set the correct security settings for your windows 10 client. note: these worked for me despite it says windows 7
  • Restart Windows

Now, for the gateway in order to get the traffic for L2TP / IPSec correctly tunneled I needed to forward these ports to my local server:

  • UDP 45, 500, 4500, 1701

As I am using a Zyxel Speedlink 5501, this looked like this (Web-Administration > Security > Port-Forwarding):
Screenshot 2016-12-11 16.24.37.png

On the OS X Server side, I set up the VPN through the Server Admin panel. I used MS-Chapv2 and a shared secret:
Screenshot 2016-12-11 16.26.27.png

Of course, you need to have a valid user/password for the server machine in order to connect succesfully.

Update 1: After a 1st test this broke my smb connections from the win 10 to another osx client on the network. 🙁

Update 2: fixed the problem above. To either connect to OS X Server via VPN or to another OS X machine it is „OK“ to set the „Network Security: LAN Manager authentication level“ to „Send NTLMv2 response only“. I was still able to connect to the VPN successfully.
network3.JPG