I'm writing a program using Rebex Terminal Emulation to login to devices and automatically download the configuration files. The program makes extensive use of the scripting.DetectPromt() and scripting.ReadUntilPrompt() methods. I haven't had any problems with Cisco, Brocade and Palo Alto devices but with JunOS devices it has some strange behaviors. If I am in edit mode on these devices and issue a DetectPrompt it continuously cycles through that command until I hard quit the application, almost as if I was holding down the enter key. If I use the scripting.Prompt = ">" to manually tell it what prompt to expect and then issue a command such as "show configuration" followed by a "ReadUntilPrompt" it runs the command and then freezes because it never detects the prompt. It may have to do with the fact that the JunOS prompt is three lines long. An example is:
(blank line)
{master:0}
user>
I think this is somehow confusing the control's ability to detect the prompt.
Has anyone else seen this behavior?