Archive for January, 2017

Can’t join a Windows 2012 server to a 2003 forest

January 21, 2017

Simple solution but here’s the scenario;

I had to replace a 2003 server with a 2012 server. So the original forest and domain is 2003 (I had to upgrade that from 2000!) but when I tried to promote the 2012 server to a DC it balked with this error;

“A domain controller running 2008 or later could not be located in this domain.”

I did some digging and found that it’s really not stopping you but prompting you to put in a recovery password. Thanks for the intuitive message MS.

So simply type in a recovery password and it will allow you to continue the promotion.

Ref: https://social.technet.microsoft.com/Forums/sharepoint/en-US/87876f09-90e6-4548-bdb6-7b1e525951be/adding-a-windows-2012-dc-to-a-windows-2003-forest?prof=required

Advertisements

Meraki Client VPN woes

January 7, 2017

I just spent two + hours trying to figure this out.

Setting the scene;

L2TP client VPN intermittently working…

Client VPN’s had been working just fine with a mix of Mac and Windows.

Today it might take 10 attempts to connect before it’s successful!


I will get right to the point. The issue was caused by a combination of Meraki having a bug and Comcast’s DNS being terrible.

We had configured our MX device to use Google’s DNS as primary and Comcast as secondary.

Beleive it or not but the problem was caused because of putting Comcast’s DNS in as a secondary. This is bug with Meraki as I said because all the DNS servers are referenced when the VPN is attempting to estabish. If ANY of the DNS servers don’t respond or are very delayed then your VPN won’t work.

The fix? Changed the secondary to Google’s secondary (8.8.4.4) and boom. Works flawlessly.

[Emoji with the rolling eyes]

Stay strong out there 🙂