From: kbs@ccr-p6.ccr.jussieu.fr (An OCR-IP fan)
Newsgroups: bit.listserv.novell,comp.sys.novell
Subject: [SUMMARY]:NW31,WIN31,MAC,PRINTING 1/2
Date: 26 Sep 92 21:37:57 GMT
Organization: Universites P. & M. Curie / D. Diderot


This are the mails I received after my posting concerning
problems I had on NW3.11 and:
- the HP III printing garbage: I've installed the patch
today (ie pserver 1.22) and it seems to work okay. Again,
I think it needs some more time to make sure it really
does work so from now....finger cross!
- UNIX, MAC connections: see below;
- Windows in general: see the post concerning Windows tips.

Thanx all again and Vive l'Europe 8)

=====================================================================
From sean@zippy.nimh.nih.gov Fri Sep 18 23:24:36 1992

>2- When I use XMSNETX, the station goes very very slow
>compare with NETX. Normal?

        Nope, not normal.  Can't really make any suggestions without
knowing your configuration of the PC, though.


>It seems that working under Windows is fairly secure
>but we still have some unknown crashes, few though.

        Join the club...Windows hates networks...

>3- We have an SCO Unix server. I'd like to connect it
>on the net.
>Is putting TCP/IP on the server and binding the ethernet
>card for use with ipx and tcp/ip enough? Obviously
>I'll have to use the ODI drivers on the workstations
>instead of ipx?
>But what should I do on the Unix server to connect it
>to the net?

        Depends what you wanna do:

        1) If you want the Unix box to be able to access the Novell files:

        Get Netware NFS ($4,900), and you can mount the Novell's drives on
your                                                                       
                                           Unix box.

        2) If some of your PC's want access to the UNIX box, then get
Novell TCP/IP and load it up on the Novell server.  You can then bind it to
your existing card.  Most of the good cards allow you to do multiple binds
to the card each using a different protocol.  Thus, you can run different
protocols with only one card.  As for the client PC's, those that want
access to the SCO Server get the ODI drivers, those that don't need UNIX
access can continue to use the IPX/SPX drivers.
 
>4- Last but not least, we're gonna have some Macs
>to install and I'd like to know which one of the
>below solutions is the best:
>
>       -putting an appletalk card on the server
>       and then connect the macs via localtalk
>       (eg. Dayna Localtalk ethernet card for PC)

        Localtalk is incredibly slow.

>       - putting an ethernet card on each Mac and
>       connect directly to the net
>       (eg. Dayna ethernet card for Mac)

        Given the cost (always coming down) of ethernet cards (I use
Asante, but Dayna are just as good, I suppose), I'd go with this.  You're
Mac users will be much happier with this option. 

>Also I got an info that IDE DRIVE were not recognized
>by Novell. I mean that the fact those drives operate
>in a slave-master mode and it will cause problems
>when you're using more than on a server as
>Netware do not manage this master-slave mode. Any follow-ups?

        There were a few "bad" IDE disk drivers shipped by Novell, but they
seem to be fine now.  There are hundreds of people using them everyday in
their servers.  

Good luck...

Sean
Systems Analyst - NIH
sean@zippy.nimh.nih.gov
----------------------------------------------------------------------
From @vm.uoguelph.ca:GBOS@ccs.uoguelph.ca Sat Sep 19 00:06:06 1992

>Hi Novellovers!
>
>In our company we have installed a Netware 3.11
>and I was getting a few annoying problems:
>
>1- Sometimes, but it seems too much for the users,
>the HP III net printer coonected on the server is
>printing garbage. The first page is always blank with
>a first line of ascii characters, and the next page
>is the actual document but with modifications (erased
>characters, lines..)
>At first, i thought it was the printer RAM. So now
>we have 2 meg on the HP, but it still does it
>and actually seemed to go worst!
>It does it when I use Works and WordPerfect (all under
>Windows) and with Word 5.0 but strangely not Windows Write.
>Even after shutting the printer to clear its memory the
>problem comes back.

Usually this is a timeout problem on the CAPTURE statement.
Try using CAPTURE L=1 J=WHATEVER TI=60
(as an example)

>Is having one printer queue a cause? I doubt though.
>
>2- When I use XMSNETX, the station goes very very slow
>compare with NETX. Normal?
>
Pretty well.  I like using something else to manage memory, eg HIMEM.SYS
and then use LOADHI NETX  to start the program instead of XMSNETX.
>
>It seems that working under Windows is fairly secure
>but we still have some unknown crashes, few though.
>
... stuff deleted...
>
>
>Also I got an info that IDE DRIVE were not recognized
>by Novell. I mean that the fact those drives operate
>in a slave-master mode and it will cause problems
>when you're using more than on a server as
>Netware do not manage this master-slave mode. Any follow-ups?
>
Most IDE drives work quite well with the ISADISK driver.  I don't have
any experience with an IDE driver.

>Thanks for the ones who took time to read this 8)
>And even more thanks to the ones who answer it!
>
Vouz etes bienvenu :-)
>Au revoir.
>--
HTH  Gerrit
--- S - h - o - r - t -   - S - i - g - n - a - t - u - r - e - : - ) ---
Gerrit Bos  Systems Analyst, Data Comm, Comp & Comm Services, U of Guelph
            Guelph ON Canada N1G 2W1 (519)824-4120x3489 Fax:(519)763-1620
-----------------------------------------------------------------------
From @ua1vm.ua.edu:JFORD@seebeck2.us.ua.edu Fri Sep 18 20:08:20 1992

>1- Sometimes, but it seems too much for the users,
>the HP III net printer coonected on the server is
>printing garbage. The first page is always blank with
>a first line of ascii characters, and the next page
>is the actual document but with modifications (erased
>characters, lines..)

Make sure you are using ???NET? v3.26 and IPX v3.11, plus the newer
PSERVER stuff.

>2- When I use XMSNETX, the station goes very very slow
>compare with NETX. Normal?

No.  What flavor of XMSNETX?

>3- We have an SCO Unix server. I'd like to connect it
>on the net.
>Is putting TCP/IP on the server and binding the ethernet
>card for use with ipx and tcp/ip enough? Obviously

Yes.  You will have to give the card an IP address.

>I'll have to use the ODI drivers on the workstations
>instead of ipx?

ODI with ODIPKT shim, or IPX genned for Packet Drivers.

>But what should I do on the Unix server to connect it
>to the net?

Configure/Start the TCPIP daemons (look in /etc/rc.tcpip or whatever).
You will have to give your Unix box an IP address.

>4- Last but not least, we're gonna have some Macs
>to install and I'd like to know which one of the
>below solutions is the best:
>
>    -putting an appletalk card on the server
>    and then connect the macs via localtalk
>    (eg. Dayna Localtalk ethernet card for PC)

No.  You are limiting everything on the Mac side to LocalTalk speeds (about
256K?).  Ethernet runs at 10MB.........

>    - putting an ethernet card on each Mac and
>    connect directly to the net

IMOHO, would be best way to go about it.
----------
James Ford - Consultant II, Seebeck Computer Center
             jford@seebeck.ua.edu, jford@risc.ua.edu
             The University of Alabama (in Tuscaloosa, Alabama)
----------------------------------------------------------------------
From rod@trapper.nwc.whecn.edu Fri Sep 18 16:41:58 1992

MACINTOSH ON NOVELL
     Ethernet is considerably faster than appletalk, so you would be better offto put ethernet cards at the stations and not appletalk in the server.  We have20 Macs on a 250 user Novell 3.11 system.  All that was needed was a network
card for each mac (Asante) and Novell for Mac 3.011 (NOT 3.0).  After that we
just hung the Macs on the ethernet just like a normal PC.  We did have to kill the notify da on the mac because it wanted to poll the Novell server about 
every second or so.  We currently are having a sporadic problem with connec-
tions not releasing, but I think it will be solvable.

WINDOWS
     We use windows 3.1 and have no problems printing from WP or Write to the
network (HPIII's).  In WordPerfect, make sure you use the windows print driver
not the WP driver.  The WP driver caused some random problems for us.  If you
are still using 3.0 windows, I strongly encourage you to upgrade, as it will
save you time in the long run.

UNIX boxes
     We haven't used the ODI workstation software yet. Currently we speak to
our unix machines with FTP compatible packet drivers (racial interlan cards anddrivers, BYU's IPXPAC, and NCSA telnet 2.3)  This combination has been very 
successful for us and seems simpler than the ODI setup.  Most net cards should
have a packet driver, if not then you can find the drivers by anonymous ftp.
The packet driver allows simultanious access to novell and TCPIP by establish-
ing a software socket for IPXPAC and Telnet to talk to rather than direct to
the hardware.  The side benefit is that excluding the packet driver, all the
software is hardware independent since it no longer talks to the card directly.SCO
     I believe that the TCPIP support package is an addon package that must be
purchased from SCO. 

                                        Good luck and don't blame me if it
                                        doesn't work.

                                        Rod Marten, Systems tech
                                        Northwest College.
======================================================================
-- 
=============================================================================
Laboratoire d'Electrochimie - Universite Paris 7  |Khac Binh Su
4, place Jussieu, Tour 44/45, 75005 PARIS. FRANCE |e-mail: kbs@ccr.jussieu.fr
=============================================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU