beautypg.com

Network video server user’s guide – Intellinet Network Solutions 550000 User Manual

Page 53

background image

Network Video Server User’s Guide

53

Symptoms, Possible Causes and Remedial Actions

Symptoms Possible causes Remedial actions

The IP address is
already used by another
devices

1.Disconnect your NETWORK VIDEO SERVER
from the network
2. Run the PING utility (as described in PINGing
your IP Address below) and follow

The IP address is
located within a
different subnet

Run the PING utility (as described in PINGing Your
IP Address, on page 51), If the utility returns “no
response” or similar, the diagnosis is probably
correct – you should then proceed as follows

In Windows 95/98 or Windows NT, check the IP
address for your NETWORK VIDEO SERVER is
within the same subnet as your workstation:
1.Click “Start”, “Settings”, “Control Panel” and
“Network”.
2.Specify the TCP/IP adapter and click on
“Properties”. In Properties, Click “IP Address”.
3.Check that the first 3 number blocks of the IP
address of your NETWORK VIDEO SERVER
match the first 3 number blocks of your workstation.
If not, your NETWORK VIDEO SERVER may be
on a different subnet and the IP address cannot be
set from this workstation. You must set the IP
address for NETWORK VIDEO SERVER from a
workstation on the same subnet.
Example:
IP Address Camera: 192.168.1.221
IP Address PC: 192.168.1.xxx.

Other networking
problems

Trying replacing your network cable

Test the network interface of the product by
connecting a local computer to the unit, using a
standard Crossover (hub-to-hub) Cable.

If the above actions do not resolve the problem,
NETWORK VIDEO SERVER maybe faulty, In this
case, try to localize the problem by connecting
NETWORK VIDEO SERVER to the serial port of a
local computer, using the supported RS232 Cable

NETWORK VIDEO
SERVER cannot be
accessed from a Web
browser
The Power LED is not
constantly lit

Faulty power supply

Verify that you are using an provided power supply

The network LED is off Faulty cabling

1.To verify that the cables are functional, PING the
address of a known existing unit on your network.
2.If the cabling is OK and your network is
reachable, your should receive the reply similar to
this:
. . . bytes = 32 time = 2 ms,