I have a 2000 professonal server/running exchange 2000/with router/
customer reported internet down/ on suggestion I cleared dns cache
then using ipconfig flush and register it fixed the problem/  I now
have to do this almost every two days/ this has been running fine for
6 months/ help !!!!!!!!!

---

Request for Question Clarification by sublime1-ga on 25 Jul 2003 15:52 PDT

doodah2003...

Please try the following: Go to Administrative Tools -> Services
and find 'DNS Client'. Right-click it and select 'properties'.
Then set the 'Startup type' to 'disabled'. In my experience,
this service is less than useless, and disabling it should 
eliminate the need to flush the dns cache, since it won't be
used. This service also serves to slow the computer considerably,
cranking CPU usage to 100% for long periods. Disabling it should
increase your preformance as well.

If this resolves your problem, let me know and I'll post this
as a formal answer.

sublime1-ga

Interesting suggestion (disable "DNS client").

The key is to find the problem and the question is unclear
about the OS/DNS server combo.

Windows 2000 "Professional" is the workstation and will not
run the MS DNS -- Server is a different product but the 
questioner indicated "Win2000 Professinal Server" with 
DNS.  If it's really Professional, the DNS server is 
either third party (e.g., BIND) or the simple DNS
relay in ICS.


Might be running NAT, ICS, or just plain routing.
Server (or Pro) might have a Hard address on the 
external (Internet) side or DHCP there -- this is 
important to the answer as with DHCP you may be
getting a bad DNS IP from the ISP DHCP server or
you may have to disable that DNS IP since this 
machine is supposed to be running DNS.

Presuming Server with NAT on the router and a real DNS
server there are all sorts of issues.  

Presuming ICS with EITHER Server or Pro (workstation)
then the troubleshooting is different.  Check to make
sure the ICS machine is NOT also trying to run a 
real DNS server (this is true for Pro or Server IF
it's ICS.)

If it's server AND ICS, switch to NAT (in RRAS).

If you are using NAT on server then there's a bunch
more to troubleshoot depening on whether you are using
"real" DNS server or the simple relay in NAT (similar
to ICS but can be turned off.)  If you run both they
may interfer with each other.

Needed:  Precise OS, type of DNS.  Is NAT or ICS running?
Or is it a simple router.

Also:  IPCONFIG /all output to a file and posted.

if nothing works, you can still add the ipconfig flush to the sheduled tasks.