what solution are you using for IP PBX ???

@Minion-Queen said:

59 ping
37.7/5.25

that's a good bandwidth, are you using this connection for data also or that is for voip only??

a codec also influence the RTP traffic, how much is your bandwidth ??

thanks for sharing

Sure we do. NTG has 2 datacenter locations, with DCs in each. IT-ADMIN only has 1 datacenter location, so putting a DC at the remote site would be a good idea. If he/she had another datacenter location, it would be less of a concern.

he not she, hhhh
thanks for your suggestion, i know that the best idea is to have an additional DC in the remote location, i will try another machine and promote it in the branch office, i will not give up, because i doubt the previous ADC has something wrong in its system, if it doesn't work i will try RODC

@scottalanmiller said:

@IT-ADMIN said:

@scottalanmiller said:

@IT-ADMIN said:

but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login

Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?

yes they switch machines toooooo ofen, no one stay in his machines and create big problem for me, even problem with outlook, i hope they stay in one place but unfortunately they change their places all the time

Oh, very odd. Yes a DC would be needed then.

off course, because we have kind of call center, staff don't care where they sit, they don't have specific software, where ever they find free computer they login into it

@IT-ADMIN said:

@scottalanmiller said:

@IT-ADMIN said:

but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login

Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?

yes they switch machines toooooo ofen, no one stay in his machines and create big problem for me, even problem with outlook, i hope they stay in one place but unfortunately they change their places all the time

i'm thinking of RODC in the branch hopefully this project will be successful !!!

@scottalanmiller said:

@IT-ADMIN said:

but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login

Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?

yes they switch machines toooooo ofen, no one stay in his machines and create big problem for me, even problem with outlook, i hope they stay in one place but unfortunately they change their places all the time

but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login

@scottalanmiller said:

@IT-ADMIN said:

What about Read Only DC, is it a good idea ??

Doesn't feel like it is needed here. Now that you have the DC at the main site... is it causing a problem?

no problem at all, but i need a backup logon server in the branch office so that if the VPN go down, ---> users in the branch can login from the DC in the branch

What about Read Only DC, is it a good idea ??

@Dashrender said:

What problems are you having now with the remote branch computers and them connecting to the domain?

ok Sir, i will tell you all the steps i have done,

1- promote windows server 2008 R2 to be a domain controller (additional), and i select during the wizard DNS server and global catalog (i did this in the main office)
2- go to Active directory site and services,--> create a new site called Branch, --> create a site link between Main and Branch,--> create new subnet 192.168.5.0, --> in the site link i set the cost and a schedule for replication,--> change ip address of my ADC from 192.168.1.250 to 192.168.5.250, and set the preferred DNS to the ip of the main DC and alternate DNS to his ip ---> i moved to branch office and plug the ADC to the switch ---> change the preferred DNS of branch computers from the PDC ip to ADC,

in this stage i go to one of my branch computer, and login from it, i open cmd then type set in order to know the logon server, it show the name of the main DC, i flushed the dns, still having the main DC as logon server, i disconnect the VPN, the user cannot login,

the problem is that the branch computers cannot recognize the PDC as logon server,

then i go to reverse lookup zone, i didn't find any reverse lookup zone that correspond to my remote network 192.168.5, so i decided to add one for my remote network, in this stage a painful story start, the main DC show a message DNS NOT OPERATING, everything got crazy, so i disconnect the VPN, the DNS was restored, enable VPN the DNS not operating, that time i recognize that the ADC who is responsible for these problem,
finally i decided to remove that shit (ADC) from remote office

this is the whole story, i hope that you enjoy it, lol

i appreciate your kind advise, but unfortunately i think that i have all setting correct but still not able to get an additional DC installed in the branch office, and what is worst is that ADC was creating conflict with the main DC (DNS issues) and i risked the stability the whole domain, for this reason i refrain from having it in the branch,

@alexntg said:

@IT-ADMIN said:

i know that the best practice is to have one additional DC in the branch office, but unfortunately i still not have the skills to get that done, this project was not successful and i risked to damage the main DC because it seem that there was some kind of conflict between the 2 DC, now i'm thinking about having child DC in the branch office, this is my next plan, hoping that will be successful

best regard

Do you mean a child domain? There's very little reason to use a child domain unless there's a legal separation requirement between two business entities or you have so many computers that a single domain wouldn't be practical.

so, i meant child domain, i plan to do that in order to have a backup login server in the branch, i know that additional DC is the best solution for that but this project was not successful. so sad .....

also just recently i have a problem, i cannot manage computers in the branch office (in the console Active Directory users and computers), this problem appear only after i add that shit (additional DC in branch office) , before that i was able to manage them, now i cannot (network path not found)

i know that the best practice is to have one additional DC in the branch office, but unfortunately i still not have the skills to get that done, this project was not successful and i risked to damage the main DC because it seem that there was some kind of conflict between the 2 DC, now i'm thinking about having child DC in the branch office, this is my next plan, hoping that will be successful

best regard

@Dashrender said:

so you only have one DNS server running now?

yes, i content myself with only one DC - DNS server which is the old one in the main office, and users in the branch office login from the main DC, hopefully the remote login will not consume much bandwidth since i have only 512 Kbps speed, i wanted to have a remote DC from my branch computers but unfortunately this project was not successful and may corrupt the all domain because the DNS service is everything in the domain, if corrupted or damaged, it will be a total lost, fortunately i test that at night otherwise i will be in trouble with the management

can you imagine what happen to me yesterday night??
i was trying to solve the problem, i added one reverse lookup zone for the remote network 192.168.5 because there was only one reverse lookup zone for the main network, after doing so the main DC get crazy, a message appears "THE DNS SERVER NOT OPERATING", fortunately i do that at night and no employee was there, everything stack, no logon server available, the network drive is not working....
i had very difficult time, i realize the importance of the DNS, so i delete the reverse lookup zone, then the DNS came to life, i restarted the main DC, the same issue again DNS NOT OPERATING, i doubt the remote DC have some affect on the main DC so i disable the VPN, restarted the main DC, DNS came to life, i enable the VPN, the DNS stack, that time i realize that the remote DC who is responsible of all of this, so i remove this shit from the Domain and from the Site and services console, everything is working now ,lol

really i'm facing your very same problem exactly, before everything was fine (no DNS issues), but as soon as i add new DC into domain in my branch office, i start having those kind of problem as you mentioned, these days i'm having difficult time, the domain is not stable at all, i neither get additional working nor the domain stability i got before,

i hope these problems come to an end

@scottalanmiller said:

Yes. Using non-AD DNS is a more expert option. Just going to make things harder. Stick with integrated AD / DNS.

yes of course i set my ADC to be DNS server, i think that this issue have no solution because i think i have everything set correctly whether it be physical and logial,
i will bring that ADC from the branch office and content myself with only one DC in the main office.