Domain Issues

I run a computer lab in a college that is on it's own domain so that we can teach the server2012 courses. We connect to the school network for internet and run a seperate domain to minimize any issues. This has worked without any problems for over a year until just the last week or so...

Over the summer the school has changed the way their network is set up so that instead of registering as "Network" on the adapters, it now registers as "ad.xxxx.edu". Now our lab computers recognize our domain as "Unidentified network" and will not allow our students to log on, saying "no logon servers are available to process the request". I have not had any issues before the schools domain started broadcasting as an actual domain, before being shown as a private network, and have been told by some others in the IT world that Windows 8.1 cannot register to two domains at the same time. 

I can log on to any of the machines that have a profile cached on them, and when I disable the network adapter and then reenable it, and the computer will identify the lab domain. This leads me to believe that the machines CAN be on both networks at the same time, they just need to be told to do so. 

This leaves me either coming in to the lab early, logging on to each machine, joining it to the domain and signing out so the students can then sign in when they get to school, OR finding a solution to the problem. Guess which I would prefer! 

I have tried setting up the adapters to find the school network first in the advanced settings in the network adapter window and this doesn't solve the problem, they still come up as an unidentified network. Any other suggestions would be VERY appreciated!

August 23rd, 2015 9:30pm

Hi,

According to your description, I suppose that this issue might be due to this scenario:

There are 2 AD environment: a public and private AD. You just used the public AD before, and now the accounts access the private AD. If you still assign IP addresses automatically using DHCP, they will access the IP address and DNS server of private AD. Thus, you can't log on. 

I recommend you assign the static IP address and DNS of private AD to check if it is helpful.

If you have further question about AD configuration, you can ask in AD forum:

https://social.technet.microsoft.com/Forums/windowsserver/en-Us/home?forum=winserverDS

Regards,


George Zhao
Forum Support

Free Windows Admin Tool Kit Click here and download it now
August 25th, 2015 3:34am

Hi,

According to your description, I suppose that this issue might be due to this scenario:

There are 2 AD environment: a public and private AD. You just used the public AD before, and now the accounts access the private AD. If you still assign IP addresses automatically using DHCP, they will access the IP address and DNS server of private AD. Thus, you can't log on. 

I recommend you assign the static IP address and DNS of private AD to check if it is helpful.

If you have further question about AD configuration, you can ask in AD forum:

https://social.technet.microsoft.com/Forums/windowsserver/en-Us/home?forum=winserverDS

Regards,


George Zhao
Forum Support

August 25th, 2015 7:33am

Hi,

According to your description, I suppose that this issue might be due to this scenario:

There are 2 AD environment: a public and private AD. You just used the public AD before, and now the accounts access the private AD. If you still assign IP addresses automatically using DHCP, they will access the IP address and DNS server of private AD. Thus, you can't log on. 

I recommend you assign the static IP address and DNS of private AD to check if it is helpful.

If you have further question about AD configuration, you can ask in AD forum:

https://social.technet.microsoft.com/Forums/windowsserver/en-Us/home?forum=winserverDS

Regards,


George Zhao
Forum Support

Free Windows Admin Tool Kit Click here and download it now
August 25th, 2015 7:33am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics