721 Error - Remote Computer Did Not Respond
Contents |
One games Xbox 360 games PC error 721 the remote computer did not respond blackberry games Windows games Windows phone games Entertainment All vpn error 721 remote computer did not respond Entertainment Movies & TV Music Business & Education Business Students & error 721 vpn connection educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
Error 800 Unable To Establish Vpn Connection
Internet 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 Band Microsoft verizon error 721 the remote computer did not respond Lumia All 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
I have FINALLY resolved an ongoing issue with our VPN connections that we have been experiencing for over a year now. I will share these findings with this forum in case others can benefit from our situation. First let me explain the problem. error 678 the remote computer did not respond The Problem: It can take up 6 retries for any remote user to successfully created a
Error 721 Vpn
remote PPTP connection to our servers. Whenever we try to connect it display the following message: Verifying username and password... And it sit there displaying
Error 721 Vpn Windows Xp
this message for about 30-40 seconds, then it says: "error: 721 The remote computer did not respond." Network Setup: We have two netopia routers on our network. They both have their own separate WAN connection (we use a lot of bandwidth, https://support.microsoft.com/en-us/kb/888201 hence the need for two WAN connections). One RAS server is configured to use one router as it's gateway, and the other RAS server uses the second router as it's gateway. When PPTP connections are made, the connection comes in and back out the same router (this I made sure). We use a multi-NAT for routing service request to internal servers. FTP, WWW, RDP, PCAnywhere, SSL, PPTP, MAIL, etc...all these services are routed to internal servers/workstations. We have approximately 32 public IP addresses, http://www.pcreview.co.uk/threads/error-721-finally-resolved.1574450/ hence why we use Multi-NAT for routing public services to internal servers. Everything works perfectly, EXCEPT PPTP (VPN) connections. We have struggled with this for a year now. For whatever reason, it struggles to make a successful connection to our RAS servers. Like I said, it can take up to 6 retries to successfully connect to our RAS servers (up to 30 retries if the remote user is behind a Linksys router). The Fix: Today, I decided to try something different. I decided to use the router's public IP address for PPTP requests, instead of one of the other public IP addresses our ISP assigned us, and simply forward PPTP (TCP 1723 & IP 47) requests to the internal servers. Therefore, the only difference is that I am using a pingable IP address which happens to belong to the router instead of using one of the public IP addresses I have NATed. For whatever reason, this solved our problem with connecting to the RAS server. We no longer have to retry up to 6 times to successfully connect. Conclusion: I have NO clue as to why I have to use the router's public IP address rather than any of the other 31 public IP addresses our ISP assigned to us. This was ONLY an issue with the PPTP service. All the other services work perfectly with the router's Multi-NAT table. In the end I don't know whether it's a router issue (ie, Netopia has problems
Did Not Respond? Don't Worry - I'm here to help you fix it! Causes of http://www.computerfixitshop.com/windows-error-721-the-remote-computer-did-not-respond.php the error: Windows Windows Error 721 The Remote Computer Did Not Respond are caused by misconfigured system files. So, from my experience, If you received a Windows Error 721 The Remote Computer Did Not Respond message then there is a 97.5% chance that your computer has registry problems. The Windows Windows Error 721 The Remote error 721 Computer Did Not Respond are easy to repair. By downloading and running the registry repair tool RegCure Pro, you can quickly and effectively fix this problem and prevent others from occuring. Simply click the links below for your free download. To Fix the problem you need to follow the 3 steps : STEP 1: Download & remote computer did Install RegCure Pro for Free. NOTE: If the download link doesn't work you may need to Download it Directly from a Mirror Here. STEP 2: Click "Quick Scan" Button to Scan Your Computer. STEP 3: Click the "Repair All" Button to Repair Your PC! That's All! Scott Chan Technical Description of System Error(for Experts only): Microsoft Windows [Version 5.2.4630] (C) Copyright 1985-2014 Microsoft Corp. C:\Documents and Settings\Administrator>RegCure Pro.exe Windows Windows Error 721 The Remote Computer Did Not Respond may caused by some of the following errors Windows Explorer ErrorsJavascript ErrorsHardware MalfunctionError Symptom include:Can not printing fileBlue ScreenIO errorShutdown problemsHttp error Tags: Windows Windows Error 721 The Remote Computer Did Not Respond 4 Response to “RegCure Pro ” DominicaSays: at 9:22 PM Thank you so much! After spending countless hours on this stupid windows error 721 the remote computer did not respond problem I almost gave up. RegCure worked like a charm on the first try. It took a bit longer than 10 minutes, c