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

This is in Windows XP

link|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
feedback

2 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).

link|improve this answer
feedback

Reverse DNS? Are your DNS servers working correctly?

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

link|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
feedback

Your Answer

 
or
required, but never shown