> > >The PCs are all NSpire 100 mz pentiums. There are 4 ports on the Perle
> > >controller. Two of the PCs are connected to one port. One PC to another
> > >port. The other two ports are open. The 3486 will get a signon screen on
> > >any port. When the PCs can't get a signon screen, moving them to another
> > >port doesn't help. It is as if the Perle goes into a mode where it
> > >cannot recognize the twinax cards, but will see a true terminal. Does
> > >that make sense? I've even tried changing the switch settings in the
> > >emulation to see if the 400 would auto config a new device. It didn't.
> >
> > Weird.
> >
> > What does Perle say?  What kind of twinax cards?
> >
> > Sometimes twinax cables can cause problems but that would be the same for
> > the dumb terminal as well.  How about the terminators?  Twinax problems on
> > another point can cause problems elsewhere on the same twinax.
> >
> > The fact that the PC's are on different ports probably means that it's not
> > the twinax.  I'm wondering about the Perle now.
> >
> > Jerry
> The cards are IBM.
> I talked to Perle yesterday. They don't have any idea about what could
> cause this. I think I'm going to order new cables. One PC uses a twinax
> cable, the other two have twisted pair cables with baluns. Would you
> guys recommend one over the other?

You might try a powered hub if you have one laying around.

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].