Good day!

I am a sole-IT Manager for a 100 person engineering firm–we have 3 remote offices that are connected to our main office via UniFi’s Site Magic, essentially a site-to-site VPN, from my understanding. I am having an issue where if I create a brand new user in the DC, and the employee tried to log in with the credentials I gave them, they get the error “We can’t sign you in with the credential, as the DC is unavailable.” However, local, cached logins work fine, and network drives connect for those users that are already signed in.

Some things to note–our DC is a Synology RackStation running Synology Directory (and DNS) Server…Windows Server 2008 equivalent. Not ideal by any means, but it’s what we have, and what has worked for us for a while.

The laptops are connected over wifi, which is on the same network that is linked via Site Magic to our main office. I can ping the DC from the remote office, and DNS is set at the router level to the DC DNS.

What else can I check to see what the issue could be? Our offices are about 2 hrs away each direction, so if need be, I can always bring the laptop to the main office, do a gpupdate/force, login, and drive back down, but I imagine one shouldn’t need to do that each time a new hire starts.

I appreciate your help for this new-ish IT Manager starting his career!

4 Spice ups

Do the individual clients use the DC server ip address as their dns server?
Is the local router (Unifi device) providing DCHP - and if so what is the dns suffix it is setting?
It needs to be the AD(synology directory) domain name.

In theory it can work with the dns server being the local router (unifi) and this forwarding all DNS to the synology DC - but make sure it really is forwarding all dns and not using the ISP dns.

As a test manually set the DNS server setting on a client to use the synology DC IP. Then test logging on with a new user.