Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have several scripts in UNC paths (from Windows batch files to PHP scripts). No matter how I run them (double click on explorer, my editor's run command menu or Windows command prompt) they take really long to start running (like 14 seconds). Once they get started they run normally. This doesn't happen if I run them from mapped drives.

I'm using Windows XP Professional SP3 inside an Active Directory domain and files are hosted in a Windows Server box (not sure about the version, it's an HP dedicated file server with bundled OS).

Why does it happen? Is there a way to speed up things while using UNC paths?

share|improve this question

Could it be something related to name resolution? Did you tried to put IP address instead of the hostname?

share|improve this answer
Good point! UNC paths with IP addresses do not experience such slowdown. Any clue about why Windows does not cache name resolution? – Álvaro González Apr 28 '10 at 14:04
You have some issues in the name resolution. Check that every XP use the AD Domain controller as DNS server. – lrosa May 2 '10 at 7:25
Networks settings come from DHCP, but the DNS server's IP address matches the domain controller. Perhaps it's the DNS server itself the one that's misconfigured... – Álvaro González Jun 30 '10 at 12:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.