[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1723.0. "Pathworks access for some users lost after IAS V2.0 removal" by LGP30::FLEISCHER (without vision the people perish (DTN 381-0426 ZKO1-1)) Tue Jan 28 1997 16:58

        Could the removal of IAS V2.0 (Internet AlphaServer,
        including tcp wrapper) affect the operation of an installed
        Pathworks For Digital UNIX Advanced Server (V6.1 ECO1)?

        Certain Pathworks For Digital UNIX Advanced Server (V6.0
        ECO1) users can no longer connect to their shares after
        removing IAS V2.0 -- but other users can connect.

        I admit to being woefully inexperienced in managing
        Pathworks, but I have made no changes lately.  There appear
        to be two main differences between the users that can access
        the server and the users that can't.  First, the users that
        can are using NT Workstation, the users that can't are using
        Windows 95.  Second, the users that can access use accounts
        that were established a year ago;  the users that can't use
        accounts that were set up earlier this month.

        Thanks for any suggestions,
        Bob

        [Also being asked in GYRO::INTERNET_SERVER Note 203.]
T.RTitleUserPersonal
Name
DateLines
1723.1dropping core files all over, tooLGP30::FLEISCHERwithout vision the people perish (DTN 381-0426 ZKO1-1)Wed Jan 29 1997 01:0918
re Note 1723.0 by LGP30::FLEISCHER:

>         Certain Pathworks For Digital UNIX Advanced Server (V6.1
>         ECO1) users can no longer connect to their shares after
>         removing IAS V2.0 -- but other users can connect.
  
        Some more data points:

        I'm getting core files deposited in various places at the
        time of attempted, and failing, PATHWORKS access. They appear
        to be from lmx.srv.

        Prior to the removal of IAS V2.0 (see .0), I was able to use
        the NT User Manager and Server Manager tools -- now I get
        either "access is denied" or sometimes other errors.
        Where do I start looking?

        Bob
1723.2elfread systemLGP30::FLEISCHERwithout vision the people perish (DTN 381-0426 ZKO1-1)Wed Jan 29 1997 01:30102
        In case it helps,  the following is the last 100 lines of
        output from elfread -od system:

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6060                
	TIME:     4:17:28PM           SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6060                
	TIME:     6:53:12PM           SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6060                
	TIME:     6:53:15PM           SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6060                
	TIME:     6:54:15PM           SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6060                
	TIME:     6:54:33PM           SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6060                
	TIME:     6:54:35PM           SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6280                
	TIME:     6:55:13PM           SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6280:   An illegal SMB was received from TECOFC1_01501.
  The SMB is the data.

DATA:	FF 53 4D 42 25 00 00 00 00 08 00 00 00 00 00 00 .SMB%...........
	00 00 00 00 00 00 00 00 0B 00 DD 05 03 80 00 00 ................
	0E 1B 00 00 00 08 00 F8 7F 00 00 00 00 00 00 00 ................
	00 00 00 1B                                     ....
	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 8033                
	TIME:     7:28:54PM           SOURCE:   BROWSER             
	USER:     N/A                 TYPE:     Information         
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: The browser has forced an election on network /dev/streams/knbtcpd because a master browser was stopped.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/28/97             EVENT ID: 6005                
	TIME:     7:36:38PM           SOURCE:   Eventlog            
	USER:     N/A                 TYPE:     Information         
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: The Event log service was started.

DATA:	
--------------------------------------------------------------------------------
	DATE:     1/29/97             EVENT ID: 6060                
	TIME:     12:39:59AM          SOURCE:   SERVER              
	USER:     N/A                 TYPE:     Warning             
	COMPUTER: TECOFC1             CATEGORY: None                

DESCRIPTION: ASU6060:   An Advanced Server for UNIX Systems process unexpectedly terminated.

DATA:	

1723.3core dumps at willLGP30::FLEISCHERwithout vision the people perish (DTN 381-0426 ZKO1-1)Thu Jan 30 1997 19:3213
        Well, I found one relatively easy way to cause core dumps on
        the server -- try to connect to my server's domain with
        srvmgr or usrmgr when my session is already connected as a
        non-admin user.

        Does anyone suggest that I just re-install (and, if so, any
        special procedure)?

        Does anyone want to look at the system (in ZKO) before I blow
        away this weird problem (or is that wishful thinking that
        it'll be gone)?

        Bob
1723.4"acladm -C" fixes some problems, still drops "core"LGP30::FLEISCHERwithout vision the people perish (DTN 381-0426 ZKO1-1)Fri Jan 31 1997 15:3313
        Well, the problem seems to have gone away after running the
        "acladm -C" command -- although it didn't appear to report
        any errors.

        (Are the ACLs that acladm manages UNIX V4 ACLs, or an ACL
        domain separate to the PATHWORKS server?  Is there any likely
        way that ACLs could have been damaged by the removal of an
        unrelated product?)

        I still got a core file from lmx.srv today, even after things
        started working.

        Bob