IPCONFIG no longer works

[debonairOne]

Okay... here's the error, then I'll provide some history...

An internal error occured: The system cannot find the file specified. Please contact Microsoft Product Support Service for further help. Additional information: Unable to query host name.

This error pops up when trying to launch ipconfig. I have had problems all day with this issue, it started with limited connectivity probs, advanced to this when I tried using various fixes and patches for this problem. I have tried system restore to no avail. What can I do now...?

WinXP Pro w/ sp2 on Dell Latitude D600

debonairOne

"I look in the mirror and what do I see..."

 

[Jump1ng]

What happens if you check your network setting under network properties? Can you do this ok?

Also you might want to check in the device manager to see if your NIC has loaded properly or if there is an error there.

Now that doesn't really explain why it can't find your ipconfig command. Do you have ipconfig.exe in your system32 folder?

When you say that you first experienced some conectivity problems that could be a sign of faulty drivers.

If you don't have any errors in device manager try installing new drivers and not sure if the Dell diagnostic has network testing but you might want to try using that see what it says. It could be that your NIC is faulty.


---
Make the best use of what is in your power, and take the rest as it happens.

 

[bcastner]

Could you specify the changes you made for the "Limited or no connectivity" issue?

Did you happen to run AdAware and "fix" this?:

http://www.broadbandreports.com/forum/remark,12882449~mode=flat

 

[debonairOne]

Jump1ng -

am able to check network properties without a problem. As for device manager, everything in there is peachy, not a problem listed anywhere... the drivers were ok minutes before my self afflicted problem began... I also removed the net adapters to reinstall the drivers and they installed ok, but I am still having the same problem... ipconfig is in the system32 folder and does not run as expected. When attempting to run it, I receive the error in the previous post.

bcastner -

the changes made to repair the "Limited or no connectivity" problem were the standard ones using the winxpfix and the manual removal methods to repair the corrupted winsock. After doing this, the problem was exacerbated, now the dhcp service hangs in a starting state. And yes, I did run adaware and probably did allow it to remove that entry... I will merge that back into my registry tonight and see if that will resolve my issue...

Thanks for the information - both of you, will report back what happens sometime late tonight... EST of course...

debonairOne

"I look in the mirror and what do I see..."

 

[linney]

With SP2 you have the built in Winsock Repair command which has superseded the older WinsockFix.exe.

Netsh Winsock Reset

WinsockFix should not be used on SP2: FAQ779-4625

"Any type of networking problem in XP SP2 will give you this “Limited or No Connectivity” message, so you may have any one of these causes of the problem"

Windows XP SP2 Networking Problems Help

http://users.tpg.com.au/adsl5muj/index.htm

Limited Connectivity
thread779-949524

ICS Gateway does not provide configuration to home computers
thread779-955113

 

[debonairOne]

Thanks to all for their input, but I have tried all of the above and still cannot see daylight... I'm not using ICS,but checked it out anyway, still not having any luck on this end... IF I assign a static, I can browse my network, but don't have any DNS... I have an issue with my DHCP service stuck in "starting" state.. cannot find a way to resolve that either... boy did I hose this but good... Also checked ad-aware for the registry key to see if it removed it, but it hadn't... Any more ideas...???

Thanks...

debonairOne

"I look in the mirror and what do I see..."

 

[LloydSev]

the DNS server you would specify would be that of your gateway/router, same for your default gateway. Using that should get you internet access with the static IP.

Computer/Network Technician
CCNA

 

[debonairOne]

LloydSev,

I tried that earlier, but tried it again... No luck... I have since run the xp repair, performed an inplace installation, booted in safe mode and replaced the dhcp and tcpip files and still no luck... I really want to find a solution for this even though it would be easier to give up and format... I have given myself one more week to struggle with this, before I just bite the bullet... I will be on the road and will need my internet access...

As a side note, my problem is no longer with a corrupt winsock... Now my primary issue is this "dhcp client hung on starting" issue. That is keeping me from the net... all references that I have found referred back to the winsock issue, but that passes the test...

debonairOne

"I look in the mirror and what do I see..."

 

[linney]

just a few more straws to clutch.

http://www.mcse.ms/archive62-2003-11-48038.html

Programs that connect to IP addresses that are in the loopback address range may not work as you expect in Windows XP Service Pack 2

http://support.microsoft.com/default.aspx?scid=kb;[LN];884020#appliesto

IP address stuck on 0.0.0.0, no internet or network access
thread779-850595

What information is available in the Event Viewer?

 

[debonairOne]

SUCCESS!!!!!!! I thank you all for your input, I finally figured out what the problem REALLY was.

After all of the above troubleshooting and reinstalling service packs and hotfixes, the fix was to actually realize what a pc needs for DNS to work properly. a NAME... it appears that sp2 removed the computer name. Don't ask me what led me to look at that, I just had an epiphany at 4am and decided, what the hell... When I checked on the network identification properties, the computer name was blank... that explains a lot... although not why sp2 would clear this field. It may have been a result of removing some of the registry keys for DNS during the winsock fix... There are several fixes out there and one of them removes a registry key for DHCP, that may be when this change happened... Anyway, for those who can not get the winsock fix to work, check your computername...

I am now downloading 189 messages and actually happy to see them coming across... There is a new update to windows messenger, etc... In short, I am communicating again as expected...

debonairOne

"I look in the mirror and what do I see..."

 

[rmwilliamsjr]

to debonairOne
thank you very much. i had exactly the same trouble.
probably spent the same amount of time fixing it.
you are right, a self-caused clearing of the name field hangs up dhcp.

thanks.

posting here to catch key words.

fix for windows xp dhcp hanging ipconfig doesn't work error is file not found. fix is check to see if name field is cleared in computer description.

symptom is dhcp daemon is starting....not started.

and again...thanks.
such a simple fix but i would not have found it on my own.

 

[bcastner]

Thanks for the note.

You just should not use the "Winsock" downloadable repair utilities under SP2, noted in faq779-4625

Natively under SP2 it is much better to do a Start, Run, cmd

netsh winsock reset catalog

And when prompted, restart the machine. This is all you need under SP2 to do a Winsock repair.

 

[debonairOne]

rmwilliamsjr,
You are welcome... I have been fortunate enough to obtain many an answer here in Tek-Tips and am pleased when I can contribute an answer in return... Glad it worked for you...

bcastner,
You are one of the invaluable ones in these forums - however, I found that the netsh winsock reset catalog command did not work for me, and then I tried other "stuff".. Anyway, thanks for always being around...

debonairOne

I look in the mirror and what do I see...