Xref: utzoo comp.sys.dec:3138 comp.unix.ultrix:3451
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!noose.ecn.purdue.edu!cidmac.ecn.purdue.edu!jmoore
From: jmoore@cidmac.ecn.purdue.edu (James D Moore)
Newsgroups: comp.sys.dec,comp.unix.ultrix
Subject: Re: Need help with DEC WINDOWS on DEC 3100 stations
Message-ID: <1990May3.165607.18189@ecn.purdue.edu>
Date: 3 May 90 16:56:07 GMT
References: <10193@batcomputer.tn.cornell.edu>
Sender: news@ecn.purdue.edu (USENET news)
Distribution: na
Organization: Purdue University Engineering Computer Network
Lines: 39

In article <10193@batcomputer.tn.cornell.edu> eric@geology.tn.cornell.edu writes:
>In a recent article jmoore@cimlab.ecn.purdue.edu (James D Moore) wrote:
>>The problem is that whenever a person tries to log into the
>>client [DECstation 3100] the DecWindows accepts the login and the password
>>and then seems to time out and return the login prompt. After
>>several tries (random number but usaly more than 5-6 tries)
>>it eventualy will allow a person to log into the system.
>
>We have been having the same problem on our DECstation 3100 (Ultrix 3.1,
>UWS 2.2) and it is not even running as a client but has its own system disks.
>The number of times one has to re-do the login is not usually more than two
>or three here, and at least half the time it works on the first try.

I guess more info was needed about my post. We are also runnign Ultrix 3.1
with UWS 2.2.

>
>It might be my imagination, but it seems to get worse the longer the system
>has been up (since we are trying to install new devices recently we have been
>rebooting often and the problem has been less.
>

Hmmm ...  I see a patern here .... Any ideas what to check?

>The only other variable that might be important is that we have "only" 12 MB
>of memory (hoping to get more).
>
>				++Eric Fielding
>eric@geology.tn.cornell.edu

Our system configuration is as follows :
(1) 1 Dec3100 system 16mb (2) 3 Dec3100 Stations 8mb (3) 2 RZ55 disks
(4) 1 RZ33 (?) internal (4) TK50 (5) DEC LN03R Scriptprinter not connected
yet.



Jim Moore
jmoore@cidmac.ecn.purdue.edu