Internal Error Occurred The Request Is Not Supported
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 19 Oct 2016 00:58:03 GMT by s_wx1062 (squid/3.5.20)
getting IP address. The laptop was not able to get IP address and I got the following error when I ran ipconfig. Windows IP Configuration An internal error occurred: The request is not supported. Please contact Microsoft Product Support Services for further help. Additional information: Unable to query host name. Checking the system event log revealed the cause of the problem. The DHCP Client service failed to start because of TCP/IP Protocol Driver service failed to start. The DHCP Client service was indeed stopped as shown in the Services console. The next entry showed that the TCP/IP Protocol Driver service failed to start because the IPSEC driver http://answers.microsoft.com/en-us/windows/forum/windows_xp-networking/windows-ip-configuration-an-internal-error/0cd70fcb-0640-4980-8b2e-394fa9e8f31f service failed to start. Finally, the next entry gave the reason why IPSEC driver service failed to start. The system cannot find the file specified. To view the status of the TCP/IP Protocol Driver service and IPSEC driver service, go to Device Manager, click on View menu and enable Show hidden devices. On the right pane, expand Non-Plug and Play Drivers. Looks for TCP/IP Protocol Driver and IPSEC driver. As shown http://deinfotech.blogspot.com/2012/02/ipconfigan-internal-error-occurred.html in the above pictures, TCP/IP Protocol Driver and IPSEC driver are having some issues. The properties page of TCP/IP Protocol Driver and IPSEC driver showed that both services were stopped. Furthermore, the Driver Details button on the IPSEC driver properties page was greyed out. This was because the IPSec.sys file was missing from the C:\Windows\system32\drivers folder. I copied the missing IPSec.sys file from another machine, rebooted the laptop and the problem was solved. Pin It Posted by Alex Siow at 5:08 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Network, Windows XP 2 comments: Practice Safe Sectors! said... Thanks for posting this. Without people like you fishing out the real problem, people like me would be left with nothing to do but reload windows 12:48 AM kaos142 said... So helpful, and so much appreciated. I rarely come across something I can't fix but this one had me really stumped.Thank you! 10:11 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Follow me Subscribe in a reader Enter your email address:Delivered by FeedBurner Followers There was an error in this gadget My Blog List Dora the Techplorer 6 months ago The Lim Kiat Comicals 3 years ago ASP.Net Rocks! 4 years ago Flema
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://serverfault.com/questions/135404/request-not-supported-in-ipconfig-winxp-sp3 Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system http://www.overnightpcrepair.com/case-studies/ipconfig-internal-error-occurred-request-supported/ and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top internal error “Request not supported” in IPCONFIG (WinXP SP3) up vote 1 down vote favorite In a customer PC (Windows XP SP3), suddenly the network went down: the network adapter appears with an error mark. I replaced the network card, but the new one does the same thing. When I enter IPCONFIG, XP shows this error (in standard and safe mode): Internal error occurred Request not supported Unable to query host name If internal error occurred I start the system with a boot cd the PC runs fine, so the problem seems to be in the XP installation. I tried: uninstalling and reinstalling the network card in the Device Manager disabling and reenabling the card netsh int ip reset netsh winsock reset catalog and a couple of "reset" programs (WinsockxpFix.exe, etc) with no luck. Is there any way to fix it without reinstalling XP? TIA, Pablo networking windows-xp share|improve this question asked Apr 24 '10 at 2:23 user41235 1287 Were any windows updates (automatically) installed recently that could have broken it? (history available @ update.microsoft.com) –iainlbc Apr 24 '10 at 2:36 @iainlbc: no, Windows Update is disabled –user41235 Apr 24 '10 at 3:06 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote I would have bet the Winsockfix would have done it. It sounds like the TCP stack is screwed up. Have you tried this KB article? share|improve this answer answered Apr 24 '10 at 3:29 uSlackr 5,6001027 add a comment| up vote 0 down vote I like uslackrs response since it has the fixitnow thing! share|improve this answer answered Apr 24 '10 at 3:55 tony roth 3,193811 add a comment| Your Answer draft saved draft discar
Hours are 11:30am-7:00pm Monday-Friday, 11:00am-5:00pm Saturday, Sunday Closed Computer Repair- Overnight PC & MAC Repair Los Angeles Computer Repair Blog Case Studies Lucky 100th Mac Repair Tips Pc Repair Tips Technology News Testimonials More Computer Repair Information From Us Our Computer Tips What We've Done for Others computer parts Our Testimonials Technology news Sitemap Recent pc repair posts How to Export Email Addresses From CC Field to Excel November 11, 2015 How to Setup VPN Server on Netgear R7000 NightHawk Router With Openvpn for Windows September 22, 2015 Macbook Air Adware Attack Browser Hijack August 4, 2015 Lines on Macbook Pro Screen July 30, 2015 Why You Should Not Buy Samsung Np680z5e Laptop Case May 3, 2015 Imac 27 Inch A1312 SSD Installation May 1, 2015 Mac Talk Woodland Hills - Closed- Out of Business April 15, 2015 Lenovo Ideapad Yoga 13 Dc Jack Replacement January 22, 2015 Number One Enemy of Imacs (And Macbook Pros) December 24, 2014 Imac Video Chip Failure - Lines and Pixelation on the Screen December 23, 2014 Share this with your Friends! Search <