• April 26, 2024, 05:55:12 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: DCS-5222L Ping But No Connect  (Read 9705 times)

kallunkija

  • Level 1 Member
  • *
  • Posts: 7
DCS-5222L Ping But No Connect
« on: December 10, 2013, 02:14:24 PM »

Hi All:
My remote DCS-5222L is hung up. One can ping it and it echos the ping.
But main console cannot connect to it. Main console cycles between showing
the word CONNECTED and then DISCONNECTED over and over forever.
I would like the telnet or ssh port, user name and password info so that I
can log in to Linux and do a reboot command to recover control of the camera.
The camera is in a remote unmanned location so there is nobody to power it
off/on or do a paper-clip reset. Need to do remote telnet or ssh login into the
Linux level to do a reboot command (Linux shutdown/restart). I am hoping this
will clear up the hang issue.
Thanks for the help! John
Logged

RYAT3

  • Level 10 Member
  • *****
  • Posts: 2254
Re: DCS-5222L Ping But No Connect
« Reply #1 on: December 10, 2013, 03:43:58 PM »

What software is doing the cycling?

Have you logged into the f/w?
Logged

kallunkija

  • Level 1 Member
  • *
  • Posts: 7
Re: DCS-5222L Ping But No Connect
« Reply #2 on: December 11, 2013, 01:39:50 AM »

web http traffic not operational at all (no response).
I would like to login to the FW as the next step.
I need the telnet and/or ssh port#, login user name and login password info so that I
can log in to the Linux FW and do a reboot command to recover control of the camera.
The camera is in a remote unmanned location so there is nobody to power it
off/on or do a paper-clip reset. Need to do a remote telnet and/or ssh login into the
FW Linux level to do a reboot command (Linux shutdown/restart). I am hoping this
will clear up the hang issue.
Thanks for the help! John
Logged

RYAT3

  • Level 10 Member
  • *****
  • Posts: 2254
Re: DCS-5222L Ping But No Connect
« Reply #3 on: December 11, 2013, 09:27:33 AM »

Is this even your camera?

I don't know which ports you used.

Run a scanner to find the http or http port.


web http traffic not operational at all (no response).
I would like to login to the FW as the next step.
I need the telnet and/or ssh port#, login user name and login password info so that I
can log in to the Linux FW and do a reboot command to recover control of the camera.
The camera is in a remote unmanned location so there is nobody to power it
off/on or do a paper-clip reset. Need to do a remote telnet and/or ssh login into the
FW Linux level to do a reboot command (Linux shutdown/restart). I am hoping this
will clear up the hang issue.
Thanks for the help! John
Logged

kallunkija

  • Level 1 Member
  • *
  • Posts: 7
Re: DCS-5222L Ping But No Connect
« Reply #4 on: December 11, 2013, 09:59:54 AM »

This is my security camera on a remote property that I own. Hence my concern that it is down.
The camera had been working ok using the D-Link D-ViewCam local LAN PC utility or via
over-the-internet mydlink web interface for 45 days after install.
It now needs a reboot I would guess to bring it back working.
So how do I login (telnet or ssh) so that I can do that Linux reboot?
I cannot find any docs on what port, name and password to use to login as telnet and/or ssh client.
I have found these ports listening at this camera IP address:
80     http
443   https
554   rtsp
7777 ?
And a ping to the camera returns the echo packet ok,
so its clear it is still running Linux and the processes.
Thanks,
John
Logged

kallunkija

  • Level 1 Member
  • *
  • Posts: 7
Re: DCS-5222L Ping But No Connect
« Reply #5 on: December 11, 2013, 11:28:09 AM »

Here is VLC debug log from attempts to access camera stream.
[004c4768] logger interface: VLC media player - 2.0.5 Twoflower
[004c4768] logger interface: Copyright © 1996-2012 VLC authors and VideoLAN
[004c4768] logger interface:
Warning: if you cannot access the GUI anymore, open a command-line window, go to the directory where you installed VLC and run "vlc -I qt"
[004c4768] logger interface: using logger.
[0360c228] live555 demux error: Failed to connect with rtsp://admin:01xtrn@192.168.0.105:554/play2.sdp
[035c8458] main access error: cannot resolve admin port 1 : No such host is known.
[035c8458] access_realrtsp access error: cannot connect to admin:1
[0360c228] live555 demux error: Failed to connect with rtsp://admin:01xtrn@192.168.0.105:554/play2.sdp
[035c8458] main access error: cannot resolve admin port 1 : No such host is known.
[035c8458] access_realrtsp access error: cannot connect to admin:1
[04899560] main input error: open of `rtsp://admin:01xtrn@192.168.0.105:554/play2.sdp' failed
[0360c228] live555 demux error: Failed to connect with rtsp://192.168.0.105:554/play1.sdp
[0360c0b8] live555 demux error: Failed to connect with rtsp://admin:01xtrn@192.168.0.105:554/play1.sdp
[035c8458] main access error: cannot resolve admin port 1 : No such host is known.
[035c8458] access_realrtsp access error: cannot connect to admin:1
[04898c58] main input error: open of `rtsp://admin:01xtrn@192.168.0.105:554/play1.sdp' failed
[0360c0b8] main demux error: cannot resolve 192.168.0.105/play1.sdp port 5004 : No such host is known.
[04898d68] main input error: open of `rtp://admin:01xtrn@192.168.0.105/play1.sdp' failed
[0360c0b8] main demux error: cannot resolve 192.168.0.105/play1.sdp port 5004 : No such host is known.
[04898d68] main input error: open of `rtp://admin:01xtrn@192.168.0.105/play1.sdp' failed
[0360c0b8] live555 demux error: Failed to connect with rtsp://192.168.0.105/play1.sdp
[0360c170] live555 demux error: Failed to connect with rtsp://192.168.0.105/play3.sdp
[0360c0b8] live555 demux error: Failed to connect with rtsp://192.168.0.105/play4.sdp
[0360b1a0] live555 demux error: Failed to connect with rtsp://admin@192.168.0.105/play4.sdp
[035c8458] main access error: cannot resolve admin@192.168.0.105 port 554 : A non-recoverable error occurred during a database lookup.
[035c8458] access_realrtsp access error: cannot connect to admin@192.168.0.105:554
[048993c8] main input error: open of `rtsp://admin@192.168.0.105/play4.sdp' failed
[0360b1a0] live555 demux error: Failed to connect with rtsp://@192.168.0.105/play4.sdp
[035c8458] main access error: cannot resolve @192.168.0.105 port 554 : A non-recoverable error occurred during a database lookup.
[035c8458] access_realrtsp access error: cannot connect to @192.168.0.105:554
[0364b888] main input error: open of `rtsp://@192.168.0.105/play4.sdp' failed
[0360b1a0] live555 demux error: Failed to connect with rtsp://192.168.0.105/play2.sdp
Logged

Acumen

  • Level 2 Member
  • **
  • Posts: 28
Re: DCS-5222L Ping But No Connect
« Reply #6 on: December 15, 2013, 08:32:35 AM »

I had/have this problem too. A power cycle was/is the only solution as far as I know.

At my cam it was caused by a full SD card. Full as in it reached the "Keep Free Space" limit.
I believe it is a bug in Firmware v1.11, but am not sure if it was already there before.
Logged

kallunkija

  • Level 1 Member
  • *
  • Posts: 7
Re: DCS-5222L Ping But No Connect
« Reply #7 on: April 12, 2014, 02:29:32 AM »

Yes, I suppose the camera software can get hung up for any number of reasons.
(My SD is not at the SD Keep level.)
Thus Dlink should at least let us know how we can remotely log into the camera
at the Linux level to do a "reboot" command.
So how do I login (telnet or ssh) so that I can do that Linux reboot?
I cannot find any docs on what port, name and password to use to do a
maintenance login as telnet and/or ssh client.
I have found these ports listening at this camera IP address:
80     http
443   https
554   rtsp
no ssh port?
Logged

Popovice

  • Level 2 Member
  • **
  • Posts: 51
Re: DCS-5222L Ping But No Connect
« Reply #8 on: April 12, 2014, 07:24:41 AM »

Wouldn't it be simplest just to add a low cost timer for regular power cycling of the camera (e.g. once per day)? I have also a camera installed very far away (in a different country) and this works fine at least for me. I installed my camera in March last year and was able to monitor the site for the whole year with this solution. Sometimes the camera hung up, but next day it was operational again, because the power cycling was configured for every night at 2AM.
Logged