Dhcp Socket Error
Contents |
Socket error If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want 10054 socket error to visit from the selection below. Results 1 to 3 of 3 Thread: DHCP Socket error wsaeconnreset 10054 Thread Tools Show Printable Version Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode September 24th, 2002,15:29 PM #1 griz View Profile socket error 10038 View Forum Posts Junior Member Join Date Sep 2002 Location Ohio Posts 1 DHCP Socket error I work for a Broadband ISP and have been coming across an error that nobody knows how to fix. It seems to happen mainly
Socket Error 10053
in Windows XP. The machine can no longer get an IP Address from the cable modem, and when the ipconfig /renew command is given, you get the following error. "An operation was attempted on something that is not a socket." (Error 10038) The only reference in the MS Knowledge Base is to McAfee Personal Firewall corrupting some network files. In our case only a few of the machines ever had this firewall installed. I have searched the web and tried socket error 10054 connection reset by peer all solutions suggested, reinstall TCP/IP, netsh, etc. But haven't had any luck. Any suggestions? Reply With Quote September 24th, 2002,15:43 PM #2 Big Booger View Profile View Forum Posts Visit Homepage Super Moderator Super Moderator Join Date Apr 2002 Location JAPAN Posts 10,941 http://support.microsoft.com/default...;EN-US;Q319952 Same error, different way to get it, the causes maybe the same.. might be that the socket you are accessing is already being accessed.. The socket is bound and listening on the loopback address 127.0.0.1. Just an idea. ANother idea, have you installed SP1? If so did it happen after or before? Also, have you updated all your drivers? just some basic issues to check. BB and lastly I found this: "Error writing to network. Cause:Socket operation on non socket (10038)" This is a Windows error message reported by the Winsock stack. It usually means the Winsock is not loaded correctly - ensure network services are in fact available (ask others if they are having problems) then try other Winsock compliant applications (eg WinQvt) to see if the same problem exists. Last edited by Big Booger; September 24th, 2002 at 15:48 PM. Map yourself with TZ Frappr | Booger's Blog Reply With Quote September 24th, 2002,16:00 PM #3 egghead View Profile View Forum Posts Precision Processor Super Moderator Join Date May 2002 Location In Your Monitor Posts 3,546 hello: these are info pages to youe error code it might give you some idea's http://support.microsoft.com/default...;EN-US;Q319952 http://www.ba
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://www.techzonez.com/forums/showthread.php/2374-DHCP-Socket-error Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/200462 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
» Socket Error 10054 Socket Error 10054 Last Year GlobalSCAPE Support 1 CuteFTP for Windows THE INFORMATION IN THIS ARTICLE APPLIES TO: CuteFTP® Home (All Versions) CuteFTP Pro® (All Versions) SYMPTOMS During an FTP session, the following error is encountered: ERROR:> Can't read from https://kb.globalscape.com/KnowledgebaseArticle10235.aspx control socket. Socket error = #10054. CAUSE & RESOLUTION A socket error 10054 may http://www.pcreview.co.uk/threads/dhcp-renew-not-a-socket-error.220106/ be the result of the remote server or some other piece of network equipment forcibly closing or resetting the connection. In some other situations a change to the default CuteFTP connection settings may be needed for connections to this particular remote FTP server. The most common cause for a socket error 10054 is the use socket error of an invalid FTP host address. Double-check to make sure that you are using the correct FTP host address. Before making any changes to the default configuration for CuteFTP, wait and retry your connection later. A socket error 10054 can also be caused by any of the following reasons: The remote server was stopped or restarted. The remote network interface is disabled for some reason. There are too many users dhcp socket error logged on to the server. Your account on the remote server is restricted for some reason. If this error started happening after a recent upgrade to your Web browser, (for example, after upgrading to Internet Explorer 7.0) please browse to KB Article ID 10294 for instructions. If you are satisfied that the remote server or user account is not at fault, and you encountered this error either when first establishing the connection or when starting a file transfer, then it may be necessary to change the data connection type. CuteFTP uses passive (PASV) mode by default but for this remote server you may need to use active (PORT) mode instead. To make the switch from PASV mode to PORT mode in CuteFTP Home, open the Site Manager and click once on the the name of the problem site on the left side of the window. On the Type tab change the Data Connection Type to Use Port. If you are using CuteFTP Professional, in the Site Manager, right-click on the name of the problem site and click Site Properties. On the Type tab, change the Data Connection Type to Use Port. Note: If changing the data connection type has no effect then you should return th
AOL installed on it - don't know if it's a factor. >-----Original Message----- >I have seen similar posts on this newsgroup after doing a >search but have yet to see any new suggestions. > >Scenario: For the general health of the computer I ran >windows update on a laptop running XP Pro, ran chkdsk, ran >defrag, ran disk cleanup, and ran Ad-Aware to clean-up >adware/spyware. > >The next day the user of that laptop could not connect to >shares on the network. After finding out it was using an >automatic private IP address, I tried "ipconfig /renew". >It returned message "An operation was attempted on >something that is not a socket." > >I did everything that was suggested by postings here or by >KB articles: > >1. Run winmsd, look at components/network/protocol and >nothing was there. >2. deleted the winsock and winsock2 reg keys >3. Rebooted >4. ran "netsh int ip reset resetlog.txt to reset TCP/IP >since you can't uninstall it on XP Pro >5. Rebooted >6. Tried "ipconfig /renew" again - failed. >7. After finding an article saying that McAfee Personal >Firewall might have been uninstalled improperly, I >reinstalled it and then uninstalled it using the McAfee >uninstall tool. (I don't know when this was ever >installed, but it came with the laptop so I thought >someone might have installed it at one point). >8. Rebooted. >9. Tried to renew again - failed. > >In my heart of hearts I know that the problem was caused >by some combination of the Windows Updates I downloaded >and installed. I updated every machine in our network >because of the recent worm threats and this is the 3rd >machine that has encountered a problem as a result of that >process. > >But that doesn't matter. I just want to get it fixed >without reinstalling Windows. > >Any help would be appreciated...Thanks! >. > marty, Aug 27, 2003 #1 Advertisements Ken Wickes [MSFT] Guest You don't mention doing steps #3 - #7, have you? 1. Backup and delete the following registry keys HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2 2. Reboot 3. Go to the network connections folder, right click the icon for your network connection, and select properties. 4. Click install, choose "protocol", and click "add..." 5. Click "Have Disk...", enter "\windows\inf", click OK 6. Select "Internet Protocol (TCP/IP), click OK 7. When the process in complete, reboot -- Ken Wickes [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "marty" <> wrote in message news:071601c36c39$802db280$... > I forgot to add that this machine has AOL ins