Re: Wardialing - Odd Results

["Champ Clark [Vistech]" <champ () bundy vistech net>]

On Tue, Jul 26, 2005 at 11:57:24AM -0500, John R. Dennison wrote:
> On Fri, Jul 22, 2005 at 09:43:32AM -0700, Atom Powers wrote:
> > I've seen this if the data rate for the system you are dialing in to and 
> > the program you are using are not in synch. For instance, if the system 
> > you are dialing to is 9600bps and you have your hyperterminal set to 

>       Any mis-configured serial port settings (baud, parity, data
>       bits, stop bits) can cause this behaviour.
>
>       In /general/, the hyperterminal default settings of 8/N/1 
>       should work in most, but not all cases; some older mainframe

        Another thing I would say is to start low and work your way up.
That is,  dial in at 300/1200 bps.  Some strange embedded systems use
lower rates.  Also,  play with your parity/stop bit setting.  8N1
is command,  but 7E1 is totally on common.   Another type,  on connecting
you might want to send a couple of characters instead of simply waiting
for the remote system to respond.  As was pointed out,  older mainframes
use such settions and X.25 PAD sometimes do as well.

        
-- 

Champ Clark III    |   Vistech Communications,Inc.   |    850-942-0388 x 101
                         http://www.vistech.net

GPG Key ID: 58A2A58F
Key fingerprint = 7734 2A1C 007D 581E BDF7  6AD5 0F1F 655F 58A2 A58F
If it wasn't for C, we'd be using BASI, PASAL and OBOL.

Attachment: _bin
Description: