The Site2 machines are only using the Site1 DNS server (192.168.1.44)
as their DNS server when performing the test. I just thought i would
throw out there the fact that the T1 connection is apparently good
because if i do put the address of a public IP server such as 4.2.2.2,
they can reach the internet.
I can ping back and forth between the two sites and ping the server
from Site2 with no problem. I will try what you suggest from Site2 in
a bit.
Re: AD DNS design question ... Just create a secondary of your primary AD DNS server.... I have a site (we'll call it Site1) that is running Active Directory.... I want to add a second site (Site2) to our Active Directory domain. ... (microsoft.public.windows.server.active_directory)
Re: Additional DC for Existing Domain - DNS Question ... I would like to have GC in both site1 and site2.... Is it ok to enable it without affecting Site1 GC? ... I have installed another DC but it did not ask for DNS installation... it would be a good idea to make the DC also a DNS server and to ... (microsoft.public.win2000.active_directory)
Re: DNS across a WAN ... The Site2 machines are only using the Site1 DNS server... I can ping back and forth between the two sites and ping the server ... If NSLookup works, I would SERIOUSLY go recheck the ... (microsoft.public.windows.server.dns)
Re: Additional DC for Existing Domain - DNS Question ... I need GC because I will have 2nd Exchange 2003 in site2.... Is it ok to enable it without affecting Site1 GC? ... it would be a good idea to make the DC also a DNS server and to ... >> it a Global Catalog and install DHCP if you use DHCP too. ... (microsoft.public.win2000.active_directory)
Re: SBS 2003 and Replication Errors with Remote DC ... either fixup the alpha site dns or point it to use the SBS dns server... and allow replication to complete (including the DNS forest and domain ...Domain Controller Diagnosis...Performing upstream analysis. ... (microsoft.public.windows.server.sbs)
