Common VMS Gateway networking issues
Updated over a week ago

If you are having trouble getting your VMS or ONVIF Device Manager/VLC to see or stream from your VMS Gateway here are a list of common issues that can stop your system from operating correctly:

  • You must be sure that every IP address you use allocate to VMS Gateway is not used by other devices on your network. You should check with your IT administrator what the DHCP reservation range is on your network and avoid it - it's better to find out a range that is reserved for static IP address usage.

  • ONVIF discovery relies on multicast packets being allowed on your network - if the are blocked then you will have to manually add your ONVIF devices to your VMS.

  • Multicast packets are usually limited to the same LAN subnet. If your VMS is on a different subnet to VMSG it is likely that you'll need to manually add your ONVIF devices to your VMS.

  • If you've installed VMS Gateway onto a virtual machine, you must ensure that each virtual machine has a unique and free IP address on your network - and don't accidentally give the virtual machine the same address as the host PC.

  • Virtual machine usage will not work with a 'switched network' (usually the default) and requires the used of a 'bridged network'. If the IP address of your VMS Gateway and the host PC do not have the same first three digits (e.g. and then it is unlikely VMS Gateway will be visible on the local network.

  • Virtual machine usage requires special features enabled, as virtual ONVIF devices will send traffic from a 'virtual' MAC address.


Did this answer your question?