QVidium QVMP2C-1011 - Manual (Page 30)

User’s Manual v.28 QVidium™ MPEG2+4 Codec
30 of 45 - Copyright 2007-2008 QVidium™ Technologies, Inc.
2. Make certain that device is powered on and connected to your network.
3. Check that green LAN light in front is lit and link light at RJ-45 port is on.
4. Try pinging the encoder by entering the IP address for the source device. For a MPEG2+4
Codec, try clicking on “Network/Ping”.
5. Make certain that both encoder and decoder are set to the same stream type (Program or
Transport), the same transport type (ProMPEG, ARQ, RTP, or UDP) and encoding type
(MPEG2 or MPEG4). For a Set-Top Box, such as an Amino, make certain that the encoder
is set to Transport & UDP.
Cannot access MPEG2+4 Codec via network via wireless interface
1. For the following steps, connect a PC through the Ethernet interface.
2. Click on the Wireless/Scan menu and verify that the ESSID is specified correctly. Note
that the ESSID is case sensitive and must match exactly.
3. Check that the wireless IP address is unique and the wireless subnet does not conflict with
the Ethernet subnet. For example, if the Ethernet IP Address is at 192.168.1.100, with
netmask 255.255.255.0, then at least one of the first 3 octets of the wireless IP address
must be different, such as 192.168.2.XXX, where XXX can be any number from 1 through
254 that does not conflict with either the wireless access point or any other wireless device
on the same WiFi network. Alternatively, the wireless IP address could be 10.10.1.100,
etc.
4. Make certain that the wireless interface is set to the same mode as your wireless access
point. If the scan says that your access point is “Managed”, then set the wireless interface
to Managed. If the access point is Ad-Hoc, then configure the Codec to Ad-Hoc.
5. Check that the address on the LAN you are using is not on the same subnet as the
Ethernet interface’s subnet. The MPEG2+4 Codec continues to have an active Ethernet
subnet, even if nothing is connected to the Ethernet interface. If the Ethernet address
is at 192.168.1.100, for example, and you are using a computer at 192.168.1.10 that
connects to the WiFi interface via a router, then you will not be able to access the
MPEG2+4 Codec. A packet going to the MPEG2+4 Codec will have a source address of
192.168.1.10. When that packet enters the Codec, then the reply packet will route to the
local, unplugged Ethernet port and not be accessible to your network. All address on the
same subnet must be directly accessible. In this example, the address 192.168.1.100 is
not accessible to the PC at 192.168.1.10, even though they are on the same subnet
(assuming that the subnet masks are 255.255.255.0).