🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.netware.misc
6 messages
6 total messages Started by Tay Systems Research Thu, 18 Jul 1996 00:00
Advice needed re: comm server.
#349
Author: Tay Systems Research
Date: Thu, 18 Jul 1996 00:00
22 lines
1777 bytes
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
  Tay Systems Research     Email: tsr@taysystems.com / dtay@juno.com
  3554 Chain Bridge Road, Suite 100           CompuServe: 74213,2471
  Fairfax, VA 22030-2709, USA  TEL.(703)760-9022 / FAX (703)893-1154
Re: Advice needed re: comm server.
#352
Author: K. Marshall
Date: Fri, 19 Jul 1996 00:00
27 lines
2150 bytes
In article <4sll4f$h9e@clarknet.clark.net>, tsr@clark.net says...
>
>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. 
>  David Tay               http://www.taysystems.com/pub/tsr/tsr.html
>  Tay Systems Research     Email: tsr@taysystems.com / dtay@juno.com
>  3554 Chain Bridge Road, Suite 100           CompuServe: 74213,2471
>  Fairfax, VA 22030-2709, USA  TEL.(703)760-9022 / FAX (703)893-1154

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.

Kevin Marshall
marshall@polaristel.net
Information Systems Coordinator
Hessian, McKasy & Soderberg, PA
Minneapolis, MN  USA
Re: Advice needed re: comm server.
#344
Author: raym
Date: Sun, 21 Jul 1996 00:00
28 lines
1916 bytes
tsr@clark.net (Tay Systems Research) wrote:

>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
>  Tay Systems Research     Email: tsr@taysystems.com / dtay@juno.com
>  3554 Chain Bridge Road, Suite 100           CompuServe: 74213,2471
>  Fairfax, VA 22030-2709, USA  TEL.(703)760-9022 / FAX (703)893-1154

INSYNC from Artisoft ( formerly ModemAssist form Synergy Solutions) is
and excellent product. It runs on Windows3.x/95. It requires no TSR.
You can have multiple modem servers and it works great on NetWare.
Re: Advice needed re: comm server.
#345
Author: Joe Julian
Date: Sun, 21 Jul 1996 00:00
25 lines
2114 bytes
K. Marshall (hmslaw@polaristel.net) wrote:
: In article <4sll4f$h9e@clarknet.clark.net>, tsr@clark.net says...
: >
: >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
Re: Advice needed re: comm server.
#346
Author: Evan Wagner
Date: Sun, 21 Jul 1996 00:00
31 lines
2098 bytes
tsr@clark.net (Tay Systems Research) wrote:

>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?

We use a Netware Connect 1.0 box (486SX-33 w/ Digiboard PC8Xem, 8MB
RAM, and 120 MB HD).  If you are only concerned about dial-out and
never see the possiblity of dialing in via PPP, I'd find a copy of
Newtare Connect 1.0

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.
Re: Advice needed re: comm server.
#347
Author: Serge Adam
Date: Mon, 22 Jul 1996 00:00
20 lines
1413 bytes
In article <4sll4f$h9e@clarknet.clark.net>,
   tsr@clark.net (Tay Systems Research) wrote:
>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. 
>




Upgrade to NetWare Connect 2.0. Nasi redirection is Windows based. Works great 
with Procomm.

 ------------------------------------------------------------
| Serge Adam                        | Serge.Adam@BAUSCH.COM  |
| Senior Technical Services Analyst | sadam@pathcom.com      |
| Bausch & Lomb Canada Inc.         |                        |
 ------------------------------------------------------------
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads