<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>openATTIC (Posts about ktpass)</title><link>/</link><description></description><atom:link href="https://openattic.org/categories/ktpass.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Thu, 22 Aug 2019 20:00:55 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Windows AD keytab file and ktutil merge</title><link>https://openattic.org/posts/windows-ad-keytab-file-and-ktutil-merge/</link><dc:creator>Kai Wagner</dc:creator><description>&lt;div&gt;&lt;p&gt;If you ever plan to setup a clustered samba fileserver within a windows active directory infastructure you'll need the following things.&lt;/p&gt;
&lt;p&gt;The problem in a clustered samba environment is, that the clients always wants to connect their network share with the same hostname/machine account.&lt;/p&gt;
&lt;p&gt;It would be possible to just use the cluster ip instead of a new machine account, but then your users/clients will always get that popup within their office programs, that this isn't a trusted location.&lt;/p&gt;
&lt;p&gt;To get rid of that annoying problem you have to create a new machine account and merge that keytab into your existing one on your samba servers.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://openattic.org/posts/windows-ad-keytab-file-and-ktutil-merge/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>kerberos</category><category>keytab</category><category>ktpass</category><category>ktuil</category><category>windows ad</category><guid>https://openattic.org/posts/windows-ad-keytab-file-and-ktutil-merge/</guid><pubDate>Fri, 21 Oct 2016 10:45:18 GMT</pubDate></item></channel></rss>