slow network access

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a office where I created a windows 2003 domain controller. this domain
is a domain controller inside an existing domain. these domains are all 2003
standard editions DHCP/DNS/WINS. I have the servers replicating through VPN.
All went well except that when the folks inside the office attemot to access
a network share or browse the network neighborhood it is very slow. Also,
when the users attempt to open something thfough Micosoft Word. If I browse
the other network from the site that houses the first domain controler, the
access speed is normal. I first suspected DNS as an issue, so I deleted and
recreated. it appeared that this solved the problem, but I was mistaken. I
did not add in additional settings to the DNS I just let it replicate from
the existing domain.
What I am looking for is a solution for the slow connection. Do I need TO
ADD A dns entry for the new domain controller? did I forget a setting else
where???
 
You do not need to create an A record for domain controller. However dns
configuration is critical in that the domain controller must point to itself
only [when there is only one] as it's preferred dns server in tcp/ip
properties and as shown via Ipconfig /all. Then all W2K/XP Pro/W2003 domain
computers must point only to the domain controller as their preferred dns
server and never include a ISP dns server in the list. The link below
explains more on AD dns. Also make sure that the domain controller is also a
wins client so that it will register is netbios names in the wins database
including domain controller and domain master browser.

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

In addition there may be problems with smb signing which you can disable the
(always) setting for on the domain controller for digitally sign
communications. That can be configured in Domain Controller Security
Policy/security settings/local policies/security options. See the link below
for more details. --- Steve


http://www.microsoft.com/technet/Security/topics/hardsys/tcg/tcgch05.mspx#E6AA
 
I was reading the articles and just want to recap> the Domain Controller at
the site in question must have the DNS point to the DC at the other site???
Then all workstations must point to the closest DNS server??
Is this correct


Steven L Umbach said:
You do not need to create an A record for domain controller. However dns
configuration is critical in that the domain controller must point to itself
only [when there is only one] as it's preferred dns server in tcp/ip
properties and as shown via Ipconfig /all. Then all W2K/XP Pro/W2003 domain
computers must point only to the domain controller as their preferred dns
server and never include a ISP dns server in the list. The link below
explains more on AD dns. Also make sure that the domain controller is also a
wins client so that it will register is netbios names in the wins database
including domain controller and domain master browser.

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

In addition there may be problems with smb signing which you can disable the
(always) setting for on the domain controller for digitally sign
communications. That can be configured in Domain Controller Security
Policy/security settings/local policies/security options. See the link below
for more details. --- Steve


http://www.microsoft.com/technet/Security/topics/hardsys/tcg/tcgch05.mspx#E6AA


Dave said:
I have a office where I created a windows 2003 domain controller. this
domain
is a domain controller inside an existing domain. these domains are all
2003
standard editions DHCP/DNS/WINS. I have the servers replicating through
VPN.
All went well except that when the folks inside the office attemot to
access
a network share or browse the network neighborhood it is very slow. Also,
when the users attempt to open something thfough Micosoft Word. If I
browse
the other network from the site that houses the first domain controler,
the
access speed is normal. I first suspected DNS as an issue, so I deleted
and
recreated. it appeared that this solved the problem, but I was mistaken.
I
did not add in additional settings to the DNS I just let it replicate from
the existing domain.
What I am looking for is a solution for the slow connection. Do I need TO
ADD A dns entry for the new domain controller? did I forget a setting else
where???
Click to expand...
Click to expand...
 
Back
Top