Question Locked

Location of Windows domain controllers

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
After having managed a WAN consisting of 8 networks, I have now taken a new job. I am no longer in control of the network, but I have noticed problems here that I have never seen before. When I was in charge, I always made sure that every network had its own domain controller. Here, instead of networks, they are using vlans. The administrative vlan does not have a domain controller. We cannot create home folders because the domain controllers cannot see the servers on which the home folders would reside, and sometimes login scripts do not run. There are other problems with several software packages such as antivirus and SMS. My thought is that placing one of the two existing domain controllers, which both on another vlan, on this vlan would resolve the problems. What do you think?

6 replies

by churdoo

There's not enough info in your post to try to determine why the VLANs and DCs are designed and placed the way they are.

However, I agree that it seems like things are not set up correctly and that something should be done, whether the solution is to change the VLAN membership of the DC and/or other servers, or to route between the VLANs so you have proper access to infrastructure resources.

by ltheodor

There is definitely an issue here. I may not be in control of how the network is set up here, but I keep running into dead ends in the process of doing my job because so many things do not work here. I am not the only one who is experiencing problems.

by genera-nation

You state - 'I am no longer in control of the network'. So leave it to the people who are.
Perhaps you could approach the persons who are in control?

by merlin the wiz

Is this the same network you were managing or a new one? If it is a new one, you MUST obtain an overview of the network setup. Vlans are VERY much like LANS and WANS, with the exception that a lot of the features and functions that esict in the hardware world do not exist (yet) in the virtual world.
I assume you want to share home folder information between virtual units.
As I understand virtual systems, You MUST have at least one virtual server in the system, or you are basically running a peer-to-peer network. And with Windows home folders can only be created only on the local pc. With windows sharing is NOT allowed unless EACH folder or drive (virtual or otherwise) is individually shared on that specific machine. Windows has the ability to restrict sharing through user rights, but this also requires a virtual server to provide a mechanism to manage the system. Depending upon the vlan software you are running, a virtual server application software package may not be available. And even if it does it may not allow folder sharing even with a virtual server. This is a VERY complicated. To sum this up in my opinion you need to add a virtual server to the system that has the ability to manage user rights. Is there a possibility of creating a virtual server on one of the existing DC's or are they running close to capacity with no capability of adding virtual server capability?

by mikeehlinger

This sounds like the router is not aware of the vlans or is not properly configured to move packets between them.

This discussion is closed to new replies.