I'll try explain the setup and the problem as best i can, but please be patient with me. Im new to AD troubleshooting and its taken me about a week to fully figure out the setup alone.
We have got 2 External sites, each with a 2Mb BIP connection to our main site. Initally, i believe the plan was to have a DC on each site and for each site to be a child domain of the domain in the main site. Im not sure how this is achieved but we were led to believe that each site would be independant in that if the link between one of the external sites and the main site goes down, external sites would not be affected. Their users would still be able to log on to their local domains witout any hastle.
The frst time the connection between a site went down, the users were frozen out. They were unable to log on to their local domain, nor were they able to access any information stored on the local servers.
So, the decision was then taken to change the setup in this site so that they were logging onto the domain in the main site. The DC in that site, i am led to believe, is now an equal DC within the domain. So now, when the users in that site logon, the are doing so to the main domain, but through the local DC. This works fine until the link is broke. Once that happens, the same problem outlines above occurs.
Complications.
The main complication in the the external site with all the problems is that there are 2 companys on the site. We have some of our own staff there, who share the site with a sister company. Its only a small company run by the brother of our MD, but we are IT support for them. Thats ok until even the smallest thing goes wrong, then they make noise and IT take all the flack. So when they cannot access their information, IT should just leave the country!!!! So as a result we tend to keep a low profile in that site and would like to do as much as possible from our main site.
And to complicate things further, the guy who set everything up, has since left the company. He was the only one of the IT dept with AD experience. He also had drafted in some ouside help (a guy who "understood" AD and how to set it up) He has being out on site 3 times now, but is still unable to solve the problem, and wont be back either.
If any one can help, or if you need more information, just let me know.
Thanks for reading, and sorry for the long post.
Paddy.
We have got 2 External sites, each with a 2Mb BIP connection to our main site. Initally, i believe the plan was to have a DC on each site and for each site to be a child domain of the domain in the main site. Im not sure how this is achieved but we were led to believe that each site would be independant in that if the link between one of the external sites and the main site goes down, external sites would not be affected. Their users would still be able to log on to their local domains witout any hastle.
The frst time the connection between a site went down, the users were frozen out. They were unable to log on to their local domain, nor were they able to access any information stored on the local servers.
So, the decision was then taken to change the setup in this site so that they were logging onto the domain in the main site. The DC in that site, i am led to believe, is now an equal DC within the domain. So now, when the users in that site logon, the are doing so to the main domain, but through the local DC. This works fine until the link is broke. Once that happens, the same problem outlines above occurs.
Complications.
The main complication in the the external site with all the problems is that there are 2 companys on the site. We have some of our own staff there, who share the site with a sister company. Its only a small company run by the brother of our MD, but we are IT support for them. Thats ok until even the smallest thing goes wrong, then they make noise and IT take all the flack. So when they cannot access their information, IT should just leave the country!!!! So as a result we tend to keep a low profile in that site and would like to do as much as possible from our main site.
And to complicate things further, the guy who set everything up, has since left the company. He was the only one of the IT dept with AD experience. He also had drafted in some ouside help (a guy who "understood" AD and how to set it up) He has being out on site 3 times now, but is still unable to solve the problem, and wont be back either.
If any one can help, or if you need more information, just let me know.
Thanks for reading, and sorry for the long post.
Paddy.
