 |  |
okay we have finally gotten it to connect to the telnet server. But it is
Re: Auto Server Setup
From: Greg McKenzie
Date: Thursday, June 8, 2000
Time: 11:26:02 am
still very SLOW.
But it logs in (slow like I said), but I cant seem to get rid of the screen
that ask for the terminal type so I put a "wait for" in with a 1 for the
response. Then I put a "wait for" to get the command prompt, with my
command string as the result.
What I get is garbage on the telecript screen for a minute (or 2) then
socket closes. Resulting in nothing being done (In the garbage it does look
like OG sent the info for the command line, but it is at that point that the
socket closes).
I even went back and put a CMD in front of the command line.
Greg
----- Original Message -----
From: "Shawn Hogan" <shawn@digitalpoint.com>
To: "Optigold ISP List" <isp-list@optigold.com>
Sent: Thursday, June 08, 2000 12:58 PM
Subject: Re: [Optigold ISP] Auto Server Setup
> Greg GDS wrote:
>
> > OK back trying to get this working again today. I installed the
Pragamasys
> > TelnetD, and it seems to be working fine, I can telnet in normally with
no
> > problems and can run the commands to add the mail box etc. with out any
> > problems. And it is pretty fast.
> >
> > BUT..... The Auto server setup for doing this is NOT working at all. I
> > still get the popup box about Telescrpt and I have copied that thing
into
> > every folder I can think of. And when you go to do a server setup it
DOES
> > connect, it DOES get the user name prompt, and the OG DOES sent that as
well
> > as the password when prompted. But that is where is all goes south.
> >
> > It looks like it does the User verification, and attempts to drop to a
> > command prompt, but as soon as it does the port is closed. And man it
takes
> > for ever, like at least a minute for the username prompt and another
minute
> > for OG to send it etc. etc.
>
> Remember that the session is case sensitive. If it's taking a minute for
any
> individual command, it's because the "wait for" portion of your script is
> timing out as it never receives it. Also, a long pause is usually cause
by
> an invalid wait for on the *next* command (compared to the one you see in
> the echo). Biggest thing to check is the case-sensitivity.
>
> As for the telsscrpt not being able to be found, flip through all auto
> server actions and make sure you don't have a rogue one set to use Command
> Line instead of telnet.
>
> - Shawn
>
> -------------------------------
> Shawn D. Hogan
> President, Digital Point Solutions
> http://www.digitalpoint.com
> (858) 452-3696
>
> ------------------------------------------
> To subscribe, unsubscribe and list archive
> please visit http://www.optigold.com/lists
> ------------------------------------------
------------------------------------------
To subscribe, unsubscribe and list archive
please visit http://www.optigold.com/lists
------------------------------------------
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696