Sounds like you are using TW 2.0b? correct? If so, that is your problem.
This is a known bug, upgrade to TW 2.1f at least. (If you are using 2.1f,
then this is a new one on me.)
>be no problems on the first try. Disconnecting and reconnecting with the
>same Trumpet session will not correctly detect the assigned IP address,
>however. Does anyone have any ideas?
2.0b 'remembered' the IP at times and that caused problems.
>Also, dialing in non-PPP, with a telnet/rlogin session through the portmaster
>to a host computer does not seem to be working perfectly. The text will
>lag behind what is actually happening. Sometimes it freezes entirely,
>and it takes a control character (e.g., ctrl-c, ctrl-l) to get things
I've not seen this before, I'd contact support.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566