Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 12 of 12
  1. #1

    Thumbs up T1600-28TS.V2 Web-GUI crash after Port-check

    Model : T1600G-28TS

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    if i use the maintenance-function and use the port-check there, 2-3 times using it will crash the hole web-gui. Only factory-reset will it revive it. I can repeat it as many times i like. But i guess this machine is broken and i will return it.
    Any 1 else was able to notice this incident? Or can try it to reproduce?

  2. #2
    Quote Originally Posted by m-Lach View Post
    Model : T1600G-28TS

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    if i use the maintenance-function and use the port-check there, 2-3 times using it will crash the hole web-gui. Only factory-reset will it revive it. I can repeat it as many times i like. But i guess this machine is broken and i will return it.
    Any 1 else was able to notice this incident? Or can try it to reproduce?
    Port check? I guess you said is cable test, is it right? In my opinion, your device is T1600G-28TS V1(160412)

  3. #3
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Quote Originally Posted by m-Lach View Post
    Or can try it to reproduce?
    Can't reproduce this, but my switch version is HW v1.0 running SW 1.0.3 Build 20160412, not HW v2, which is still not available in my country for T1600G-28TS.

  4. #4
    i tested my new device today, also hardware 2.0.
    Unpack, put it on a table and did not mount it in my rack. Plugged my test-laptop via cable, used the Port or Cable-test-function 10 times - all fine.
    Changed IP-Adress, plugged in a 2nd Cable, used the testing-function again, all fine.
    Powered down, mount it in the rack, plug in all 14 cables, went into my office, start the computer, try to open the webinterface... nothing. Timeout.
    I guess i return this "box" also and buy a other device. but i guess there is not the name "tp-Link" on it. Or nay hints maybe?

  5. #5
    Quote Originally Posted by m-Lach View Post
    i tested my new device today, also hardware 2.0.
    Unpack, put it on a table and did not mount it in my rack. Plugged my test-laptop via cable, used the Port or Cable-test-function 10 times - all fine.
    Changed IP-Adress, plugged in a 2nd Cable, used the testing-function again, all fine.
    Powered down, mount it in the rack, plug in all 14 cables, went into my office, start the computer, try to open the webinterface... nothing. Timeout.
    I guess i return this "box" also and buy a other device. but i guess there is not the name "tp-Link" on it. Or nay hints maybe?
    so strange, now you do not configure cable test function, only connect 14 devices to the switch, you will not open the web interface.....
    Besides the issues of ip conflict, I do not know the reason.

  6. #6
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Quote Originally Posted by m-Lach View Post
    Changed IP-Adress, plugged in a 2nd Cable, used the testing-function again, all fine.
    Powered down, mount it in the rack, plug in all 14 cables, went into my office, start the computer, try to open the webinterface... nothing. Timeout.
    Did you remember to save the changed configuration before powering down? If not, try the switch's default IP.

  7. #7
    Some. News:
    After a factory-reset an re-configuration the Problem seems to be only a reset of the Webinterface if i try a cable-test on the port of the PC running the cleintbrowser-window. My own pc.
    here a video:
    https://drive.google.com/open?id=0B6...mJjWGVfNThuOVE

  8. #8
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    Uh, of course it will break the connection between your PC and the web UI if you are testing the port you're connected through to the web UI, so you will not see the result of the test!

    But the web UI is still operational, only your browser fails executing AJAX calls and obviously the browser on your PC remember this state until a reload of the web UI! My browser on a Unix system does not remember the state and lets me navigate through the web UI's menus as soon as the test has finished, although I don't see the result, too. That's not a bug in the switch's web UI!

  9. #9
    But the other Switch i returned allready, broke down totaly and was only able to resurrect by a factroy-reboot.
    Sure, it sounds locical, that there are some "happenings" if i test the port iam working on. But should not kick the hole gui in a coma.

  10. #10
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    The web UI heavily uses Javascript and AJAX calls. Therefore, if the connection is disrupted, communication between browser and web UI stops. Normally communication is resumed as soon as the connection returns to the "connected" state and it indeed does so on MacOS and Linux, but not on Windows. If you want to blame the software, blame Windows for this. The browser - or to be precise: the network layer of Windows - tries to be "super smart" and blocks communication with the message "Verbindung fehlgeschlagen".

    Thus, if something falls into coma, it's your browser due to response from the OS' network layer, not the switch's web UI. By forcing a reload, you wake up the browser from its coma. Sorry to say, but this is the normal Windows insanity. I experience a lot of such madness from Win users in our support every day where the OS thinks to know better what happens (not only with switches, but also with access points, Internet connections, etc.).
    Last edited by R1D2; 10-12-2017 at 19:49.

  11. #11
    sorry, but my other switch, i had, had a much worse behavior then this as shown in the video of the "newone". The oldone was totally down, even a power-reset did not help. Only a factory-reset helped to wake the gui of the switch. Sure i tried to reboot my pc during all the test and of curse before i factory-reset a "brand new" switch in my rack.
    So it seems, that the older switch was really defect and i returning it was the best way.
    For the new device was a bad start, that it showed me the same effect in 10 minutes after unpacking it.
    But it seems to work in a normal way if i interpret all the infos here right.
    So this thread can be closed i guess.
    thank you all a lot.

  12. #12
    Members R1D2 is on a distinguished road
    Join Date
    Dec 2015
    Posts
    1,127
    I can't say what was wrong with your first switch. Maybe it was broken. But clearly your video shows a typical Windows error which many users encounter every day. This OS tries to be "smart" for the average users and often spits out error messages b/c it misinterprets the real situation.

    You can proof that the switch's web UI indeed is still alive after the connection to your Win PC is disrupted by connecting another PC/laptop to another port and load the web UI there while the first port is being tested. I bet that the web UI is still alive.

    I can only tell you that every switch I got in my hand perfectly did run the cable test without any freeze or crash of the web UI or the switch, among those T1600G, TL-SG2008, TL-SG108 and some others There is definitely nothing wrong with the web UI. So I am convinced you misinterpret what you see in the video you made.
    Last edited by R1D2; 10-12-2017 at 20:37.


 

Tags for this Thread

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.