[RC5] NetWare client

gindrup at okway.okstate.edu gindrup at okway.okstate.edu
Fri May 29 09:55:24 EDT 1998


     You didn't mention your address (and some mail systems strip headers 
     long before they reach the clients), so...
     From the current NetWare client build extractable file:
     [attachment   readme.nw   6341B   ASCII text]
            -- Eric Gindrup ! gindrup at okway.okstate.edu


______________________________ Reply Separator _________________________________
Subject: [RC5] NetWare client 
Author:  <rc5 at llamas.net> at SMTP
Date:    5/28/98 8:04 AM


Does anyone have installation instructions for the NetWare client?  I have just 
herited two 3.12 servers which do little more than allow logins now.  I figure t
s is even a good means to learn something about the servers...
     
You can reply directly to me if you wish.  Thanks.
     
------------
Regards,
Daniel C. Petrak
System Administrator
The FCT Group of Companies
--
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net 
rc5-digest subscribers replace rc5 with rc5-digest
     
     


-------------- next part --------------
                                                    
 RC5-DES 2.7020.403b Client for NetWare 3.11 and above
 Released 24 May 1998 by Cyrus Patel <cyp at fb14.uni-mainz.de>
                                                          
 Welcome to the new RC5-DES (Project Monarch) Client for NetWare.
 This version is a unified client for both SMP and non-SMP machines.

    1.0  Getting started
    2.0  Notes: NetWare specific issues.
    3.0  Help! 
   
    Refer to the online FAQ at
    http://www.distributed.net/FAQ/client-2.7.html
    for non-NetWare specific issues or command line and ini file options.

  NetWare 3.11 specific note:
     
    A3112.NLM is required by this version of the client. NetWare 3.11
    users who do not have this file in their SYS:/SYSTEM directory may 
    obtain it from Novell (it is part of the latest CLIB update, 
    ie LIB311.EXE (October '95)). The updates are also available from 
    http://fb14.uni-mainz.de/~rc5des/
    
 1.0  Getting started ------------------------------------------------
 
    Just copy the client into a directory of your choice and fire it up
    with LOAD [path]RC5DES.NLM   
    If you have never run the client before, it will prompt you with a
    list of options. Quit and save when done, and then reload the client.
    
    If you are not running the client offline, then you may need to
    need to configure SYS:/ETC/RESOLV.CFG. The HELP section at the end of
    this document has details.

    The client does not *require* TCPIP (ie it will run offline if TCPIP 
    is not detected), but will use it if available. The client has not 
    been tested SFTIII, although it should work fine in that environment. 
    Feedback to the porter :) <cyp at fb14.uni-mainz.de> is much appreciated.

    Please contact me at the address above if you have access to a 
    NetWare 3.11 machine and are interested in running the pre-release 
    clients at your site.
 
 2.0  Notes: ---------------------------------------------------------
 
    As mentioned above, is version of the client is for both SMP and 
    non-SMP machines; that is, it will run with one thread if running 
    on a single processor machine and will run with two blocks per 
    thread on multi-processor (or 'numcpu' is specified in rc5des.ini 
    to be greater than one) machines.

    This version of the client can also be loaded more than one time. 
    Unloading and reloading the client for executing -fetch, -flush or 
    -update is therefore no longer neccesary. 

    The following switches cause the client to use the system 
    console screen for display rather than output to its own screen:
    -fetch, -flush, -update, -benchmark, -benchmark2 and -test.

    Some users have noted that load-sensitive tasks, such as some
    file server backup applications, would not run well when the client 
    was active. This was traced to what was seen as a 'high' processor
    utilization which caused those jobs to reschedule themselves 
    because they believed the file server to be heavily loaded. 
    Beginning with version 2.7020.403, the client will, when possible, 
    insert itself into the Idle Loop (called the 'Polling Loop' on 
    NetWare 3.x) just like PSERVER does, which allows it to control 
    processor usage far more exactly than it could before. Thus, it 
    will appear as if the client was using no processing power at all.
    However, due to the added overhead, using the idle loop also brings 
    a slight loss of client performance with it and can be disabled by
    by loading the client with '-nopoll' on the command line. 

 3.0  Help: ----------------------------------------------------------

    Please report problems, suggestions to the port maintainer
    Cyrus Patel <cyp at fb14.uni-mainz.de>  Don't fret if you don't get 
    a response right away.
 
    If you need assistance regarding use or operation, post a message to 
    the mailing list at <rc5 at llamas.net> (To subscribe to the mailing list, 
    send a message to <majordomo at llamas.net> with "subscribe rc5" as the 
    message text).

    90% of the problems that are brought to my attention are network 
    related. While the trouble may not be on your end (such as when the 
    proxies are overloaded and refusing connections), here are some 
    things to  check for:

    a) Is the TCP/IP stack correctly configured?
       Your BIND statement should look *minimally* something like this: 
       BIND TCPIP TO [MLIDname] ADD=134.93.246.119 
              MASK=255.255.255.0  GATE=134.93.247.254  BCAST=134.93.247.255
        where <add>   is the legal IP address of your machine
              <mask>  is the netmask - it must agree with every other host 
                      on your network.
              <gate>  is the IP address of the gateway. Ask your 
                      network guru for the correct number. Use GATE
                      even if Novell tells you not to (such as when 
                      using RIP [Routing Information Protocol]).
              <bcast> is the IP range your machine will broadcast in.
                      Your network guru will know this too.
       Do *not* use leading zeros in IP address components (would 
       otherwise be interpreted as an octal number).
    b) Is your network interface card correctly configured?
       Does the NetWare SETting 'Maximum Physical Receive Packet Size'
       exceed the limits of the card? Try adding 
          SET Maximum Physical Receive Packet Size = 2048
       to your STARTUP.NCF. You will need to DOWN, EXIT and restart the
       server for the changes to become effective.
    c) Is your SYS:/ETC/RESOLV.CFG correctly configured?
       The contents should look *minimally* something like this: 
          domain arl.mil
          search hosts dns
          nameserver 128.63.31.4
          nameserver 128.63.5.4
       This is only an example. Your internet guru knows the correct 
       values. NOTE: THE FILE IS CALLED RESOLV.CFG (without a second 'E')
    
    Other non-network hotspots to watch out for are:
    a) If you get a startup message saying:
          Cannot find public symbol XXX
       read the NetWare 3.x specific note in section 2.



More information about the rc5 mailing list