command can run success in bash/cmd directly via RDP, but fail to run via Putty

4 posts / 0 new
Last post
Anonymous
command can run success in bash/cmd directly via RDP, but fail to run via Putty

I have a vbs script in a windows 2008 server which will call the "ADODB.Connection".

This script can run successfully via the copssh bash and copssh cmd directly if I login via RDP and open the application.

However if I login the copssh via SSH putty, and run the script excatly the same,  there is error, showing "The Specified module could not be found.". According to the detail, it shows the script line below is having issue:

Set ADOconn = CreateObject("ADODB.Connection")

The copssh I am using is v4.9.4 and the only similar question in Forum is below and it's out of date

https://www.itefix.net/content/copssh-64bit-architecture-will-not-run-ad...

I suspect there is some persimission issue between the bash in the server directly and the bash via putty.  How can I check for this and anyone else have the similar issue ?

Thank you.

itefix
Offline
Last seen: 22 hours 56 min ago
Joined: 01.05.2008 - 21:33
Try to run the script via cmd

Try to run the script via cmd shell: cmd /c script-name. If it is about to establish some network based communication, your service must be run by a domain based service account.

Anonymous
It's still not working

Thanks for the advise, unfortunately it' still not working, same error was present even if I use the cmd /c in front :(

The openssh service in the windows server is already using the account with domain admin access. The same command is able to run if I use the bash inside the copssh directly from the windows RDP.

I tried to compare the environment value of the bash inside copssh and bash via ssh putty, the value from the putty is much more less than the value from the bash in copssh. But I don't know if it's the issue.

I don't quite understand the difference between the bash inside copssh and the bash  via ssh putty, they are all supposed to use the cygwin inside the copssh with the same permission,  right ?

Anymore suggestion ?  Thank you very much.
 

itefix
Offline
Last seen: 22 hours 56 min ago
Joined: 01.05.2008 - 21:33
 

 

PATH in a remote bash session is limited to bin and standard Windows system directories. You can change it by updating bash startup file in etc directory.