Someone where I work has created and shared a .msi file that installs a Windows Tunnel Service that Procomm can use to connect to SSH-only devices. Once connected to the devices, I can execute the same scripts that I use on similar devices that have telnet enabled.
They also included some basic code on how to connect to the tunnel.
I have been using the Tunnel Service since about July of 2011 and seems to work okay.
The bad news is that it was provided as a .msi file, probably written in a .Net language, that I cannot share or view the code with the .exe file.
Maybe someone on the forum can reverse-engineer this Tunnel Service if I describe how I use it???
My Aspect Script that Uses the Tunnel Service:
1) Ensure the Tunnel Service is running on my PC.
Basically, it opens a DOS window, executes a command to check the running status of the Service and sends output of that command to a temp file. The script command to construct the DOS command is:
strfmt getStateCmd "sc query %s | find /n `"STATE`" > %s" serviceToCheck FNAME
The script then checks the contents of that file.
If not running, execute the DOS command "sc start tunnelServiceName", to start it.
; ensureServiceIsRunning(service)
; Returns: true - if the requested service is running.
; If not, attempt to start it.
; false - if the service could not be started.
2) Connect to the Tunnel.
dialnumber telnet "127.0.0.1"
3) Connect to the device, and do normal login processing:
; Construct the command to connect to a device.
; agSvr could be an IP or a server name.
strfmt svrConnString "connect:%s^M" agSvr
I do not know much about Tunneling so I do not know if this Tunnel Service had to be tailored to Procomm/Aspect or it is just a generic Tunnel Service that any application can use.
****************************
The Procomm GUI Application that I wrote to use this Tunnel Service (TS, from now on), provides a list of devices (Nortel, Genband, Avaya) as opposed to connecting to them from a normal connection directory. Each group of devices can only be reached through a certain group of servers (east or west coast servers). When you click on a device, an appropriate server is selected. Step 3 above, is actually connecting (SSH) to a server that will offer a DESTINATION: prompt where the script enters the actual device name. From there, normal login processing may occur.
We have other sites where where we can direct SSH to a device. Since telnet is getting disabled in more and more of our devices, I really need to test a script soon that can use the tunnel for direct SSHing.
...it would be ideal if this was a login script that could be used with my existing connection directories.
They also included some basic code on how to connect to the tunnel.
I have been using the Tunnel Service since about July of 2011 and seems to work okay.
The bad news is that it was provided as a .msi file, probably written in a .Net language, that I cannot share or view the code with the .exe file.
Maybe someone on the forum can reverse-engineer this Tunnel Service if I describe how I use it???
My Aspect Script that Uses the Tunnel Service:
1) Ensure the Tunnel Service is running on my PC.
Basically, it opens a DOS window, executes a command to check the running status of the Service and sends output of that command to a temp file. The script command to construct the DOS command is:
strfmt getStateCmd "sc query %s | find /n `"STATE`" > %s" serviceToCheck FNAME
The script then checks the contents of that file.
If not running, execute the DOS command "sc start tunnelServiceName", to start it.
; ensureServiceIsRunning(service)
; Returns: true - if the requested service is running.
; If not, attempt to start it.
; false - if the service could not be started.
2) Connect to the Tunnel.
dialnumber telnet "127.0.0.1"
3) Connect to the device, and do normal login processing:
; Construct the command to connect to a device.
; agSvr could be an IP or a server name.
strfmt svrConnString "connect:%s^M" agSvr
I do not know much about Tunneling so I do not know if this Tunnel Service had to be tailored to Procomm/Aspect or it is just a generic Tunnel Service that any application can use.
****************************
The Procomm GUI Application that I wrote to use this Tunnel Service (TS, from now on), provides a list of devices (Nortel, Genband, Avaya) as opposed to connecting to them from a normal connection directory. Each group of devices can only be reached through a certain group of servers (east or west coast servers). When you click on a device, an appropriate server is selected. Step 3 above, is actually connecting (SSH) to a server that will offer a DESTINATION: prompt where the script enters the actual device name. From there, normal login processing may occur.
We have other sites where where we can direct SSH to a device. Since telnet is getting disabled in more and more of our devices, I really need to test a script soon that can use the tunnel for direct SSHing.
...it would be ideal if this was a login script that could be used with my existing connection directories.
