You almost certainly have a DNS problem. To correct:
1) Make sure each and every client points ONLY to the DCs for name
resolution. Specifically, do NOT put your external ISP DNS servers into the
clients TCP/IP configuration.
2) Make sure each DC (running DNS) is configured to forward unknown
requests to the DNS servers provided by your ISP (or, can be your router's
IP). Also, make sure your DCs (and DNS servers) DNS client in TCP/IP
configuration is ALSO configured to point to ONLY to the DCs themselves.
Specifically, do not put your ISP provided external DNS servers into the
TCP/IP configuration of your DCs.
-Frank
"flabs" <(E-Mail Removed)> wrote in message
news:5DD9CE90-3D6B-44D5-B7CA-(E-Mail Removed)...
>I do not know the reason, have someone any idea, how I can locate the
>cause?
>
> we have an windows 2000 native mode AD with a 2k3 an a 2k DC (migration to
> 2003 is in progress) additional
> we have 8 windows 2k/2k3 based Servers, 25 XP Client, 10 of are often
> external Without connection to local Network
>
> Our Problem is, the useres are browse to Network Share via Drive Mapping
> or
> UNC Path. Sometimes they received "Not Response" from windows Explorer,
> if
> they click on a folder or file to open it. This Problem is not always
> only
> sometimes. At one time they can browse normal in LAN, but suddenly in next
> click they received "Not Response" and they can close the windows explorer
> only by task manager
>
> I have no idea to start my lookup to find out the errors
>
> Many Thanks
|