NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Management Interface unreachable when a connected webcam is viewed
Hello, I use the GS108PEv3 to connect an AXIS webcam to it. The switch provides PoE für the webcam. The webcam operates fine with the switch. When I use the live view (Full HD, 25fps, H264 codec) t...
Hi GreenHell,
Kindly try to factory reset the GS108PEv3 back to factory defaults then reconfigure it from scratch and check if same problem will occur. Let us know the results.
Regards,
DaneA
NETGEAR Community Team
Hello DaneA,
thank you for your responste. Here the answers:
a. Is the Axis webcam directly connected to the GS108PEv3 switch? yes
b. Have you tried to connect the Axis webcam to other ports on the GS108PEv3 switch and check if same problem will occur? yes, the effect is the same
c. Are you using a CAT5e or CAT6 ethernet cables between the GS108PEv3 switch and the Axis webcam? yes. The counters for CRC error packets are all "0".
Kindly try to enable Flow Control on the GS108PEv3 switch then observe if same problem will occur. Kindly read pages 56-57 of the ProSAFE® Gigabit Web Managed (Plus) Switches User Manual here on how to manage Flow Control.
I enabled Flow Control on all ports. The situation is a little better, some PING are answered and the management interface is responding very slowly. Here the results of the ping to the IP address of the switch:
> ping 192.168.6.53
PING 192.168.6.53 (192.168.6.53) 56(84) bytes of data.
64 bytes from 192.168.6.53: icmp_seq=1 ttl=64 time=0.781 ms
64 bytes from 192.168.6.53: icmp_seq=2 ttl=64 time=0.716 ms
64 bytes from 192.168.6.53: icmp_seq=3 ttl=64 time=0.762 ms
64 bytes from 192.168.6.53: icmp_seq=4 ttl=64 time=0.731 ms
64 bytes from 192.168.6.53: icmp_seq=5 ttl=64 time=0.764 ms
64 bytes from 192.168.6.53: icmp_seq=6 ttl=64 time=0.788 ms
64 bytes from 192.168.6.53: icmp_seq=7 ttl=64 time=0.786 ms
64 bytes from 192.168.6.53: icmp_seq=8 ttl=64 time=0.837 ms
64 bytes from 192.168.6.53: icmp_seq=9 ttl=64 time=0.864 ms
64 bytes from 192.168.6.53: icmp_seq=10 ttl=64 time=0.729 ms
64 bytes from 192.168.6.53: icmp_seq=11 ttl=64 time=0.755 ms
64 bytes from 192.168.6.53: icmp_seq=12 ttl=64 time=0.743 ms
<-- HTTP-Connection with live-view to webcam started
64 bytes from 192.168.6.53: icmp_seq=15 ttl=64 time=109 ms
64 bytes from 192.168.6.53: icmp_seq=20 ttl=64 time=121 ms
64 bytes from 192.168.6.53: icmp_seq=21 ttl=64 time=119 ms
64 bytes from 192.168.6.53: icmp_seq=27 ttl=64 time=108 ms
64 bytes from 192.168.6.53: icmp_seq=29 ttl=64 time=116 ms
64 bytes from 192.168.6.53: icmp_seq=34 ttl=64 time=122 ms
64 bytes from 192.168.6.53: icmp_seq=38 ttl=64 time=125 ms
64 bytes from 192.168.6.53: icmp_seq=49 ttl=64 time=17.2 ms
64 bytes from 192.168.6.53: icmp_seq=52 ttl=64 time=24.0 ms
<-- HTTP-Connection with live-view to webcam ended
64 bytes from 192.168.6.53: icmp_seq=62 ttl=64 time=0.878 ms
64 bytes from 192.168.6.53: icmp_seq=63 ttl=64 time=0.748 ms
64 bytes from 192.168.6.53: icmp_seq=64 ttl=64 time=0.750 ms
64 bytes from 192.168.6.53: icmp_seq=65 ttl=64 time=0.705 ms
64 bytes from 192.168.6.53: icmp_seq=66 ttl=64 time=0.701 ms
64 bytes from 192.168.6.53: icmp_seq=67 ttl=64 time=0.746 ms
64 bytes from 192.168.6.53: icmp_seq=68 ttl=64 time=0.715 ms
^C
--- 192.168.6.53 ping statistics ---
68 packets transmitted, 28 received, 58% packet loss, time 68300ms
rtt min/avg/max/mdev = 0.701/31.364/125.540/50.075 ms
Hi GreenHell,
Here are my follow-up questions:
a. Are you using the ProSAFE Plus Configuration Utility to manage the GS108PEv3 switch? If yes, what is the version of the ProSAFE Plus Configuration Utility you are using?
b. I believe you are managing the GS108PEv3 switch using a browser. What browser(s) are you using?
c. Is a browser needed to be opened to use live view or are you using a software utility to open it?
Regards,
DaneA
NETGEAR Community Team
Hi DaneA,
here are your answers:
a. I use a WebBrowser to configure the switch
b. Firefox 49.0.2
c. I use the Firefox browser for the live view
Hi GreenHell,
Let us isolate the problem.
Scenario A:
1. Kindly download the latest version of the ProSAFE Plus Configuration Utility which is v2.3.20 here then install it to your PC.
2. Connect the same PC where you have installed the ProSAFE Plus Configuration Utility directly to the GS108PEv3.
3. Open the ProSAFE Plus Configuration Utility then check if it detects the GS108PEv3. If the GS108PEv3 is detected then you will be able to manage it using the utility.
4. Using the same PC, open live view using Firefox.
Note: Do not access the web-GUI of the GS108PEv3 switch using Firefox or any browser.
5. Open command prompt then ping the IP address of the GS108PEv3 switch.
6. Observe if same problem will occur.
Scenario B:
1. On the PC that is directly connected to the GS108PEv3, open Firefox then access the web-GUI of the GS108PEv3 switch.
2. Using the same PC, open another browser like Google Chrome or Inernet Explorer to open live view.
3. Open command prompt then ping the IP address of the GS108PEv3 switch.
4. Observe if same problem will occur.
Scenario C:
1. Kindly download the latest version of the ProSAFE Plus Configuration Utility which is v2.3.20 here then install it to PC1.
2. Connect PC1 directly to the GS108PEv3.
3. Open the ProSAFE Plus Configuration Utility then check if it detects the GS108PEv3. If the GS108PEv3 is detected then you will be able to manage it using the utility.
4. Connect PC2 directly to the GS108PEv3.
5. Open live view using Firefox on PC2.
Note: Do not access the web-GUI of the GS108PEv3 switch using Firefox or any browser.
6. Open command prompt on both PC1 and PC2 then ping the IP address of the GS108PEv3 switch.
7. Observe if same problem will occur.
Scenario D:
1. Connect PC1 directly to the GS108PEv3 then open Firefox to access the web-GUI of the GS108PEv3 switch.
2. Connect PC2 directly to the GS108PEv3 then open another browser like Google Chrome or Inernet Explorer to open live view.
3. Open command prompt on both PC1 and PC2 then ping the IP address of the GS108PEv3 switch.
4. Observe if same problem will occur.
Let us know the results.
Regards,
DaneA
NETGEAR Community Team
Hello DaneA,
for the tests, every devices wwas connected to the GS108PEv3. Flow control was disabled to have a very clear effect.
Scenario A: no problem (using the Internet Explorer instead of Firefox the problem is the same, there are ping timeouts)
Scenario B: same problem. ping timeout on PC
Scenario C: same problem, ping timeouts on both PC
Scenario D: same problem, ping timeouts on both PC
As soon as there are ping timeouts the ProSAFE Plus Configuration Utility also has timeouts.
Scenario A is no soultion for me as I use Linux for my daily work.
Btw, in my original network setup there is a GS108Tv1 as central switch. There is no ping timeout and no web management timeout while the live view is active, despite the data is traversing this central switch.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
