Skip to main content

Cannot join domain - 'network name no longer available' & 'access denied' DHCP authorizing

(sorry for the long title)

We ran into an interesting problem I wanted to document here, hopefully it will help someone else out.

At head office: Old call center is being moved to a new building, but cannot have any downtime. We are getting infrastructure set up (DC/proxy/etc) ahead of time. We had a test network set up at head office but it was having issues (ADSL flapping), so while on the new IP subnet we were not able to join the domain (seeing 'network name no longer available' error). We figured this was due to the flapping, and we decided to leave the join/promote to when we were local.

Catch to the setup: We cannot see two of the four DCs, as our hub/spoke network design does not allow the spokes (remote offices) to see each other, only to see the hub (head office). This is fine, as we have two DCs at the spoke office, and two DCs at the head office (for this child domain...not in total).

At the remote office: Same issue persists, but we no longer have the flapping.

1. We could ping the FQDN of the domain: child.domain.local
2. We could ping the DCs involved (the two at the head office).

We brainstormed, checked security settings, disabled firewalls, telnetted to ports, and eventually we ticked on there being multiple roles, and some are only set on specific DCs (naming master, ops master, infrastructure master, etc). Last year they moved several key roles down to the remote site to speed up logon times. It turns out that you need these roles to join the domain.

The roles were moved back to the two DCs at the head office, and we were able to join the domain immediately, and promote it to DC without any issues as well.

One last issue cropped up - the new DHCP scope could not be authorized. It could be created, services started, but not authorized. A little research turned up that for CHILD domains, only ENTERPRISE admins could authorize scopes. Small point, but pretty key!! Gave the correct permissions, and authorized the scope.


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…