Windows VPN: Error 720 - A connection to the remote computer could not be established

Dear all
I have a windows7 Laptop 64bit Dell 1340.
I was working with a UMTS card, was connected with a VPN to a windows 2003 server over PPTP and experienced a bluescreen. After this, I have the following errors when connecting to the VPN:
"Registering your computer on the network... Error 720: A connection to the remote computer could not be established. You might need to change the network settings for this connection"
and in the event view I receive the following:
EventID: 1, Source RasSstp
CoId={A3478DFD-FFA4-4E8F-9DA3-CE829BDA777B}:The initial Secure Socket Tunneling Protocol request could not be successfully sent to the server. This can be due to network connectivity issues or certificate (trust) issues. The detailed error message is provided below. Correct the problem and try again.
I tried to use the Rarepair.exe tool but it looks to work only on windows xp. I deleted the IP and TCP settings without any luck.
I run a registry cleaner as well with out any luck.
Your help will be greatly appreciated!
Marc

Hi,
Since it worked previously, a quick solution is to run System Restore and get back to the previous status when the issue didn’t occur.
If system restore doesn’t help, please also try the following:
1.    Check if you can establish the VPN via other connections except the connection through the UMTS card.
2.    Reset the PPTP and L2TP WAN miniport with running the following commands one by one in an elevated command prompt:
Netcfg -u MS_L2TP
Netcfg -u MS_PPTP
Netcfg -l %windir%\inf\netrast.inf -c p -i MS_PPTP
Netcfg -l %windir%\inf\netrast.inf -c p -i MS_L2TP
Then reboot the computer and see how it works.
Meanwhile, I would like to share the following with you for your reference:
Troubleshooting common VPN related errors
Hope this helps. Thanks.
Nicholas Li - MSFT

Similar Messages

  • Error 720 a connection to the remote computer could not be established win 8

    hello, i have this error on my windose 8, error 720 a connection to the remote computer could not be established ,for VPN connection,  how can i fix it ? 

    Hi，
    For this issue,I would like to know your VPN protocol.
    Did you use Windows in-built VPN client?
    I think the issue is related to your security software or Firewall.
    Let’s temporarily disable other security software and Windows firewall to check if that helps.
    If it doesn't work, please uninstall the third-party security software or firewall to test it.
    Also, please check your event view to see if there are some related error in it.
    Regards,
    Kelvin hsu
    TechNet Community Support

  • BB Torch - bluetooth tethering for laptop internet use: "Error 720: A connection to the remote computer could not be establishe​d

    Trying to set up Blackberry Torch for laptop tethering...bluetooth. I have connection/drivers/etc. but keep getting error message: "Error 720: A connection to the remote computer could not be established. You might need to change the network settings for this connection." Where and what do I chancge setting to so this will work?
     I have synched my phone and laptop wirelessly across other internet connection....just cant get this above to work. Anybody know how to fix this? Thanks!

    Hi,
    Since it worked previously, a quick solution is to run System Restore and get back to the previous status when the issue didn’t occur.
    If system restore doesn’t help, please also try the following:
    1.    Check if you can establish the VPN via other connections except the connection through the UMTS card.
    2.    Reset the PPTP and L2TP WAN miniport with running the following commands one by one in an elevated command prompt:
    Netcfg -u MS_L2TP
    Netcfg -u MS_PPTP
    Netcfg -l %windir%\inf\netrast.inf -c p -i MS_PPTP
    Netcfg -l %windir%\inf\netrast.inf -c p -i MS_L2TP
    Then reboot the computer and see how it works.
    Meanwhile, I would like to share the following with you for your reference:
    Troubleshooting common VPN related errors
    Hope this helps. Thanks.
    Nicholas Li - MSFT

  • Error 720: A connection to the remote computer could not be established.

    So I got an aircard Novatel P720. It was working fine for months. Then I installed a VPN connection. Now, I get this error.
    Error 720: A connection to the remote computer could not be established.
    Most of of what I found recommends uninstalling the WAN Miniport (IP), it seems that  I have to go thru so many hoops to get this fixed. Wondering if I would be better off rebuilding my machine from scratch again. Is there an patch or another way to get me going.
    I think this is an old issue. Lots of comments on this thru Google. I am hoping I can get a definative answer from Lenovo's itself!

    josezald wrote:
    So I got an aircard Novatel P720. It was working fine for months. Then I installed a VPN connection. Now, I get this error.
    Error 720: A connection to the remote computer could not be established.
    Most of of what I found recommends uninstalling the WAN Miniport (IP), it seems that  I have to go thru so many hoops to get this fixed. Wondering if I would be better off rebuilding my machine from scratch again. Is there an patch or another way to get me going.
    I think this is an old issue. Lots of comments on this thru Google. I am hoping I can get a definative answer from Lenovo's itself!
    Well, seeing since your having an Issue with a non Lenovo product. I dont think your going to get an official answer from Lenovo. You may get suggestions however. 
    Ignorance is no excuse!

  • VPN ERROR 619 :: A connection to the remote computer could not be established, so the port used for this connection was closed

    I have been searching endlessly for this issue. Every time I try to connect to a VPN connection I get the error above. Thank you for any relevant input concerning this matter. My NIC is Qualcomm Atheros and I'm in Win8.1 x64.

    everything normal before?
    is there any changes before this issue happen?
    turn off your antivirus and firewall, update the latest VPN client software, if still not working go to security settings and change the VPN type automatic to PPTP. And also change data encryption configuration to Optional and select CHAP & MS-CHAP v2.
    If still not working try with other internet connection and try to contact your VPN provider

  • A connection to the QuickTime server could not be established. This computer may be having trouble accessing the Internet or the server may be offline

    When I select “Update existing software in QuickTime Pro I get an error message saying “A connection to the QuickTime server could not be established. This computer may be having trouble accessing the Internet or the server may be offline”
    This has persisted for several weeks. Any help will be welcomed as I do not know how to contact QuickTime support via Apple.
    I am using Windows 7 64 bit.  
    Many thanks

    I was able to download and install the latest version of iTunes  (10.6.3.25) without a hitch. After the reboot I tried again to update my exisitng Quicktime Pro software as described in my original posting and got exactly the same error message.
    If it happens that there is no software to download because I am already running the latest version, surely a message to that effect would appear and not the one saying “A connection to the QuickTime server could not be established. This computer may be having trouble accessing the Internet or the server may be offline”
    Still seeking advice if possible
    Cheers

  • The remote computer could not be found. please contact your helpdesk

    RDS Farm set up as follows 3- RD Session Host/Web servers set up as network load balanced  and 2-RD Connection broker servers set up as clustered servers. I access the RdWeb farm from the internet via VPN clientless. I can get into
    RdWeb with no problems, however I have few clients that can connect to RdWeb portal but once they open any application icon the error gets displayed "the remote computer could not be found. please contact your helpdesk ".  The client
    pc is Windows 8 with IE11 and Windows 7 with IE 10.  I could not find anything that related to some users that could not connect. Help!

    Hi,
    Firstly please provide some more information from your side.
    1.  Does the other user can able to work properly without any issue?
    2.  Did you install the RD gateway role to allow the external user to access the internal resource? If so, please help to make sure you configure the FQDN for the RD gateway, and the external users can resolve this name on the internet.
    3.  Can you telnet the RD host server (like telnet server name 3389) to check whether the RD host server is available for another server?
    4.  Did you try to temporarily disable all of firewall and anti-virus to test if this issue persists?
    You can configure RD Web Access behavior on IIS manager as per below.
    IIS Manager Console > Default Web Site > RDWeb > Pages > Application Settings > DefaultTSGateway > add the "FQDN of the Remote Desktop Gateway"
    After finishing all above steps, please launch the RemoteApp again to see if the same issue still exists. For more information, you can refer beneath article.
    Configure Remote Desktop Web Connection Behavior
    Hope it helps!
    Thanks.

  • The remote computer could not be found

    Guys,
    Im having this error message pop up when I launch a remoteapp from an external network through the rd web access page. On the deployment settings I have the gateway setting to "automatically detect rd gateway server settings". This always givves
    me this error regardless of whether I edit the rdweb access application settings and add the defaultTSGateway : External FQDN. 
    If I switch the rd gateway settings in deployment proprties to "Use this rd gateway server setting" : external FQDN it works fine.
    can someone tell me why? how does the automatically detect rd gateway server setting work and if it's even supposed to work if I am accessing apps externally?

    Hi,
    You should select Use these RD Gateway server settings in most cases.  Automatically detect is for when the client PCs are domain-joined and you have specified the RD Gateway settings using group policy.
    -TP

  • The remote name could not be resolved

    We are running Office 365 Power BI (as a trial) and published our data through the data manager gateway service.
    We are able to retrieve a list of shared tables / views through Power Query in Excel 2013 Professional Plus.
    However, when clicking on edit on any table returned we get this error in the Power Query window:
    DataSource.Error: OData: Request failed (NameResolutionFailure):
    The remote name could not be resolved: 'SERVER-NAME.DOMAIN.local'
    Details: https://POWERBISITE.hybridproxy.powerbi.com/ODataService/v1....
    I have tried configuring the Data Manager Gateway service to run HTTP (at first) and HTTPS.
    Could this be a port number issue? Or what else?
    Appreciate any help, Thank you
    Ian

    Hi intrasight,
    I gave the hosts thing a try.
    I was getting 'unable to resolve' errors in attempting to use Power Query in a small stand-alone test domain (all computers are in the domain, and in this little LAN).  So I edited
    hosts in C:\Windows\System32\drivers\etc
    I added this line: 
    192.168.0.4 mycomputer.ad.mydomain.com
    mycomputer is the name of the computer running the Data Management Gateway, and
    ad.mydomain.com is the name of the domain.
    Now, I get
    <textarea class="role-selectableText" cols="1" readonly="readonly" rows="1" style="width:659px;height:87px;" tabindex="-1">DataSource.Error: OData: Request failed: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS
    secure channel. Details: https://mydomain.hybridproxy.powerbi.com/ODataService/v1.0/mydatasource</textarea>
    Which tells me that hosts on the client is indeed now resolving the name/IP correctly, and Power Query is  finding the DMG directly (rather than via the
    hybridproxy.powerbi.com cloud service).
    But that's terrible!  
    A) I shouldn't need to use hosts since
    B) the hybridpproxy cloud service is finding the DMG on my database machine (because the Test Connection works OK) 
    C) but without hosts the client Power Query says that "The remote name could not be resolved"
    DataSource.Error: OData: Request failed: The remote name could not be resolved: 'mycomputer.ad.mydomain.com'
    Details:
    https://mydomain.hybridproxy.powerbi.com/ODataService/v1.0/mydatasource
    There's no way an actual production system should require editing
    hosts on all client machines.
    So to my mind, the original question is still outstanding. 
    How do I get Power Query to resolve the remote name?
    Cheers, Donna
    Donna Kelly

  • A connection to the deployment share could not be made. connection ok

    hi,
    i have deployment windows 7 by MDT，and there is something wrong with the test. i have a MDT Service and 2 clients that one is updated and another is used to capture the image.but when i captured the image,there is error."a connection to the deployment
    share could not be made. connection ok" 

    i create and capture the image from a physical
    machine,and i create the network drivers on the MDT console. And it will generate the winPE.When i capture
    and restart the machine, it will get the error. 

  • We are using the Azure server for our web services. Server is generating an error "Unable to connect to the remote server". What is this error means

    We are using the Azure server for our web services. Server is generating an error "Unable to connect to the remote server". What is this error means  

    Hello,
    Did you means that you use the Windows Azure Virtual Machine DNS name as the server name in the Reporting Server Web Services URL?
    For example:
    Report server:http://uebi.cloudapp.net/reportserver
    Report manager:http://uebi.cloudapp.net/reports
    If you want to connect to Report Manager on the virtual machine from a remote computer, you should create a  virtual machine TCP Endpoint and open the port in the virtual machine’s firewall. By default, the report server listens for HTTP requests
    on port 80.
    Reference:http://msdn.microsoft.com/en-us/library/jj992719.aspx#bkmk_ssrs_connect_2_remote_RM
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • ITunes - An Error occured while connecting to the remote speaker. (-15000)

    I have been using airportexpress for the last 9 months with no problem. I used to use Windows Vista (32bit) to play itunes music and stream the music to the airportexpress which connects to my living room AV system.
    Couple of days ago, I rebuilt my machine now running Win7 (64bit). Since then, I am not able to stream the audio to the airport express. Whenever I select the remote speakers, wait for about 30 secs and I get this error : An error occurred while connecting to the remote speakers "livingroom". An unknown error occured (-150000).
    Does anyone experience this ? From the same machine, I am able to connect to the airport express using the airport utility. Wireless is working fine. I just not able to stream my music to it.
    Regards
    Moehadi

    moehadi, Welcome to the discussion area!
    This is typically caused by a firewall or Internet security software running on your PC. Please read the comments in "Error -3256 or -15000 when streaming to AirPort Express base stations using iTunes".
    Also there is "iTunes 8: Unknown error -15000 when attempting to stream music to devices connected to AirPort Express with AirTunes".

  • An error occurred while connecting to the remote speaker. The network connection failed.

    I can't get my itunes to connect to the remote speakers via airport express anymore  - I did not change any settings - but did update iTunes to 10.2.2 and now things are not working and I get his message - "An error occurred while connecting to the remote speaker “Living Room”. The network connection failed."
    Does anybody have a fix for this problem?
    thanks

    Same problem for me. Ever since I upgraded to 10.6.3 and iTunes 9.1, about once per week I'll get the error message when trying to get iTunes/Airtunes to connect to my older Airport Express (running firmware 6.3) "An error occurred while connecting to the remote speaker <insert speaker name here>. The network connection failed." (No error codes are given.)
    Airport Utility sees the offending Airport Express just fine (and there's a green light on said AE).
    Curiously, a newer AE-n, elsewhere in the house (running firmware 7.4.2) does NOT exhibit this problem.
    Simply restarting the offending AE does NOT clear the problem. Restarting the main router - a Time Capsule DOES clear the problem. Alternatively, toggling off the Airtunes functionality on the offending AE, restarting it, then toggling Airtunes back on, and finally restarting it DOES clear the problem (as an alternate to restarting the router). No matter how the problem is cleared, it returns within a week. It's frustrating that the problem cannot be recreated immediately.
    Probably not relevant, but the computer on which I'm running iTunes (a Mac Mini) is connected to my TC via ethernet, not wirelessly.
    I've tried the suggestion of disabling ipv6. No effect.
    I fear the only solution will be to scrap my older Airport Express and replace it with a newer n-model. But before I resign myself to the $100 fix, any more ideas?

  • A Connection to the deployment share could not be made....

    Hi,
    I know this question has been posted a fair number of times on the forums but so far none of the responses have fixed my issue.
    I am having trouble connecting to the deployment share receiving the error message below.
    "A connection to the deployment share could not be made. The deployment will not proceed.
    The following networking device did not have a driver installed PCI\VEN_10EC&DEV_8168&SUBSYS_00041179&REV_10"
    I have downloaded the correct network drivers and even installed Windows 7 manually and added
    the drivers to check they are correct drivers.
    I have added them to the OOB drivers in the deployment share and then updated and also regenerated
    the deployment share. Then i have updated the .wim file in the boot images folder but yet i still cannot get past this stage.
    Does anyone have any further ideas that i could try?
    Thanks,
    Adam

    Hi,
    I can exit to cmd and attempt ipconfig/ping etc. but get confirmation that there is no IP.
    The imaging process is working for older versions of laptops and Netbooks but not for the newer models. They are all Toshiba models.
    [Settings]
    Priority=Default
    Properties=MyCustomProperty
    [Default]
    _SMSTSORGNAME=(*****)
    OSInstall=YES
    SkipAdminPassword=YES
    SkipApplications=YES
    SkipAppsOnUpgrade=YES
    SkipBDDWelcome=YES
    SkipBitLocker=YES
    SkipCapture=YES
    SkipComputerName=NO
    SkipComputerBackup=YES
    SkipDeploymentType=YES
    DeploymentType=NEWCOMPUTER
    SkipDomainMembership=YES
    JoinDomain=(*****)
    DomainAdmin=Build
    DomainAdminDomain=(*****)
    DomainAdminPassword=(*****)
    SkipFinalSummary=YES
    SkipLocaleSelection=YES
    KeyboardLocale=en-GB
    UserLocale=en-GB
    UILanguage=en-GB
    SkipPackageDisplay=YES
    SkipProductKey=YES
    SkipSummary=YES
    SkipTaskSequence=NO
    SkipTimeZone=YES
    TimeZoneName=GMT Standard Time
    skipUserData=Yes
    FinishAction=LOGOFF
    I have removed some of the information of the organisation with (*****)
    Thanks,
    Adam

  • Connection to the deployment share could not be made (network driver not installed)

    Hi guys! i bought the new laptop Dell Latitude E6510 and try to install the enterprise image but i got the error:
    "A connection to the deployment share could not be made. The deployment will not proceed. The following networking device did not have a driver installed PCI\VEN_8086&DEV_10EA&SUBSYS_040B1028&REV_05."
    I look on internet and i found out that it is the intel network card driver missing. So i get the driver from Dell website and i added this drivers in the MDT console.
    Then i have updated the deployment share to rebuild the boot images. Everything went fine but i always get this error.
    Am I missing something ?

    I too was having the problem...
    the single thing that I was forgetting is that while I was recreating & regenerating the images in the deployment workbench. I wasn't burning & booting from a CD...
    because (aha) I'm clever & using Windows deployment services to boot across the network & save all that time burning CDs etc.
    Doh, I didn't update the WIM that WDS was using...
    Open your windows deployment services console,
    expand out servers : <server name> : boot images
    Right click your boot image (I have 2, one for x86 & one for x64),
    choose "replace image" then navigate to your newly regenerated WIM images
    (probably C:\deployment_share\boot) & choose the appropriate WIM file.
    do this for any images you have, reboot your client machine & BAM, deployment goodness.
    MS should really add a module for PXE boot (etc) into the deployment workbench rather than have 2x deployment solutions & use the deployment module from one & the boot module from the other.
    Anyhoo, works now, must make a mental note to remember this in future...
    Cheers Toolman
    Thank you for this.  This resolved the issue that I had.

Maybe you are looking for