Very Computer

We're looking to replace an old Novell NACS/NASI comm. server with a
present day solution, one that's preferably Windows-based (ie. no DOS
TSR's required, drivers are all Windows .DLL based) and works over NetWare
3.12.

For those of you who have deployed a comm. server solution on your
environment, what are your experiences and recommendations?  This will
serve primarily as a dial-out (I doubt if there will be any dial-in)
through system, for access to online systems and hosts (ie. BBS, etc.) via
28.8K modems, and using Procomm Plus for Windows.  

I understand that the two components needed are separated; software and
hardware.  For the former, is INT14 the way to go?

Thanks in advance,

--
  David Tay               http://www.taysystems.com/pub/tsr/tsr.html

  3554 Chain Bridge Road, Suite 100           CompuServe: 74213,2471
  Fairfax, VA 22030-2709, USA  TEL.(703)760-9022 / FAX (703)893-1154

Kevin Marshall

Information Systems Coordinator
Hessian, McKasy & Soderberg, PA
Minneapolis, MN  USA

: >
: >We're looking to replace an old Novell NACS/NASI comm. server with a
: >present day solution, one that's preferably Windows-based (ie. no DOS
: >TSR's required, drivers are all Windows .DLL based) and works over NetWare
: >3.12.

: FWIW - We've installed within the last 3-4 months a NetWare Connect 2 server
: and have had quite satisfactory dial out performance.  We use it mostly for
: dialing out to online services (Westlaw, Lexis/Nexis, Compuserve) as well as
: to our ISP for net access.  Installed NWC2 on a clone pc (P75) running NW4.1
: runtime.  I'd like to tell you more but was installed mostly by consultants
: and has run nearly transparently since then.  Only SNAFUs in dial-in processes
:  which are mostly due to old remote control software and hardware.  Also can't
: comment on costs because I was more interested in smooth integration with the
: rest of my NW environment.  General experience - very positive.

NWC2 works quite well under 3.12. The win2ncs drivers are all windows
based and there is an upgrade available that even works with windows
95's mapi drivers. Dialing in through ppp is a no-brainer with 95
also (and I presume, though haven't tested, any win31 ppp software.)

Joe

Quote:>We're looking to replace an old Novell NACS/NASI comm. server with a
>present day solution, one that's preferably Windows-based (ie. no DOS
>TSR's required, drivers are all Windows .DLL based) and works over NetWare
>3.12.
>For those of you who have deployed a comm. server solution on your
>environment, what are your experiences and recommendations?  This will
>serve primarily as a dial-out (I doubt if there will be any dial-in)
>through system, for access to online systems and hosts (ie. BBS, etc.) via
>28.8K modems, and using Procomm Plus for Windows.  
>I understand that the two components needed are separated; software and
>hardware.  For the former, is INT14 the way to go?

Novell released a free NASI redirector for Windows (winncs) which does
not require INT 14 to access a Netware Connect modem from a
workstation.  winncs allows any Windows application to access a
Netware Connect modem .  The only requirement is that your
workstations must have 8MB of RAM (6 works but not recommended).

We use our Netware Connect box for dialing out under Procomm,
Terminal, Trumpet Winsock for dial-up PPP internet access, and procomm
for DOS.

Quote:>We're looking to replace an old Novell NACS/NASI comm. server with a
>present day solution, one that's preferably Windows-based (ie. no DOS
>TSR's required, drivers are all Windows .DLL based) and works over NetWare
>3.12.

 ------------------------------------------------------------


| Bausch & Lomb Canada Inc.         |                        |
 ------------------------------------------------------------