Jump to content

So long story short. I scored an Intel server with 2 Quad Core Xeon's, dual redundant PSUs, and 64 GB ram for $200 USD!!

 

I am a member of Dream Spark so I installed Server 2012 R2 with a legit key.

I own the domain InsanityStudios.com through Google Domains.

 

I had set up the AD DS for InsanityStudios.com and have my primary NIC set to loopback on the DNS.

I have set up the DNS zones for the Domain as well for my local controllers and have it through a DMZ on my router (Running DD-WRT)

 

When I try to join InsanityStudios.com on my other machines I get an error trying to hit the DC stating it may not be running. I have also tried via the NetBIOS name with no luck.

 

Its not a super important server, as it only will be used for testing purposes for the field of study I am in. But it would be great to have it working.

 

I appreciate any advice anyone would have. I am even willing to give you my static ip and login information if your willing to lend a hand!

 

Thanks guys!

 

Link to post
Share on other sites

Why do you domains? would different user be much easier in your case?

Magical Pineapples


 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Link to post
Share on other sites

On ‎3‎/‎11‎/‎2016 at 10:30 PM, MrUnknownEMC said:

Why do you domains? would different user be much easier in your case?

I could use the user mode and not domain, however I need a domain controller to work with Active Directory. I own a small Indie Development studio and need to manage rights via security groups for different users, giving access to different resources per user and so on.

Link to post
Share on other sites

10 hours ago, seanbisepic said:

@CrazyCori, have you updated the DNS settings on the client to point to the AD DS yet? If not, then the client will be attempting to connect to an unknown DNS name.

Thanks for the reply Seanbiseptic. This was exactly my issue, unfortunately I fixed it before I saw your reply. It was exactly that, had to set my internal machines DNS's to 8.8.8.8 so now it resolves via google then back to the DC. Thank again tho

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×