Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Does anyone have any idea why ipconfig on Windows XP might take a 10-20 seconds to finish? It’s causing a timeout issue for me in an application.

share|improve this question
3  
is this just ipconfig, or are you specifying flags (/release & /renew can be slow for reasons mentioned below) –  voretaq7 Feb 8 '10 at 19:17
    
In addition to wanting to see some more details I'm particularly curious as to why ipconfig (as opposed to the separate network connectivity issue) affects an application. –  John Gardeniers Feb 8 '10 at 21:32
add comment

3 Answers

Most of the time when I've had ipconfig be slow, it's been because there's an issue contacting the DHCP server - whether it was because the server was down, or because there was an issue with the client box was irrelevant (and also unreported by ipconfig).

share|improve this answer
add comment

Reverse DNS? Are your DNS servers working correctly?

Are you using any other options such as /all, or /release, /renew like Harper suggested?

share|improve this answer
    
How is DNS relevant? –  John Gardeniers Feb 8 '10 at 21:31
    
Yes, I'm using /all –  JonF Feb 8 '10 at 23:49
    
I thought ipconfig did a reverse DNS lookup on your IP address to get your hostname. Could be wrong though, it's been a few months since I had anything to do with Windows networking. –  Andy Shellam Feb 9 '10 at 19:19
add comment

When I read your question it sounds as if you are calling ipconfig from within an application? If so, how do you call ipconfig?

Is it as slow if you use ipconfig from a bare cmd.exe shell?

share|improve this answer
add comment

Your Answer

 
discard

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