[bit.listserv.novell] Syscon Hanging.

Tim_Munro@CARLETON.CA (02/12/90)

      An  associate  of  mine  here has just set  up  his  first
   Netware  system  (ANW  2.15c).  An  interesting  problem  has
   arisen.  In syscon the functions ACCT RESTRICTIONS and  OTHER
   INFO,  and under the SUPERVISOR OPTIONS menu, options DEFAULT
   ACCT BALANCE/RESTRIC. all semm to hang the workstation. After
   the  connection  times  out you  get:  Network  Error:  error
   receiveing from network.  Abort  or Retry.  If you retry same
   result,  if  you abort you are logged out and sitting in  the
   Login  directory.  All  other  functions  in  Syson  work ok.
   ACCOUNTING has not been installed.

   Any and all suggestions welcome.

   Tim      <Tim_Munro@carleton.ca> Fax:(613) 788-4448
                                  Voice:(613) 788-3722

THOMAS@USUHS.BITNET (02/12/90)

In reply to Tim Munroe's problem regarding SYSCON hanging.

I had the same problem when I installed my LAN.  I found that I had a TSR
that was competing with SYSCON.  My problem was the order in which IPX, NET3
and Sidekick were loaded.  If you load Sidekick before IPX and NET3 SYSCON
hangs up.  If you load Sidekick after IPX and NET3 SYSCON runs just fine.

Check and see if you have a memory resident program that is causing the problem.
Load IPX and NET3 before any other memory resident routines.  SYSCON should
run just fine.

JERRY THOMAS
USUHS
THOMAS@USUHS

Tim_Munro@CARLETON.CA (02/13/90)

      Hmm, not the case here. Our 'boot disk' consists of PC-DOS v3.30
   IPX.COM and NET3.COM and that's all.  I did notice,  however,  that
   the version of NET3.COM is Rev A (as shipped with NOS Rev.C) So the
   system is as naked  as  possible,  with  only  the stuff as sent by
   novell,  with  the  one  exception of the WD8003  drivers.  All  is
   configured normally nothing  fancy and nothing special.  At first I
   though it was the auto-boot roms on the WD cards,  but this is  not
   the case. I booted normally with a floppy and the problem persists.

   Tim      <Tim_Munro@carleton.ca> Fax:(613) 788-4448
                                  Voice:(613) 788-3722

bdahlen@ZEPHYR.CAIR.DU.EDU (Robert L. Dahlen @ U. of Denver USA=) (02/13/90)

I remember somthing that happened here a while ago, it might not
solve your problem but here goes.

Somehow (????) a copy of the screen driver novell uses for its
"windowing" and colors got saved and hidden in the root directory of
a server disk that was configured for every thing to come up black
on black.  We only found it accidently using XTREE to do something
else.  I don't know how it got there but it gave the imp[ression
of SYSCON hanging.
Good Luck
Bob
-------------------------------------------------------------------
Robert L. Dahlen - Director, Information Systems & Technology
University of Denver - Denver, Colorado 80208 (303) 871-4385
INET:bdahlen@du.edu BITNET:bdahlen@ducair UUCP:ncar!dunike!bdahlen

BOMR@TRIUMFRG.BITNET (ROD NUSSBAUMER) (02/13/90)

>
>
>      An  associate  of  mine  here has just set  up  his  first
>   Netware  system  (ANW  2.15c).  An  interesting  problem  has
>   arisen.  In syscon the functions ACCT RESTRICTIONS and  OTHER
>   INFO,  and under the SUPERVISOR OPTIONS menu, options DEFAULT
>   ACCT BALANCE/RESTRIC. all semm to hang the workstation. After
>   the  connection  times  out you  get:  Network  Error:  error
>   receiveing from network.  Abort  or Retry.  If you retry same
>   result,  if  you abort you are logged out and sitting in  the
>   Login  directory.  All  other  functions  in  Syson  work ok.
>   ACCOUNTING has not been installed.
>
>   Any and all suggestions welcome.
>
>   Tim      <Tim_Munro@carleton.ca> Fax:(613) 788-4448
>                                  Voice:(613) 788-3722

        I have experienced very nearly the same problem within
        SYSCON, but in a different menu area.  I get the same symptoms
        when I try to access the OTHER INFO item in USER INFORMATION.
        For me, it isn't consistent, and seems to be worst when I
        try to access info on a user who is on a server which I am only
        ATTACHed to, rather than on the server I'm logged into.

        I am using ANW 2.15C, and trying all of this as SUPERVISOR.

        Up until now I've just ignored it, although I would like
        to resolve the matter, especially if it is indicative of
        some more serious problem.

        +------------------------------------------+
        |  Rod Nussbaumer                          |
        |  Programmer / Technologist               |
        |  TRIUMF  ---  Vancouver, BC, Canada      |
        |  (604) 222-1047                          |
        |  BITNET%"BOMR@TRIUMFER"                  |
        |  USERTRRN@mtsg.ubc.ca                    |
        +------------------------------------------+

THOMAS@USUHS.BITNET (02/13/90)

I had that problem when I first installed my Novell Software.  The problem
was a conflict between Sidekick and the IPX and NET3 TSR's.  Loading Sidekick
last resolved the problem.

I have a feeling that there are TSR's which may be causing the interference.

JERRY THOMAS

THOMAS@USUHS

mgw@RELAY.PROTEON.COM (02/13/90)

>      An  associate  of  mine  here has just set  up  his  first
>   Netware  system  (ANW  2.15c).  An  interesting  problem  has
>   arisen.  In syscon the functions ACCT RESTRICTIONS and  OTHER
>   INFO,  and under the SUPERVISOR OPTIONS menu, options DEFAULT
>   ACCT BALANCE/RESTRIC. all semm to hang the workstation. After
>   the  connection  times  out you  get:  Network  Error:  error
>   receiveing from network.  Abort  or Retry.  If you retry same
>   result,  if  you abort you are logged out and sitting in  the
>   Login  directory.  All  other  functions  in  Syson  work ok.
>   ACCOUNTING has not been installed.
>
>   Any and all suggestions welcome.
>
>>
>>       I have experienced very nearly the same problem within
>>       SYSCON, but in a different menu area.  I get the same
>>       symptoms when I try to access the OTHER INFO item in USER
>>       INFORMATION.  For me, it isn't consistent, and seems to be
>>       worst when I try to access info on a user who is on a server
>>       which I am only ATTACHed to, rather than on the server I'm
>>       logged into.
>>
>>      I am using ANW 2.15C, and trying all of this as SUPERVISOR.
>>
>>      Up until now I've just ignored it, although I would like
>>      to resolve the matter, especially if it is indicative of
>>      some more serious problem.

           This was experienced by us at Proteon Inc. as well,
           downgrading to the SYSCON supplied in 2.15 rev a solved
           it...

           Marc Washburn
           TS Engineer
           Proteon Inc.
           (508) 898-3100
           mgw@relay.proteon.com

Tim_Munro@CARLETON.CA (02/14/90)

      Thanks  to  Marc Washburn we have solved another  Rev.C  bug.  I
   rolled SYSCON back to a 2.15 Rev. A and sure enough all is fine and
   dandy.

   Tim      <Tim_Munro@carleton.ca> Fax:(613) 788-4448
                                  Voice:(613) 788-3722