I am looking to incorporate the launching of Absolute Telnet from a web server. What I am currently doing is passing an ASCII paramater file to our current telnet client and it connects to the specified host. These ASCII files are built as customer records on the web server are updated. If I had Absoulte Telnet connection files downloaded from the web server to connect it works fine, but I dont want these files to have to be updated manually. Can you pass command line paramaters to the AbsoulteTelnet.exe program to tell it to connect to a specific system via dialup, or IP, passing phone numbers or ip addresses?
To give you an idea as to what we have now, there is an ascii file that looks somewhat like this:
DEVICE=serial
PHONE=3035551212
or
DEVICE=TCP
IP=135.30.20.10
PORT=23
... or something like that... Are there command line options to the exe, or is there a way to pass ASCII connection files into it?
[size=1][ August 09, 2002, 02:36 PM: Message edited by: Brian T. Pence ][/size]
There are only a few command line options, but I'll entertain others....
Currently, the command line can take either:
1. A Path to a .tnt file, allowing full configurability but the .tnt file is binary not ascii
2. A single hostname, connecting automatically via telnet on the default port
3. A telnet url in the form
telnet://hostname:port
If called from an embeded link in a web page, a URL of this form will cause whichever telnet client is defined as the 'default' telnet client to attempt the connection. AbsoluteTelnet prompts you to make it the default telnet client when you first run the program. If you accept, AbsoluteTelnet will handle telnet URLS when clicked from the browser. But, even if AbsoluteTelnet is not the default telnet client, you can still pass these URLs to it on the command line.
Will any of these work for you? Only method one supports connection via something other than telnet.
It would be nice to be able to say whether I want telnet, ssh, or dialup somehow....
/s /i 125.23.23.12 /p 22 for ssh?!?!
/d /n 3035551212 /b 56000 for 56k dialup??
/t /i 125.23.23.12 /p 23 for telnet
Thats kind of what I had in mind....
as a bare minimum, if AbsoluteTelnet when launched with a FQDN or an IP address (as you mentioned in #2 above) that it would try telnet first, and then try ssh if it cant use telnet. What about something like that? That would probably address my telnet/ssh issues, but not my dialup issues.
whatcha think?
