Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) completely boggled by modem callback
Kevin Smith wrote:
>
>>Modem callback. Nothing in the documentation prepared us for the
>>apparent fact that it just plain doesn't do it. (Except if the
>>caller is running something called Maxlink Pro under Windows 3.11.
>
>Callback from the MAX to the client after authentication ? Yes it does
>do that....I don't see why MaxLink would be needed to support it.
PMJI, but I can't imagine that Matt C is the only one who's
underwhelmed by callback support in the MAX. We found to our
disappointment that terminal server callback is impossible. Ditto for
SLIP, although the latter is less important now that CBCP seems around
the corner.
On the topic of Maxlink: MaxLink Pro / 3.11 as packaged today is
seriously flawed. It's some 9 megabytes of 1994-style TCP/IP services
--- and the only reason to install it is callback! It doesn't allow use
of the MS-TCP stack, which means you can't get access to NT server
(there's no support for NBT).
The basic Funk ODI/PPP driver that MaxLink Pro is based on is okay (and
it's only 400kB). It can (and should) be isolated to run under MS-TCP.
At the moment, this is something that Ascend leaves for integrators and
customers to figure out -- causing lots of hair-pulling.
In general, MAX callback support for the corporate access environment
has been less than brilliant. Pretending that client support isn't part
of the remote access product doesn't help. Three cheers for the
upcoming CBCP support, though.
Thanks
-Peter
---------------------------
Peter Kleynjan
Ixonet bv
Utrecht, The Netherlands
E-mail: pkleynjan@ixonet.nl
URL: http://www.ixo.net
Tel: +31-30-2724379
Fax: +31-30-2715583
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>