1. Forum
  2. Usenet
  3. COMP.OS.MS-WINDOWS.NETWOR

  • IP Cam: Pingable, but cannot connect?

    From [email protected]@21:1/5 to PeteCresswell on Thu Jun 7 11:38:09 2018
    On Sunday, August 18, 2013 at 12:06:00 AM UTC+3, (PeteCresswell) wrote:
    IP cam, local network (i.e. not across the WAN).

    SoftPerfect Network Scanner says it's on the network and exposing ports
    80 (HTTP) and 554 (RTSP).

    I can ping it as in:
    -----------------------------------------------
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    ping 10.0.0.138

    Pinging 10.0.0.138 with 32 bytes of data:

    Reply from 10.0.0.138: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.138: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.138: bytes=32 time<1ms TTL=64
    Reply from 10.0.0.138: bytes=32 time<1ms TTL=64

    Ping statistics for 10.0.0.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0%
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


    -----------------------------------------------

    But when trying to get to it's web page via
    Chrome as in HTTP: //10.0.0.138:80, Chrome
    returns:
    "No data received..
    Unable to load the webpage because the server sent no data.
    Error code: ERR_EMPTY_RESPONSE".

    I know the port is right because we have been using this
    cam for the best part of a year.

    I did the Control Panel | Java | General | Temporary
    Internet Files | Settings | Restore Defaults thing.
    And also clicked "Delete Files on the same dialog, but
    no joy.

    Also, IE cannot open it either - albeit returning
    only "The page cannot be displayed. Cannot find server or DNS Error".

    My kneejerk is that the cam's gone South.

    But a little voice is saying "User RCI"....

    Can anybody shed some light?

    --
    Pete Cresswell

    Did you find a solution for this?
    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From (PeteCresswell)@21:1/5 to All on Sun Jun 10 09:53:13 2018
    Per [email protected]:
    Did you find a solution for this?

    Not exactly a "Solution", but it seems that HikVision cams automagically
    become non-login-able after a certain number of failed attempts.

    But the state times out after a certain time and the "Solution" was to just wait it out.

    Also, I am pretty sure I found a Settings parm that will turn off that behavior.... I set it to False... but did not have the heart to test.

    Time will tell.
    --
    Pete Cresswell
    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)