Harry, You can also have WUG send the <CR> and <LF> as decimal values in the form: %nnn%nnn I think it is %013%010 I'd have to find my ASCII chart...yep, that is correct.
Try adding one at the end of what you have now to send the <CR> that it seems to need. Here is a url for that ASCII chart, in case you need or want it: http://www.asciitable.com/ Dan Donnelly ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 15, 2004 12:35 PM Subject: Re: [WhatsUp Forum] Telneting to a Unix workstation.. WUG script > > Thanks for your suggestions Guys... however I am still not successful. > Performing a snoop, I still see that the Sun workstation is still waiting > on a CR. > > ugh... > > Harry > ----- Original Message ----- From: "Daniel Donnelly" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 14, 2004 12:03 PM Subject: Re: [WhatsUp Forum] Telneting to a Unix workstation.. WUG script > Jason is correct, use both! The system may indeed be waiting for the > sequence to be completed, only when both the <CR>& <LF> come in. In > your case, the <CR> is missing and it is likely the system considers > that an invalid (incomplete? bad syntax?) command line. > > In WhatsUp Gold (and probably many other applications): > \r = Carriage Return <CR> > \n = Newline <LF> (or Line Feed, depending on your terminology) > > Many systems/protocols require both a <CR> and <LF> before accepting > the command as complete. I've even seen systems badly affected (not > work) when the order was reversed to <LF><CR>. Once had to tell a > programmer to change the order and he moaned and groaned saying it > should not matter (but RFCs often say it does, in this case it was an > email client application), but once it was changed to the "correct > order", things worked perfectly. > > My suggestion is that you make it a habit to send both (and in the > specified order!) even if the system responds with just one of the > pair. If you don't, you will likely go down this painful path again! > > Daniel Donnelly > > ----- Original Message ----- > From: "Jason Dennis" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, October 14, 2004 9:13 AM > Subject: Re: [WhatsUp Forum] Telneting to a Unix workstation.. WUG > script > > > > Try using \r\n in combination - here is a snippet from a check we do > > against a Solaris 9 machine... > > > > Line000=Send=GET /whatsup HTTP/1.0\r\n\r\n > > > > -Jason > > > > > > On Thu, 14 Oct 2004 08:26:40 -0400, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > > > > > Actually did some further investigation last night, and discovered > > > what the issue might be. It seems that everytime I do a "Send=userid\n", > > > the unix server does not recognize /n as a new line value. The Sun server > > > behaves as if it is still waiting for a "CR" to be sent and thus never even > > > sends over a Password prompt. > > > > > > Anyone know what the value for a carriage return might be for a > > > > Sun Server? I know it is \n for unix, and \r for almost everything else.. > > > but \n is not working on any of my Sun machines. > > > > > > The reason for my doing this quite simple. We run Sybase on Sun > > > servers,and I need to login to Sybase to verify database consistency. > > > > > > Thanks, > > > - Harry > > > Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
