Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 15 of 16
  1. #1
    Administrator tplink has disabled reputation
    Join Date
    Mar 2012
    Posts
    438

    Solved the problem the PC can't create PPTP connection to TL-R600VPN unless reboot

    [Announcement]
    The new firmware can be used for TL-R600VPN_V1 only, it is strictly prohibited to upgrade if not this model, any incorrect upgrade will damage your device.

    [Firmware Version]
    TL-R600VPN_V1_130827_Beta

    [Release Note]
    Solved the problem that your PC can no longer create PPTP connection to TL-R600VPN unless you reboot it

    [Current State]
    The new beta firmware worked normally in our test LAB, now we are waiting for the further test results from our customers.

    [Beta firmware download link]
    http://www.tp-link.com/resources/sof...30827_Beta.zip

  2. #2
    Quote Originally Posted by tplink View Post
    [Announcement]
    The new firmware can be used for TL-R600VPN_V1 only, it is strictly prohibited to upgrade if not this model, any incorrect upgrade will damage your device.

    [Firmware Version]
    TL-R600VPN_V1_130827_Beta

    [Release Note]
    Solved the problem that your PC can no longer create PPTP connection to TL-R600VPN unless you reboot it

    [Current State]
    The new beta firmware worked normally in our test LAB, now we are waiting for the further test results from our customers.

    [Beta firmware download link]
    http://www.tp-link.com/resources/sof...30827_Beta.zip
    Works fine so far!

  3. #3

    What for V2?

    I have latest firmware (TL-R600VPN_V2_130831) for V2 that should repair it also, and its not! Its still the same? Should I throw it away and buy something else?

  4. #4

  5. #5

    Firmware update changed the hardware version of my TL-R600VPN

    I had hardware version 1 of this router, so I installed the latest firmware update for it. The filename was: r600vpnv1_en_1_2_1_up(130831).bin

    Now the router's status page says this:

    1.2.1 Build 130831 Rel.63039n
    Hardware Version:
    R600VPN v2 00000000

    It seems unlikely that the firmware magically turned my hardware into v2. Can you advise, please?

  6. #6
    Quote Originally Posted by TnIan View Post
    I had hardware version 1 of this router, so I installed the latest firmware update for it. The filename was: r600vpnv1_en_1_2_1_up(130831).bin

    Now the router's status page says this:

    1.2.1 Build 130831 Rel.63039n
    Hardware Version:
    R600VPN v2 00000000

    It seems unlikely that the firmware magically turned my hardware into v2. Can you advise, please?
    I just posted the same question. Have you received an answer?

  7. #7

    Exclamation cant connect to my pptp with my dynamic ip address

    Firmware Version:
    1.2.1 Build 130831 Rel.63039n
    Hardware Version:
    R600VPN v2 00000000


    any solution on how to connect my PPTP VPN Server ?
    1. i use dynamic ip address of my own TL-R600VPN to set into my phone.
    2. i had created username n password for it.
    3. my phone using 3G,yet i cant connectName:  acc_set.jpg
Views: 0
Size:  93.6 KBName:  ser_set.jpg
Views: 0
Size:  84.3 KB
    i had follow the guide from the support pages and pdf files, yet i cant connect.

    please help.

  8. #8
    i too can nolonger establish pptp connection after the latest firmware upgrade.

    Below is a sample log file of what occurs on an inbound request for pptp connection from a client.

    ################################################## ##################
    # TL-R600VPN System Log
    # Time = 2014-09-09 21:00:09 345626s
    # H-Ver = R600VPN v2 00000000 : S-Ver = 1.2.2 Build 140422 Rel.33638n
    # L = 192.168.1.1 : M = 255.255.255.0
    # W1 = DHCP : W = 23.241.222.92 : M = 255.255.252.0 : G = 23.241.220.1
    ################################################## ##################

    Sep 9 00:01:29 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:32 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:35 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:38 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:41 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:44 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:47 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:50 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:53 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0x2b8bfd41 pcomp accomp]
    Sep 9 00:01:56 PPP ERROR User request
    Sep 9 00:01:56 PPP INFO sent [LCP TermReq]
    Sep 9 00:01:59 PPP INFO sent [LCP TermReq]
    Sep 9 00:02:02 VPN INFO PPTPS CTRL: Client 67.77.147.79 control connection started
    Sep 9 00:02:03 VPN INFO PPTPS CTRL: Client 67.77.147.79 control connection finished
    Sep 9 00:02:03 VPN INFO PPTPS CTRL: Client pppd TERM sending
    Sep 9 00:02:03 VPN INFO PPTPS CTRL: Client pppd finish wait
    Sep 9 00:02:03 VPN INFO PPTPS CTRL: Starting call (launching pppd, opening GRE)
    Sep 9 00:02:03 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:06 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:09 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:12 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:15 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:18 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:21 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:24 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:27 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:30 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xcec5ecb2 pcomp accomp]
    Sep 9 00:02:33 PPP ERROR User request
    Sep 9 00:02:33 VPN INFO PPTPS CTRL: Client 67.77.147.79 control connection finished
    Sep 9 00:02:33 VPN INFO PPTPS CTRL: Client pppd TERM sending
    Sep 9 00:02:33 VPN INFO PPTPS CTRL: Client pppd finish wait
    Sep 9 00:02:38 VPN INFO PPTPS CTRL: Client 67.77.147.79 control connection started
    Sep 9 00:02:39 VPN INFO PPTPS CTRL: Starting call (launching pppd, opening GRE)
    Sep 9 00:02:39 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:02:42 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:02:45 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:02:48 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:02:51 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:02:54 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:02:57 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:03:00 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:03:03 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:03:06 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xa8037d5a pcomp accomp]
    Sep 9 00:03:10 PPP ERROR User request
    Sep 9 00:03:10 VPN INFO PPTPS CTRL: Client 67.77.147.79 control connection finished
    Sep 9 00:03:10 VPN INFO PPTPS CTRL: Client pppd TERM sending
    Sep 9 00:03:10 VPN INFO PPTPS CTRL: Client pppd finish wait
    Sep 9 00:03:15 VPN INFO PPTPS CTRL: Client 67.77.147.79 control connection started
    Sep 9 00:03:16 VPN INFO PPTPS CTRL: Starting call (launching pppd, opening GRE)
    Sep 9 00:03:16 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:19 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:22 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:25 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:28 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:31 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:34 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:37 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:40 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:43 PPP INFO sent [LCP Req asyncmap=0x0 auth=chap-MS-v2 magic=0xb15c418f pcomp accomp]
    Sep 9 00:03:46 PPP ERROR User request
    Sep 9 00:03:46 PPP INFO sent [LCP TermReq]
    Sep 9 00:03:49 PPP INFO sent [LCP TermReq]
    Sep 9 00:03:52 VPN INFO PPTPS CTRL: Client 67.77.147.79 control connection finished
    Sep 9 00:03:52 VPN INFO PPTPS CTRL: Client pppd TERM sending
    Sep 9 00:03:52 VPN INFO PPTPS CTRL: Client pppd finish wait
    Sep 9 06:10:10 DHCP NOTICE DHCPC Send REQUEST to server 142.254.237.21 with request ip 23.241.222.92
    Sep 9 06:10:11 DHCP NOTICE DHCPC Recv ACK from server 142.254.237.21 with ip 23.241.222.92 lease time 86400
    Sep 9 06:10:11 DHCP NOTICE DHCPC:GET ip:23.241.222.92 mask:255.255.252.0 gateway:23.241.220.1 dns1:209.18.47.61 dns2:209.18.47.62 static route:0
    Sep 9 06:10:11 DHCP NOTICE Dynamic IP(DHCP Client) obtained an IP successfully
    Sep 9 07:40:35 DHCP NOTICE DHCPS:Recv REQUEST from 00:26:2D:22:3D:18
    Sep 9 07:40:35 DHCP NOTICE DHCPS:Send ACK to 192.168.1.101
    Sep 9 07:40:56 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 07:42:11 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 07:43:34 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 07:46:51 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 07:48:11 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 07:53:36 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 07:58:13 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:03:38 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:08:16 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:13:41 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:18:19 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:23:43 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:28:21 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:33:46 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:38:23 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:43:49 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:48:26 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:53:51 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 08:58:28 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:03:54 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:08:30 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:13:56 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:18:33 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:23:59 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:28:35 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:34:01 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:38:37 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:44:04 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:48:40 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 09:54:06 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:04:08 DHCP NOTICE DHCPS:Recv REQUEST from 00:26:2D:22:3D:18
    Sep 9 12:04:08 DHCP NOTICE DHCPS:Send ACK to 192.168.1.101
    Sep 9 12:04:10 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:05:33 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:15:36 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:25:38 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:30:42 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:35:41 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:45:43 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 12:55:46 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 13:05:48 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 13:15:51 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 13:22:58 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 13:25:53 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 13:35:55 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 13:45:58 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 13:56:00 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 14:06:03 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 14:16:05 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 14:26:08 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 14:36:10 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 14:46:13 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 14:56:15 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 15:06:18 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 15:16:20 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 17:24:25 DHCP NOTICE DHCPS:Recv REQUEST from 00:26:2D:22:3D:18
    Sep 9 17:24:25 DHCP NOTICE DHCPS:Send ACK to 192.168.1.101
    Sep 9 17:24:28 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 17:24:28 DHCP NOTICE DHCPS:Recv REQUEST from 00:26:2D:22:3D:18
    Sep 9 17:24:28 DHCP NOTICE DHCPS:Send ACK to 192.168.1.101
    Sep 9 17:25:51 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 17:35:53 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 17:45:56 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 17:55:58 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 18:04:00 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 18:06:01 DHCP NOTICE DHCPS:Recv INFORM from 00:26:2D:22:3D:18
    Sep 9 18:10:12 DHCP NOTICE DHCPC Send REQUEST to server 142.254.237.21 with request ip 23.241.222.92

  9. #9
    I have opened a support ticket with TPLink and have been told that it is okay to update a router with a V1 tag to the latest V2 firmware.

    I suspect that most of us have resisted doing this based on text in the OP's post where it says:

    [Announcement]
    The new firmware can be used for TL-R600VPN_V1 only, it is strictly prohibited to upgrade if not this model, any incorrect upgrade will damage your device.


    Here is the response from TPLink support:



    " > I understand that there is an updated firmware for the V2 of the 600VPN. But
    my device is actually a V1.1 based on the ID Tag on the unit. (See enclosed image).
    >
    > The problem is that when I updated to 1.2.1 Build 130831 Rel.63039n the Web
    page information was changed to read Hardware Version: R600VPN v2 00000000.
    There are others in the tech support forum who have the same issue.
    >
    > I am concerned that if I use the update intended for V2 it will damage my device.



    Thanks for your valued reply,
    I'm so sorry for the inconvenience.
    The firmware of V2 can be used to updated your TL-R600vpn (v1).
    Don't worry about this.




    Best Regards
    ----------------------------------------------
    Allan liu
    TP-LINK Technical SupportWebsite:
    "


    I haven't attempted this yet. If you don't hear from me assume it failed
    Last edited by Jimmersd; 09-23-2014 at 12:51.

  10. #10
    Okay, the V2 firmware does work on the V1 device.

    Firmware Version:
    1.2.3 Build 140801 Rel.49374n
    Hardware Version:
    R600VPN v2 00000000


    TPLink just doesn't pay attention to this forum. And their instructions are lacking in clarity.

    The only guidance I can give you is when I did this I couldn't connect to the router's web page at first. Although the box had retained my original configuration and was available on it's old IP address and I did get internet. The web interface was a blank page that wouldn't load. I was forced to reset to defaults before I could logon using the default IP 192.168.0.1 and admin/admin. Then I was able to reload my configuration data which I had saved.

    Lets see if this resolves the intermittent dropped WAN port and other issues.

    Good luck!

  11. #11
    hi Jimmersd,

    can you help me please, I have TL-ER604W and try to setup VPN based and follow tplink vpn guide but unable to stablish connection.. i have posted my config on my post..

    thank you.. appreciate your help..

  12. #12
    Quote Originally Posted by odie View Post
    hi Jimmersd,

    can you help me please, I have TL-ER604W and try to setup VPN based and follow tplink vpn guide but unable to stablish connection.. i have posted my config on my post..

    thank you.. appreciate your help..

    I'm sorry Odie. I do not own that type of router. This topic concerns the TL-R600VPN. The correct topic for you to search is here http://forum.tp-link.com/forumdispla...odel=TL-ER604W. If you still can't find an answer there I suggest that you open a support ticket directly with TPLink. Good luck.

  13. #13
    Hi Experts,<br>
    In beginning of purchase I upgraded to 1.2.2 Build 140422 Rel.33638n and didnít check the hardware version, I think this one belong to the V2. Router is working fine but with only one problem Dynamic DNS update failed once internet. <br>
    Is there any way to downgrade for fixation ? <br>
    <br>
    [IMG]file:///C:\Users\ADMINI~1\AppData\Local\Temp\msohtmlclip1\ 01\clip_image001.jpg[/IMG]<br>
    <br>
    in contact with direct support they just send me the link only which is mentioned below , if i am updating with V1 firmware its also showing same error , is any one have solution ?<br>
    <br>
    -----------------------------------------------------------------------------------------------------------------------------------------------------<br>
    <br>
    <strong>From:</strong> TP-LINK Technical Support [<a href="mailto:support.mea@tp-link.com">mailto:support.mea@tp-link.com</a>]<br>
    <strong>Sent:</strong> Sunday, April 10, 2016 11:57 AM<br>
    <strong>To:</strong> Hassan Javed<br>
    <strong>Subject:</strong> RE: TL-R600VPN V2<br>
    <br>
    Dear Hassan ,<br>
    Please ensure you are try to upload matching file .<br>
    Please check the link below to know how upgrade your firmware to latest version <br>
    <a href="http://www.tp-link.com/en/faq-688.html" target="_blank">http://www.tp-link.com/en/faq-688.html</a><br>
    Best Regards <br>
    <br>
    <strong>From:</strong> Hassan Javed <br>
    <strong>Sent:</strong> Saturday, April 09, 2016 4:52 PM<br>
    <strong>To:</strong> <a href="mailto:support.mea@tp-link.com">support.mea@tp-link.com</a><br>
    <strong>Subject:</strong> TL-R600VPN V2<br>
    <br>
    Dear Support,<br>
    I am facing trouble for upgrade in firmware of subjected model router. The errors is mentioned in 2<sup>nd</sup> image whereas current version is as well mentioned in 1<sup>st</sup> image. <br>
    <br>
    <br>
    1.<br>
    [IMG]file:///C:\Users\ADMINI~1\AppData\Local\Temp\msohtmlclip1\ 01\clip_image001.jpg[/IMG]<br>
    <br>
    <br>
    2.<br>
    [IMG]file:///C:\Users\ADMINI~1\AppData\Local\Temp\msohtmlclip1\ 01\clip_image002.jpg[/IMG]

  14. #14
    Hi Experts,
    In beginning of purchase I upgraded to 1.2.2 Build 140422 Rel.33638n and didnít check the hardware version, I think this one belong to the V2. Router is working fine but with only one problem Dynamic DNS update failed once internet.
    Is there any way to downgrade for fixation ?


    in contact with direct support they just send me the link only which is mentioned below , if i am updating with V1 firmware its also showing same error , is any one have solution ?

    -----------------------------------------------------------------------------------------------------------------------------------------------------

    From: TP-LINK Technical Support [mailto:support.mea@tp-link.com]
    Sent: Sunday, April 10, 2016 11:57 AM
    To: Hassan Javed
    Subject: RE: TL-R600VPN V2

    Dear Hassan ,
    Please ensure you are try to upload matching file .
    Please check the link below to know how upgrade your firmware to latest version
    http://www.tp-link.com/en/faq-688.html
    Best Regards

    From: Hassan Javed
    Sent: Saturday, April 09, 2016 4:52 PM
    To: support.mea@tp-link.com
    Subject: TL-R600VPN V2

    Dear Support,
    I am facing trouble for upgrade in firmware of subjected model router. The errors is mentioned in 2nd image whereas current version is as well mentioned in 1st image.


    1.
    [IMG]file:///C:\Users\ADMINI~1\AppData\Local\Temp\msohtmlclip1\ 01\clip_image001.jpg[/IMG]


    2.
    [IMG]file:///C:\Users\ADMINI~1\AppData\Local\Temp\msohtmlclip1\ 01\clip_image002.jpg[/IMG]

  15. #15

    Solved the problem the PC cant create PPTP connection to TL R600VPN unless reboot

    Having changed the SIP server address to sip.voipfone.co.uk, the Register Server to sip.voipfone.co.uk, and the SIP Service Domain setting to sip.voipfone.co.uk; I find that I can longer register my VOIP connection anymore.Does anyone out there have any idea as to why this might be?Thank you in advance.JdeP
    [url=http://amberwizard.eu]AMBERZODIAC SIGN Amberwizard


 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright © 1996-2017 TP-LINK Technologies Co., Ltd. All rights reserved.