01304 827609 info@use-ip.co.uk Find us

HikVision HWD-7108MH-G2 - cant enable SSH?

sp0ok3r

Member
Messages
14
Points
1
When trying to enable SSH by web control, it shows a error: "Device is busy" (NET_DVR_BUSY 24).

Opinions?
 
If you don't come right, you can use RClient or cURL to enable it. Let me know if you need help doing so.
 
same error again: curl: (3) URL using bad/illegal format or missing URL
 
Load the Restlet Client for Chrome I linked to above.
Skip the sign in when prompted.
Method must be PUT
URL: http://admin:xxxx@192.168.1.xx/ISAPI/System/Network/ssh
Body:
<SSH version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<enabled>true</enabled>
</SSH>

2205
 
Returned:

<ResponseStatusversion="1.0"xmlns="urn:psialliance-org">
<requestURL>/ISAPI/System/Network/ssh</requestURL>
<statusCode>2</statusCode>
<statusString>Device Busy</statusString>
<subStatusCode>deviceBusy</subStatusCode>
</ResponseStatus>

what now?
 
Good question...
Sometimes the setting will stick but needs a reboot.
Firmware up-to-date?
Check under Integration Protocol, do you have a admin level account?
2206
 
Now given this error

<userCheck>
<script />
<statusValue>401</statusValue>
<statusString>Unauthorized</statusString>
</userCheck>

didn't change anything

???
 
Strange. The 401 error might be related to the previous session and it expiring on reboot. The only other way I can think of is trying via the Hikvision SDK. You could download the SDK and compile the Remote Configuration project in Visual Studio (a chore if you don't have VS installed) or I could compile the project and post the application. Still no guarantee it will work...
 
<NetworkCap xmlns="http://www.hikvision.com/ver20/XMLSchema" version="1.0">
<script />
<isSupportWireless>false</isSupportWireless>
<isSupportWAN>false</isSupportWAN>
<isSupportPPPoE>true</isSupportPPPoE>
<isSupportBond>false</isSupportBond>
<isSupport802_1x>false</isSupport802_1x>
<isSupportNtp>true</isSupportNtp>
<isSupportFtp>false</isSupportFtp>
<isSupportUpnp>true</isSupportUpnp>
<isSupportPNP>false</isSupportPNP>
<isSupportDdns>true</isSupportDdns>
<isSupportHttps>true</isSupportHttps>
<SnmpCap><isSupport>false</isSupport>
</SnmpCap><isSupportExtNetCfg>true</isSupportExtNetCfg>
<isSupportNetPreviewStrategy>true</isSupportNetPreviewStrategy>
<isSupportEZVIZ>true</isSupportEZVIZ>
<GB28181Cap>
<isSupportGB28181Service>false</isSupportGB28181Service>
</GB28181Cap>
<VerificationCodeModification>
<verificationCodeType opt="normal,empty">normal</verificationCodeType><isSupportDeclarationURL>true</isSupportDeclarationURL>
<isSupportPrivacyPolicyURL>true</isSupportPrivacyPolicyURL>
<verificationCodeModify>true</verificationCodeModify>
<Hyperlinks>
<isSupportVerificationCodeCheck>true</isSupportVerificationCodeCheck>
</VerificationCodeModification>
<isSupportIntegrate>true</isSupportIntegrate>
<isSupportGenetec>true</isSupportGenetec>
</NetworkCap>
 
Back to curl...
Check you have WEB Authentication set to digest/basic. Then run the command again.
2217

2219


Any difference?
 
Long shot, check you don't have IP filtering enabled.
/ISAPI/System/Network/ipFilter
 
Back
Top