The network is too Slow

  • Thread starter Thread starter Charisma
  • Start date Start date
C

Charisma

Hi,
I have a local DNS and we connected to internet by setting
proxy Ip address,I think we don't need to set forwarder.
But our network is too slow during logon and searching
network and searching for print servers and browsing
network.
What's the problem?
We have two DC that both of them are GC and the preferred
DNS for both of them is it's own IP Address and altenate
DNS is other DC IP address.
THank you.
 
What do you mean by setting proxy address?

If you are pointing your DNS at a proxy server, that is for external names;
not internal names.

Basically, you need to point at the Win2000 DNS server.

You then have several choices as to how you resolve external
names -forwarders, root hints, both, or the proxy to name but a few. Some
configurations add the root zone '.' to the internal DNS to stop the
internal resolving anything other than their zones and configure the proxy
to resolve external zones.
 
Hi,
For every client in IE setting in LAN setting we set an ip
address for proxy server(our isp gave it to us),for
connecting to internet through a default gateway ip
address because we have a lease line and a dsl modem with
an ip address.Then our external dns is in other places but
we have an internal dns.
Now what's my problem?
Thank you.
 
OK, you have to ensure that *all* internal clients point to the internal DNS
server; the DNS server itself (which I assume is the AD domain controller)
needs to point to itself, and all of the clients, whether server or
workstation. DNS needs to be configured to support Dynamic Updates.

IE settings are fine. When you enter an address into IE with a period '.'
in it, it will look to the proxy for the name resolution. All other name
resolution should, and will, go through the internal DNS server.

To be on the safe side, I would restart netlogon on the DC when it is
pointing to itself so that it reregisters any missing SRV records. To do
this, type the following commands into a command prompt:

C:\>ipconfig /flushdns
C:\>net stop netlogon
C:\>net start netlogon
C:\>ipconfig /registerdns

Try this and wait several minutes. You'll also need to ensure that the
clients are configured to register in DNS. This is achieved through
selecting the option "Register this connections suffix in DNS" in the
advanced DNS properties of your network cards TCP/IP settings.

--

Paul Williams
_________________________________________
http://www.msresource.net - Under construction, but coming soon...


Join us in our new forums!
http://forums.msresource.net
_________________________________________
 
Back
Top