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

Conference ranger::pwultrix

Title:Pathworks for ULTRIX
Notice:This conferance is not an official problem reporting channel
Moderator:RANGER::DEE
Created:Tue Feb 12 1991
Last Modified:Mon Jun 02 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1296
Total number of notes:3840

1295.0. "pwultrix,dns and dhcp ???" by VMSNET::G_OEHMS (Will the wonders never seize the day?) Tue Feb 04 1997 21:03

    Hi:
    
     Customer first reported "broken pipe" errors that I researched and
    found scattered instances of, usually related to duplicate addresses
    (decnet surely, tcp/ip suspected).  Also the reported instances seemed
    to be one-time occurrences.  Passed that info on to customer and he was
    content.
    
    Then he came back with recurrences of those errors and other info about
    his having been told to use wildcards in the dns host.rev files in
    conjunction with dhcp and the pwultrix server.  He says he was looking
    for a workaround to  deal with the PWULTRIX 1 minute time after a DNS
    name resolution fails.
    
    Below is all the information he sent me.  Can anyone make sense of this
    and advise on what he can and cannot expect in this scenario.
    
    +++++++++++++++
    Here is some of the information which I've collected.  Attached also 
         are chunks of the 2 servers' syslog (servername.log) files from
    the 
         days with problems.
         
         aspen.log attachment
         
         Aspen was the first file server to crash, BEFORE I did the DNS
    setup 
         for dhcp nodes with wildcards (like you can see from the tail end
    of 
         the following 'host.rev' file.  That's why one can see the
    straight IP 
         addresses.  I've inserted blank lines around the broken pipe
    errors.
         
         Chronology:
         - It starts the day with broken pipe errors
         - I then restart the pathworks server at 8:11am
         - Occasional broken pipe errors appear throughout the day, but
    don't 
         seem fatal to the server. 
         - there haven't been any more broken pipe errors since that day a
    week 
         ago.
    Here is some of the information which I've collected.  Attached also 
         are chunks of the 2 servers' syslog (servername.log) files from
    the 
         days with problems.
         
         aspen.log attachment
         
         Aspen was the first file server to crash, BEFORE I did the DNS
    setup 
         for dhcp nodes with wildcards (like you can see from the tail end
    of 
         the following 'host.rev' file.  That's why one can see the
    straight IP 
         addresses.  I've inserted blank lines around the broken pipe
    errors.
         
         Chronology:
         - It starts the day with broken pipe errors
         - I then restart the pathworks server at 8:11am
         - Occasional broken pipe errors appear throughout the day, but
    don't 
         seem fatal to the server. 
         - there haven't been any more broken pipe errors since that day a
    week 
         ago.
         
         lan710.log attachment
     
         LAN710 (my primary dns server, as well as pathworks file and print 
         server) had the problem AFTER I changed  the dns host.rev file to 
         use wild card dhcp entries.
         
         Chronology:
         - file server runs great all day, but stops accepting pathworks 
         connections and drops existing ones around 17:30
         - I restart the pathworks server, then plenty of broken pipe
    errors 
         appear.  I also noticed some wierd "PCSAFS130: Unable to open 
         pcsaadmd message queue - No such file or directory" errors during 
         shutdown.
         - the file server has run without noticable problems all day today
    (no 
         broken pipe error messages)
         
         note:  the hosts.rev file I have below has been modifiled slightly
    to 
         shorten the dhcp aliases so that the 'dhcpholladay.trimet.org'
    nodes 
         which show up in the lan710.log are currently 'dhcphol.trimet.org'
         
         some files:
         
         =========primary hosts.rev (dns reverse name lookup file) ======== 
         10.1.18.172.in-addr.arpa.       IN      PTR    
    switch830.trimet.org. 
         2.4.1.191.in-addr.arpa.         IN      PTR     white.trimet.org. 
          2.1.1.191.in-addr.arpa.         IN      PTR     groff.trimet.org. 
         200.70.1.191.in-addr.arpa.      IN      PTR     el1.trimet.org. 
         202.1.1.191.in-addr.arpa.       IN      PTR    
    csadmin1.trimet.org. 
         200.1.1.191.in-addr.arpa.       IN      PTR    
    helpdesk.trimet.org. 
         *.*.18.172.in-addr.arpa.        IN      PTR    
    dhcphol.trimet.org. 
         *.2.168.192.in-addr.arpa.       IN      PTR    
    dhcpsun.trimet.org. 
         *.4.168.192.in-addr.arpa.       IN      PTR    
    dhcphaw.trimet.org. 
         *.6.168.192.in-addr.arpa.       IN      PTR    
    dhcphil.trimet.org. 
         *.8.168.192.in-addr.arpa.       IN      PTR    
    dhcpjef.trimet.org. 
         *.12.168.192.in-addr.arpa.      IN      PTR    
    dhcptst.trimet.org.   
         ====primary  named.boot ===================================
         ;
         ; BIND data file to boot a primary name server. 
         ;
         ; directory where all the data files are stored 
         directory       /var/dss/namedb
         ;
         ; type          domain                  source host/file 
         primary         trimet.org              hosts.db.trimet 
         primary         tri-met.org             hosts.db.tri-met 
         primary         18.172.in-addr.arpa     hosts.rev 
         primary         2.168.192.in-addr.arpa  hosts.rev 
         primary         4.168.192.in-addr.arpa  hosts.rev 
          primary         6.168.192.in-addr.arpa  hosts.rev 
         primary         8.168.192.in-addr.arpa  hosts.rev 
         primary         12.168.192.in-addr.arpa hosts.rev
         ;
         ;
         primary         0.0.127.in-addr.arpa    named.local 
         ;
         ; load the cache data last
         cache           .                       named.ca     
         
         =================  pcsamgr screen   =================
         
           S E S S I O N S
           Session Number         Node        Number of Connections
         
              39                  10.288                     1 
              40                  10.92                      3 
              48                  dhcphol.trimet.o           2 
              54                  dhcphol.trimet.o           4 
              56                  dhcphol.trimet.o           5 
              57                  dhcphol.trimet.o           5 
              60                  dhcphol.trimet.o           3 
              61                  10.666                     2 
               62                  10.273                     2 
              64                  10.600                     7 
              75                  10.787                     6 
              77                  10.639                     6 
              80                  dhcphol.trimet.o           5 
              84                  10.251                     1 
              98                  dhcphol.trimet.o           5
         
             <DELETE>       <ZOOM>         <RETURN>       <HELP>     
         ============== /usr/pcsa/lanman.ini =============== 
         lan710:{root}_/usr/pcsa> more lanman.ini
          maxsessions  =  512
          maxconnections  =  2048
          connspersession  =  25
          maxopens  =  2048
          guestacct  =  pcguest
          accptunreg  =  yes
          autodisconnect  =  0
          messagelog  =  no
          messagelogfile  =  /usr/pcsa/message.log 
          maxmessagelog  =  100000
          errorlog  =  yes
          errorlogfile  =  /usr/pcsa/error.log 
           maxerrorlog  =  100000
          auditlog  =  yes
          auditlogfile  =  /usr/pcsa/audit.log 
          maxauditlog  =  100000
          user_connection_group_access  =  readwrite 
          user_connection_other_access  =  readonly 
          guest_connection_group_access  =  readwrite 
          guest_connection_other_access  =  readwrite 
          personal_service_group_access  =  readonly 
          personal_service_other_access  =  noaccess 
          ultrixlockingenabled  =  no
          uniqueopenfiles  =  2048
          maxserverlocks  =  2048
          disablewritebehind  =  no
          disablesetdir  =  no
          inheritrootprot  =  yes             
         ================= end ============================== 
         Thanks for looking into this.
      +++++++++++++++++++++++++++++++++++++++++
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:22 localhost: 3954 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service win_word
    Jan 28 17:30:31 localhost: 4171 PCSAFS130: Starting server with 10.804
    and netbi
    os name 817
    Jan 28 17:30:31 localhost: 4171 PCSAFS130: Connect 373 Session 137 
    start on nod
    e 10.804 user pcguest for service pcsav41
    Jan 28 17:30:45 localhost: 4172 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC752
     Jan 28 17:30:45 localhost: 4172 PCSAFS130: Connect 375 Session 138 
    start on nod
    e dhcpholladay.tri user lash for service lash
    Jan 28 17:30:47 localhost: 4173 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name CD501
    Jan 28 17:30:47 localhost: 4173 PCSAFS130: Connect 376 Session 140 
    start on nod
    e dhcpholladay.tri user pcguest for service netbats
    Jan 28 17:31:30 localhost: 4163 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service ipc$
    Jan 28 17:31:35 localhost: 4074 PCSAFS130: Invalid service name from
    node lan710
     user pcguest service ipc$
    Jan 28 17:32:26 localhost: 4163 PCSAFS130: Connect 377 Session 133 
    start on nod
    e dhcpholladay.tri user phillips for service lgl
    Jan 28 17:32:58 localhost: 3902 PCSAFS130: Client dhcphillsboro.tr user
    pcguest 
    stopped connection tid 12
    Jan 28 17:32:58 localhost: 3902 PCSAFS130: Client dhcphillsboro.tr user
    pcguest 
    stopped connection tid 11
    Jan 28 17:32:58 localhost: 3902 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:33:12 localhost: 2577 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:33:26 localhost: 4177 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC8343
    Jan 28 17:33:26 localhost: 4177 PCSAFS130: Connect 11 Session 141 
    start on node
     dhcpholladay.tri user robertsb for service sn
    Jan 28 17:33:35 localhost: 4178 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC278
    Jan 28 17:33:36 localhost: 4178 PCSAFS130: Connect 12 Session 142 
    start on node
     dhcpholladay.tri user phillips for service lgl
    Jan 28 17:33:41 localhost: 4179 PCSAFS130: Starting server with
    pc8056.trimet.or
     and netbios name PC8056
    Jan 28 17:33:41 localhost: 4179 PCSAFS130: Connect 275 Session 143 
    start on nod
    e pc8056.trimet.or user pcguest for service netbats
    Jan 28 17:33:41 localhost: 4178 PCSAFS130: Connect 378 Session 142 
    start on nod
    e dhcpholladay.tri user phillips for service phillips
    Jan 28 17:33:44 localhost: 4180 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC681
    Jan 28 17:33:44 localhost: 4180 PCSAFS130: Connect 380 Session 144 
    start on nod
    e dhcpholladay.tri user pcguest for service netbats
    Jan 28 17:33:54 localhost: 4146 PCSAFS130: Connect 381 Session 110 
    start on nod
    e dhcpholladay.tri user pcguest for service netbats
    Jan 28 17:34:11 localhost: 4181 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC8343
    Jan 28 17:34:11 localhost: 4181 PCSAFS130: Connect 382 Session 145 
    start on nod
    e dhcpholladay.tri user robertsb for service sn
    Jan 28 17:34:35 localhost: 4182 telnetd: Connect from pc8056.trimet.org
    Jan 28 17:34:45 localhost: 4185 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC681
    Jan 28 17:34:46 localhost: 4185 PCSAFS130: Connect 383 Session 146 
    start on nod
    e dhcpholladay.tri user pcguest for service netbats
    Jan 28 17:34:51 localhost: 4188 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC289
    Jan 28 17:34:51 localhost: 4188 PCSAFS130: Connect 391 Session 147 
    start on nod
    e dhcpholladay.tri user pcguest for service netbats
    Jan 28 17:34:56 localhost: 4190 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC8343
    Jan 28 17:34:56 localhost: 4190 PCSAFS130: Connect 392 Session 148 
    start on nod
    e dhcpholladay.tri user robertsb for service sn
    Jan 28 17:35:47 localhost: 4206 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC289
    Jan 28 17:35:47 localhost: 4206 PCSAFS130: Connect 393 Session 149 
    start on nod
    e dhcpholladay.tri user pcguest for service netbats
    Jan 28 17:36:17 localhost: 3051 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:17 localhost: 3051 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:17 localhost: 3051 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:17 localhost: 4061 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:17 localhost: 4061 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:17 localhost: 4061 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:17 localhost: 4059 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:36:18 localhost: 319 PCSAFS130: Session with node 10.655
    terminated by
     system administrator
    Jan 28 17:36:18 localhost: 4059 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:36:18 localhost: 4059 PCSAFS130: Node 10.804 connection
    closed
    Jan 28 17:36:18 localhost: 319 PCSAFS130: Session with node 10.655
    terminated by
     system administrator
    Jan 28 17:36:18 localhost: 319 PCSAFS130: Node 10.655 connection closed
    Jan 28 17:36:18 localhost: 4055 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:18 localhost: 4055 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:18 localhost: 4055 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:19 localhost: 320 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:19 localhost: 4051 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:19 localhost: 4051 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:19 localhost: 4051 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:19 localhost: 320 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:19 localhost: 320 PCSAFS130: Node dhcpholladay.tri
    connection close
    d
    Jan 28 17:36:20 localhost: 4060 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 4060 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 4060 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:20 localhost: 4066 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 4066 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 4066 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:20 localhost: 4058 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 4058 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 4058 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:36:20 localhost: 4052 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 3047 PCSAFS130: Session with node 10.718
    terminated b
    y system administrator
    Jan 28 17:36:20 localhost: 4052 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:20 localhost: 4052 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:21 localhost: 4054 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:21 localhost: 4054 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:21 localhost: 4054 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:21 localhost: 4050 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:22 localhost: 4050 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:22 localhost: 4050 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:22 localhost: 4062 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:22 localhost: 4062 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:22 localhost: 4062 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:23 localhost: 4070 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:23 localhost: 4070 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:23 localhost: 4070 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:23 localhost: 4068 PCSAFS130: Session with node 10.789
    terminated b
    y system administrator
    Jan 28 17:36:23 localhost: 4068 PCSAFS130: Session with node 10.789
    terminated b
    y system administrator
    Jan 28 17:36:23 localhost: 4068 PCSAFS130: Node 10.789 connection
    closed
    Jan 28 17:36:23 localhost: 4056 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:23 localhost: 4074 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:23 localhost: 3089 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:23 localhost: 4074 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:23 localhost: 4074 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:23 localhost: 4071 PCSAFS130: Session with node 10.365
    terminated b
    y system administrator
    Jan 28 17:36:23 localhost: 4071 PCSAFS130: Session with node 10.365
    terminated b
    y system administrator
    Jan 28 17:36:23 localhost: 4071 PCSAFS130: Node 10.365 connection
    closed
    Jan 28 17:36:24 localhost: 4056 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:24 localhost: 4056 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:24 localhost: 4053 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:24 localhost: 4053 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:24 localhost: 4053 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:24 localhost: 4063 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:24 localhost: 4063 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:24 localhost: 4063 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:25 localhost: 4067 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4067 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4067 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:25 localhost: 346 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:25 localhost: 4049 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4073 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4049 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4049 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:25 localhost: 4073 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4073 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:25 localhost: 4083 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4083 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:25 localhost: 4083 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:26 localhost: 347 PCSAFS130: Session with node 9.623
    terminated by 
    system administrator
    Jan 28 17:36:26 localhost: 347 PCSAFS130: Session with node 9.623
    terminated by 
    system administrator
    Jan 28 17:36:26 localhost: 347 PCSAFS130: Node 9.623 connection closed
    Jan 28 17:36:26 localhost: 4064 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:26 localhost: 4078 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:26 localhost: 4064 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:26 localhost: 4064 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:26 localhost: 4078 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:26 localhost: 4078 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:26 localhost: 345 PCSAFS130: Session with node 10.633
    terminated by
     system administrator
    Jan 28 17:36:26 localhost: 345 PCSAFS130: Session with node 10.633
    terminated by
     system administrator
    Jan 28 17:36:26 localhost: 345 PCSAFS130: Node 10.633 connection closed
    Jan 28 17:36:26 localhost: 4065 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:26 localhost: 4065 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:26 localhost: 4065 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:36:27 localhost: 4082 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:27 localhost: 358 PCSAFS130: Session with node 10.774
    terminated by
     system administrator
    Jan 28 17:36:27 localhost: 4082 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:27 localhost: 4082 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:27 localhost: 3179 PCSAFS130: Session with node 10.379
    terminated b
    y system administrator
    Jan 28 17:36:27 localhost: 358 PCSAFS130: Session with node 10.774
    terminated by
     system administrator
    Jan 28 17:36:27 localhost: 358 PCSAFS130: Node 10.774 connection closed
    Jan 28 17:36:27 localhost: 344 PCSAFS130: Session with node 10.666
    terminated by
     system administrator
    Jan 28 17:36:27 localhost: 4080 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:27 localhost: 3179 PCSAFS130: Session with node 10.379
    terminated b
    y system administrator
    Jan 28 17:36:27 localhost: 3179 PCSAFS130: Node 10.379 connection
    closed
    Jan 28 17:36:27 localhost: 4080 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:27 localhost: 4080 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:27 localhost: 375 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:27 localhost: 4077 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:27 localhost: 4077 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:27 localhost: 4077 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:27 localhost: 344 PCSAFS130: Session with node 10.666
    terminated by
     system administrator
    Jan 28 17:36:27 localhost: 344 PCSAFS130: Node 10.666 connection closed
    Jan 28 17:36:28 localhost: 4093 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:28 localhost: 375 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:28 localhost: 375 PCSAFS130: Node dhcpholladay.tri
    connection close
    d
    Jan 28 17:36:28 localhost: 4093 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:28 localhost: 4093 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:28 localhost: 4090 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:28 localhost: 4090 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:28 localhost: 4090 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:28 localhost: 4069 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:28 localhost: 4069 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:28 localhost: 4069 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:28 localhost: 3211 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:28 localhost: 3187 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 3211 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 3211 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:29 localhost: 4075 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 4075 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 4075 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:29 localhost: 4099 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 4099 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 4099 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:29 localhost: 4079 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 4079 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:29 localhost: 4079 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:30 localhost: 4085 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:30 localhost: 4086 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:30 localhost: 4085 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:30 localhost: 4085 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:30 localhost: 4086 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:30 localhost: 4086 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:30 localhost: 4104 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:30 localhost: 4104 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:30 localhost: 4104 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:31 localhost: 4105 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:31 localhost: 4105 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:31 localhost: 4105 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:31 localhost: 4091 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:31 localhost: 4091 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:31 localhost: 4091 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:31 localhost: 4094 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:31 localhost: 4072 PCSAFS130: Session with node 10.507
    terminated b
    y system administrator
    Jan 28 17:36:31 localhost: 4094 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:31 localhost: 4094 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:31 localhost: 4072 PCSAFS130: Session with node 10.507
    terminated b
    y system administrator
    Jan 28 17:36:31 localhost: 4088 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:31 localhost: 4072 PCSAFS130: Node 10.507 connection
    closed
    Jan 28 17:36:31 localhost: 4088 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:32 localhost: 4088 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:32 localhost: 4089 PCSAFS130: Session with node 10.747
    terminated b
    y system administrator
    Jan 28 17:36:32 localhost: 4089 PCSAFS130: Session with node 10.747
    terminated b
    y system administrator
    Jan 28 17:36:32 localhost: 4089 PCSAFS130: Node 10.747 connection
    closed
    Jan 28 17:36:32 localhost: 4108 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:32 localhost: 4108 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:32 localhost: 4108 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:32 localhost: 4112 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:36:32 localhost: 4112 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:36:32 localhost: 4112 PCSAFS130: Node 10.804 connection
    closed
    Jan 28 17:36:32 localhost: 4081 PCSAFS130: Session with node 10.288
    terminated b
    y system administrator
    Jan 28 17:36:32 localhost: 4081 PCSAFS130: Session with node 10.288
    terminated b
    y system administrator
    Jan 28 17:36:32 localhost: 4081 PCSAFS130: Node 10.288 connection
    closed
    Jan 28 17:36:32 localhost: 4087 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:32 localhost: 4087 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:32 localhost: 4087 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:33 localhost: 366 PCSAFS130: Session with node 10.676
    terminated by
     system administrator
    Jan 28 17:36:33 localhost: 366 PCSAFS130: Session with node 10.676
    terminated by
     system administrator
    Jan 28 17:36:33 localhost: 366 PCSAFS130: Node 10.676 connection closed
    Jan 28 17:36:34 localhost: 4084 PCSAFS130: Session with node 10.764
    terminated b
    y system administrator
    Jan 28 17:36:34 localhost: 4084 PCSAFS130: Session with node 10.764
    terminated b
    y system administrator
    Jan 28 17:36:34 localhost: 4084 PCSAFS130: Node 10.764 connection
    closed
    Jan 28 17:36:34 localhost: 4098 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:34 localhost: 4098 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:34 localhost: 4098 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:34 localhost: 4096 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:34 localhost: 4096 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:34 localhost: 4096 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:35 localhost: 4103 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:35 localhost: 4103 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:35 localhost: 4103 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:36 localhost: 4095 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4095 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4095 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:36 localhost: 4100 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4100 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4100 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:36 localhost: 4106 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4107 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4107 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4106 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4107 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:36 localhost: 4106 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:36 localhost: 4092 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4092 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4092 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:36 localhost: 4114 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4114 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:36 localhost: 4114 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:37 localhost: 4109 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:37 localhost: 4109 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:37 localhost: 4109 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:37 localhost: 4120 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:37 localhost: 4120 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:37 localhost: 4120 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:37 localhost: 4128 PCSAFS130: Session with node 10.272
    terminated b
    y system administrator
    Jan 28 17:36:37 localhost: 4128 PCSAFS130: Session with node 10.272
    terminated b
    y system administrator
    Jan 28 17:36:37 localhost: 3262 PCSAFS130: Session with node 10.683
    terminated b
    y system administrator
    Jan 28 17:36:37 localhost: 3227 PCSAFS130: Session with node 10.631
    terminated b
    y system administrator
    Jan 28 17:36:37 localhost: 4128 PCSAFS130: Node 10.272 connection
    closed
    Jan 28 17:36:37 localhost: 3227 PCSAFS130: Session with node 10.631
    terminated b
    y system administrator
    Jan 28 17:36:37 localhost: 3227 PCSAFS130: Node 10.631 connection
    closed
    Jan 28 17:36:39 localhost: 4102 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4102 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4102 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:39 localhost: 4116 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4122 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4122 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4116 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4122 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:39 localhost: 4116 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:39 localhost: 4113 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4113 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:39 localhost: 4113 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:40 localhost: 3318 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:40 localhost: 3318 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:40 localhost: 3318 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:40 localhost: 4124 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:40 localhost: 4124 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:40 localhost: 4124 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:40 localhost: 4123 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:40 localhost: 4123 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:40 localhost: 4123 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:41 localhost: 4133 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4133 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4133 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:36:41 localhost: 4137 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4137 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4137 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:36:41 localhost: 476 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:41 localhost: 3310 PCSAFS130: Session with node 10.365
    terminated b
    y system administrator
    Jan 28 17:36:41 localhost: 4111 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4110 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4111 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4111 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:41 localhost: 4110 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4110 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:41 localhost: 4136 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4136 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:41 localhost: 4136 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:42 localhost: 4121 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:42 localhost: 4121 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:42 localhost: 4121 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:42 localhost: 4115 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:42 localhost: 4115 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:42 localhost: 4115 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:43 localhost: 4141 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:43 localhost: 4141 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:43 localhost: 4141 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:43 localhost: 3379 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:43 localhost: 4129 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:43 localhost: 4125 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:43 localhost: 4129 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:43 localhost: 4129 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:43 localhost: 4125 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:43 localhost: 4125 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:43 localhost: 4214 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:36:44 localhost: 4215 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:36:44 localhost: 4216 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:36:44 localhost: 4131 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4131 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4146 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4131 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:44 localhost: 4140 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4146 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4146 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:44 localhost: 4140 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4140 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:44 localhost: 4147 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4147 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:44 localhost: 4147 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:45 localhost: 4135 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:45 localhost: 4135 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:45 localhost: 4135 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:45 localhost: 4130 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:45 localhost: 4130 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:45 localhost: 4130 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:46 localhost: 4134 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4134 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4134 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:36:46 localhost: 4126 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4126 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4126 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:46 localhost: 4142 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4142 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4142 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:36:46 localhost: 4127 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4127 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:46 localhost: 4127 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:47 localhost: 4151 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:47 localhost: 3351 PCSAFS130: Session with node 10.734
    terminated b
    y system administrator
    Jan 28 17:36:47 localhost: 4151 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:47 localhost: 4151 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:47 localhost: 3351 PCSAFS130: Session with node 10.734
    terminated b
    y system administrator
    Jan 28 17:36:47 localhost: 3351 PCSAFS130: Node 10.734 connection
    closed
    Jan 28 17:36:47 localhost: 4156 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:47 localhost: 4155 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:47 localhost: 4156 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:47 localhost: 4155 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:47 localhost: 4155 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:47 localhost: 4156 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:48 localhost: 4157 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:48 localhost: 3391 PCSAFS130: Session with node 10.737
    terminated b
    y system administrator
    Jan 28 17:36:48 localhost: 4157 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:48 localhost: 4157 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:48 localhost: 3391 PCSAFS130: Session with node 10.737
    terminated b
    y system administrator
    Jan 28 17:36:48 localhost: 3391 PCSAFS130: Node 10.737 connection
    closed
    Jan 28 17:36:48 localhost: 477 PCSAFS130: Session with node 10.639
    terminated by
     system administrator
    Jan 28 17:36:48 localhost: 477 PCSAFS130: Session with node 10.639
    terminated by
     system administrator
    Jan 28 17:36:48 localhost: 477 PCSAFS130: Node 10.639 connection closed
    Jan 28 17:36:49 localhost: 4166 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:49 localhost: 4166 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:49 localhost: 4166 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:49 localhost: 4145 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:49 localhost: 4145 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:49 localhost: 4145 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:49 localhost: 4148 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4148 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4148 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:50 localhost: 4143 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4149 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4149 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4143 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4143 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:50 localhost: 4149 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:50 localhost: 4138 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4138 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:50 localhost: 4138 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:50 localhost: 4152 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:51 localhost: 4152 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:51 localhost: 4152 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:51 localhost: 4171 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:36:51 localhost: 4171 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:36:51 localhost: 4171 PCSAFS130: Node 10.804 connection
    closed
    Jan 28 17:36:51 localhost: 4179 PCSAFS130: Session with node
    pc8056.trimet.or te
    rminated by system administrator
    Jan 28 17:36:51 localhost: 4179 PCSAFS130: Session with node
    pc8056.trimet.or te
    rminated by system administrator
    Jan 28 17:36:51 localhost: 4179 PCSAFS130: Node pc8056.trimet.or
    connection clos
    ed
    Jan 28 17:36:51 localhost: 517 PCSAFS130: Session with node 10.507
    terminated by
     system administrator
    Jan 28 17:36:52 localhost: 4150 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:52 localhost: 521 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:52 localhost: 4150 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:52 localhost: 4150 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:52 localhost: 517 PCSAFS130: Session with node 10.507
    terminated by
     system administrator
    Jan 28 17:36:52 localhost: 517 PCSAFS130: Node 10.507 connection closed
    Jan 28 17:36:52 localhost: 521 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:52 localhost: 521 PCSAFS130: Node dhcpholladay.tri
    connection close
    d
    Jan 28 17:36:52 localhost: 4154 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:52 localhost: 4154 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:36:52 localhost: 4154 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:36:52 localhost: 4159 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:52 localhost: 4159 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:52 localhost: 4159 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:53 localhost: 4153 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:53 localhost: 4153 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:53 localhost: 4153 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:53 localhost: 1821 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:53 localhost: 3435 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:53 localhost: 1821 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:36:53 localhost: 1821 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:36:54 localhost: 4162 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:54 localhost: 4162 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:54 localhost: 4162 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:54 localhost: 3510 PCSAFS130: Session with node 10.128
    terminated b
    y system administrator
    Jan 28 17:36:54 localhost: 3510 PCSAFS130: Session with node 10.128
    terminated b
    y system administrator
    Jan 28 17:36:54 localhost: 3510 PCSAFS130: Node 10.128 connection
    closed
    Jan 28 17:36:54 localhost: 4180 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:54 localhost: 4180 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:54 localhost: 4180 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:55 localhost: 4160 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:55 localhost: 4160 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:55 localhost: 4160 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:55 localhost: 4172 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:55 localhost: 4172 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:55 localhost: 4172 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:55 localhost: 2438 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:55 localhost: 627 PCSAFS130: Session with node 10.672
    terminated by
     system administrator
    Jan 28 17:36:55 localhost: 627 PCSAFS130: Session with node 10.672
    terminated by
     system administrator
    Jan 28 17:36:55 localhost: 627 PCSAFS130: Node 10.672 connection closed
    Jan 28 17:36:55 localhost: 3588 PCSAFS130: Session with node 10.638
    terminated b
    y system administrator
    Jan 28 17:36:56 localhost: 4185 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4178 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 2472 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4185 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4185 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:56 localhost: 4178 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4178 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:56 localhost: 4177 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 3588 PCSAFS130: Session with node 10.638
    terminated b
    y system administrator
    Jan 28 17:36:56 localhost: 4177 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4177 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:56 localhost: 3588 PCSAFS130: Node 10.638 connection
    closed
    Jan 28 17:36:56 localhost: 760 PCSAFS130: Session with node 10.511
    terminated by
     system administrator
    Jan 28 17:36:56 localhost: 2472 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 2472 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:56 localhost: 4190 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4190 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4190 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:56 localhost: 4164 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4164 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4164 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:56 localhost: 4165 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4165 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:56 localhost: 4165 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:57 localhost: 4163 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:57 localhost: 4163 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:57 localhost: 4163 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:57 localhost: 4173 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:57 localhost: 4173 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:57 localhost: 4206 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:57 localhost: 4173 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:57 localhost: 4206 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:57 localhost: 4206 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:58 localhost: 771 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:58 localhost: 2498 PCSAFS130: Session with node 10.600
    terminated b
    y system administrator
    Jan 28 17:36:58 localhost: 2619 PCSAFS130: Session with node 10.677
    terminated b
    y system administrator
    Jan 28 17:36:58 localhost: 2594 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:59 localhost: 2630 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:59 localhost: 2630 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:36:59 localhost: 2630 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:36:59 localhost: 722 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:59 localhost: 2578 PCSAFS130: Session with node 10.775
    terminated b
    y system administrator
    Jan 28 17:36:59 localhost: 722 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:36:59 localhost: 722 PCSAFS130: Node dhcpholladay.tri
    connection close
    d
    Jan 28 17:37:00 localhost: 3687 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:00 localhost: 3687 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:00 localhost: 3687 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:00 localhost: 2573 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:00 localhost: 2543 PCSAFS130: Session with node 10.789
    terminated b
    y system administrator
    Jan 28 17:37:01 localhost: 3685 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 2451 PCSAFS130: Session with node 10.778
    terminated b
    y system administrator
    Jan 28 17:37:01 localhost: 4188 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 4181 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 4188 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 4188 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:01 localhost: 4181 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 3685 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 3685 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:01 localhost: 4181 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:01 localhost: 2451 PCSAFS130: Session with node 10.778
    terminated b
    y system administrator
    Jan 28 17:37:01 localhost: 2451 PCSAFS130: Node 10.778 connection
    closed
    Jan 28 17:37:01 localhost: 2635 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 2635 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 2635 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:01 localhost: 2496 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 2496 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:37:01 localhost: 2496 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:37:01 localhost: 2207 PCSAFS130: Session with node 10.92
    terminated by
     system administrator
    Jan 28 17:37:02 localhost: 1090 PCSAFS130: Session with node 10.311
    terminated b
    y system administrator
    Jan 28 17:37:02 localhost: 2207 PCSAFS130: Session with node 10.92
    terminated by
     system administrator
    Jan 28 17:37:02 localhost: 2207 PCSAFS130: Node 10.92 connection closed
    Jan 28 17:37:02 localhost: 3929 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:02 localhost: 2470 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:02 localhost: 3929 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:02 localhost: 3929 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:02 localhost: 2470 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:02 localhost: 2470 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:02 localhost: 2734 PCSAFS130: Session with node 10.747
    terminated b
    y system administrator
    Jan 28 17:37:03 localhost: 2734 PCSAFS130: Session with node 10.747
    terminated b
    y system administrator
    Jan 28 17:37:03 localhost: 2734 PCSAFS130: Node 10.747 connection
    closed
    Jan 28 17:37:03 localhost: 2591 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:03 localhost: 2643 PCSAFS130: Session with node 10.331
    terminated b
    y system administrator
    Jan 28 17:37:03 localhost: 2591 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:03 localhost: 2591 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:03 localhost: 2643 PCSAFS130: Session with node 10.331
    terminated b
    y system administrator
    Jan 28 17:37:03 localhost: 2643 PCSAFS130: Node 10.331 connection
    closed
    Jan 28 17:37:03 localhost: 3944 PCSAFS130: Session with node 10.684
    terminated b
    y system administrator
    Jan 28 17:37:03 localhost: 3944 PCSAFS130: Session with node 10.684
    terminated b
    y system administrator
    Jan 28 17:37:03 localhost: 3944 PCSAFS130: Node 10.684 connection
    closed
    Jan 28 17:37:04 localhost: 3689 PCSAFS130: Session with node 10.273
    terminated b
    y system administrator
    Jan 28 17:37:04 localhost: 3689 PCSAFS130: Session with node 10.273
    terminated b
    y system administrator
    Jan 28 17:37:04 localhost: 3689 PCSAFS130: Node 10.273 connection
    closed
    Jan 28 17:37:04 localhost: 2518 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:05 localhost: 2682 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:05 localhost: 3855 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:05 localhost: 2708 PCSAFS130: Session with node 10.348
    terminated b
    y system administrator
    Jan 28 17:37:05 localhost: 2555 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:37:06 localhost: 2716 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:06 localhost: 3962 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:06 localhost: 3962 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:06 localhost: 3962 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:06 localhost: 3986 PCSAFS130: Session with node 10.673
    terminated b
    y system administrator
    Jan 28 17:37:06 localhost: 1235 PCSAFS130: Session with node 10.341
    terminated b
    y system administrator
    Jan 28 17:37:06 localhost: 3986 PCSAFS130: Session with node 10.673
    terminated b
    y system administrator
    Jan 28 17:37:06 localhost: 3986 PCSAFS130: Node 10.673 connection
    closed
    Jan 28 17:37:07 localhost: 2605 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:07 localhost: 1235 PCSAFS130: Session with node 10.341
    terminated b
    y system administrator
    Jan 28 17:37:07 localhost: 1235 PCSAFS130: Node 10.341 connection
    closed
    Jan 28 17:37:07 localhost: 2605 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:07 localhost: 2605 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:07 localhost: 3972 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:37:07 localhost: 2747 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:08 localhost: 2747 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:08 localhost: 2747 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:08 localhost: 3991 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:08 localhost: 3991 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:08 localhost: 3991 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:08 localhost: 2684 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:08 localhost: 3990 PCSAFS130: Session with node 10.764
    terminated b
    y system administrator
    Jan 28 17:37:08 localhost: 3990 PCSAFS130: Session with node 10.764
    terminated b
    y system administrator
    Jan 28 17:37:08 localhost: 3990 PCSAFS130: Node 10.764 connection
    closed
    Jan 28 17:37:09 localhost: 3954 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3954 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3954 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:09 localhost: 3992 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3947 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3993 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 4217 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:09 localhost: 3992 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3992 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:09 localhost: 3947 PCSAFS130: Session with node
    dhcphillsboro.tr te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3947 PCSAFS130: Node dhcphillsboro.tr
    connection clos
    ed
    Jan 28 17:37:09 localhost: 3993 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3993 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:09 localhost: 3925 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 2749 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3925 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:09 localhost: 3925 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:09 localhost: 1378 PCSAFS130: Session with node 10.339
    terminated b
    y system administrator
    Jan 28 17:37:10 localhost: 1378 PCSAFS130: Session with node 10.339
    terminated b
    y system administrator
    Jan 28 17:37:10 localhost: 1378 PCSAFS130: Node 10.339 connection
    closed
    Jan 28 17:37:10 localhost: 2753 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:10 localhost: 1356 PCSAFS130: Session with node 10.319
    terminated b
    y system administrator
    Jan 28 17:37:10 localhost: 1356 PCSAFS130: Session with node 10.319
    terminated b
    y system administrator
    Jan 28 17:37:10 localhost: 1356 PCSAFS130: Node 10.319 connection
    closed
    Jan 28 17:37:10 localhost: 1246 PCSAFS130: Session with node 10.689
    terminated b
    y system administrator
    Jan 28 17:37:10 localhost: 3963 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:11 localhost: 2806 PCSAFS130: Session with node 10.253
    terminated b
    y system administrator
    Jan 28 17:37:11 localhost: 2806 PCSAFS130: Session with node 10.253
    terminated b
    y system administrator
    Jan 28 17:37:11 localhost: 2806 PCSAFS130: Node 10.253 connection
    closed
    Jan 28 17:37:11 localhost: 1437 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:11 localhost: 2805 PCSAFS130: Session with node 10.650
    terminated b
    y system administrator
    Jan 28 17:37:11 localhost: 1474 PCSAFS130: Session with node 10.763
    terminated b
    y system administrator
    Jan 28 17:37:11 localhost: 2805 PCSAFS130: Session with node 10.650
    terminated b
    y system administrator
    Jan 28 17:37:11 localhost: 2805 PCSAFS130: Node 10.650 connection
    closed
    Jan 28 17:37:12 localhost: 3964 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 4007 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 1474 PCSAFS130: Session with node 10.763
    terminated b
    y system administrator
    Jan 28 17:37:12 localhost: 1474 PCSAFS130: Node 10.763 connection
    closed
    Jan 28 17:37:12 localhost: 3964 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 3964 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:12 localhost: 4007 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 4007 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:12 localhost: 3996 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 4014 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 3996 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 3996 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:12 localhost: 4014 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:12 localhost: 4014 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:13 localhost: 4218 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:13 localhost: 4219 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:13 localhost: 4220 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:13 localhost: 3997 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:13 localhost: 4015 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:13 localhost: 3997 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:13 localhost: 3997 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:13 localhost: 4015 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:13 localhost: 4015 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:13 localhost: 3989 PCSAFS130: Session with node 10.787
    terminated b
    y system administrator
    Jan 28 17:37:13 localhost: 3989 PCSAFS130: Session with node 10.787
    terminated b
    y system administrator
    Jan 28 17:37:13 localhost: 3089 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:13 localhost: 3989 PCSAFS130: Node 10.787 connection
    closed
    Jan 28 17:37:13 localhost: 3089 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:14 localhost: 346 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:37:14 localhost: 3187 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:14 localhost: 3310 PCSAFS130: Session with node 10.365
    terminated b
    y system administrator
    Jan 28 17:37:14 localhost: 2498 PCSAFS130: Session with node 10.600
    terminated b
    y system administrator
    Jan 28 17:37:14 localhost: 3310 PCSAFS130: Node 10.365 connection
    closed
    Jan 28 17:37:14 localhost: 771 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:37:14 localhost: 346 PCSAFS130: Node dhcpholladay.tri
    connection close
    d
    Jan 28 17:37:14 localhost: 3855 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:14 localhost: 3855 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 3187 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 476 PCSAFS130: Session with node
    dhcpholladay.tri ter
    minated by system administrator
    Jan 28 17:37:15 localhost: 476 PCSAFS130: Node dhcpholladay.tri
    connection close
    d
    Jan 28 17:37:15 localhost: 2498 PCSAFS130: Node 10.600 connection
    closed
    Jan 28 17:37:15 localhost: 2716 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 2716 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 771 PCSAFS130: Node dhcpholladay.tri
    connection close
    d
    Jan 28 17:37:15 localhost: 2555 PCSAFS130: Session with node
    dhcphawthorn.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 2555 PCSAFS130: Node dhcphawthorn.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 2708 PCSAFS130: Session with node 10.348
    terminated b
    y system administrator
    Jan 28 17:37:15 localhost: 2708 PCSAFS130: Node 10.348 connection
    closed
    Jan 28 17:37:15 localhost: 2438 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 2438 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 3435 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 3435 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 3379 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 3379 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 1246 PCSAFS130: Session with node 10.689
    terminated b
    y system administrator
    Jan 28 17:37:15 localhost: 1246 PCSAFS130: Node 10.689 connection
    closed
    Jan 28 17:37:15 localhost: 2573 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 2573 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 2682 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 2682 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 1437 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 1437 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 2684 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:15 localhost: 2684 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:15 localhost: 2543 PCSAFS130: Session with node 10.789
    terminated b
    y system administrator
    Jan 28 17:37:15 localhost: 2543 PCSAFS130: Node 10.789 connection
    closed
    Jan 28 17:37:15 localhost: 760 PCSAFS130: Session with node 10.511
    terminated by
     system administrator
    Jan 28 17:37:15 localhost: 760 PCSAFS130: Node 10.511 connection closed
    Jan 28 17:37:15 localhost: 1090 PCSAFS130: Session with node 10.311
    terminated b
    y system administrator
    Jan 28 17:37:15 localhost: 1090 PCSAFS130: Node 10.311 connection
    closed
    Jan 28 17:37:15 localhost: 2578 PCSAFS130: Session with node 10.775
    terminated b
    y system administrator
    Jan 28 17:37:15 localhost: 2578 PCSAFS130: Node 10.775 connection
    closed
    Jan 28 17:37:16 localhost: 2753 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:16 localhost: 3972 PCSAFS130: Session with node 10.804
    terminated b
    y system administrator
    Jan 28 17:37:16 localhost: 3972 PCSAFS130: Node 10.804 connection
    closed
    Jan 28 17:37:16 localhost: 2753 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:16 localhost: 4003 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:16 localhost: 3047 PCSAFS130: Session with node 10.718
    terminated b
    y system administrator
    Jan 28 17:37:16 localhost: 3047 PCSAFS130: Node 10.718 connection
    closed
    Jan 28 17:37:16 localhost: 4002 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:16 localhost: 2518 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:16 localhost: 2518 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:16 localhost: 2619 PCSAFS130: Session with node 10.677
    terminated b
    y system administrator
    Jan 28 17:37:16 localhost: 2619 PCSAFS130: Node 10.677 connection
    closed
    Jan 28 17:37:16 localhost: 2774 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:16 localhost: 2749 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:16 localhost: 2749 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:17 localhost: 3995 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:17 localhost: 4020 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:17 localhost: 4043 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:17 localhost: 3995 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:17 localhost: 3995 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:17 localhost: 4017 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:17 localhost: 4033 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:17 localhost: 4004 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:17 localhost: 4003 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:17 localhost: 4003 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:17 localhost: 2874 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:17 localhost: 4048 PCSAFS130: Node 10.804 terminated by
    Broken pipe
     signal at pc 431548
    Jan 28 17:37:18 localhost: 2594 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:18 localhost: 2594 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:18 localhost: 3963 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:18 localhost: 3963 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:18 localhost: 4047 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:18 localhost: 4019 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:18 localhost: 4223 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:18 localhost: 4017 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:18 localhost: 4017 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:18 localhost: 4016 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:18 localhost: 4021 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:18 localhost: 4008 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:19 localhost: 4000 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:19 localhost: 4021 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:19 localhost: 4009 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:19 localhost: 4021 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:19 localhost: 4042 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:19 localhost: 2774 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:19 localhost: 2774 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:19 localhost: 4228 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:19 localhost: 4000 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:19 localhost: 4000 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:19 localhost: 4022 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:19 localhost: 4230 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:19 localhost: 4002 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:19 localhost: 4002 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:19 localhost: 4232 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:19 localhost: 3262 PCSAFS130: Session with node 10.683
    terminated b
    y system administrator
    Jan 28 17:37:19 localhost: 3262 PCSAFS130: Node 10.683 connection
    closed
    Jan 28 17:37:20 localhost: 4018 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:20 localhost: 4023 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:20 localhost: 3998 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:20 localhost: 3998 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:20 localhost: 3998 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:20 localhost: 4011 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:20 localhost: 4025 PCSAFS130: Session with node 10.600
    terminated b
    y system administrator
    Jan 28 17:37:20 localhost: 4046 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:20 localhost: 2874 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:20 localhost: 2874 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:20 localhost: 4011 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:20 localhost: 4011 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:20 localhost: 4028 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:20 localhost: 4006 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:21 localhost: 2933 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:21 localhost: 4019 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:21 localhost: 4019 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:21 localhost: 4032 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:21 localhost: 4039 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:21 localhost: 4026 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:21 localhost: 4008 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:21 localhost: 4008 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:21 localhost: 2836 PCSAFS130: Session with node 10.519
    terminated b
    y system administrator
    Jan 28 17:37:21 localhost: 4035 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:21 localhost: 4009 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:21 localhost: 4009 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:21 localhost: 4027 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:21 localhost: 4034 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:22 localhost: 4044 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:22 localhost: 4010 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:22 localhost: 4010 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:22 localhost: 4010 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:22 localhost: 4016 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:22 localhost: 4016 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:22 localhost: 4025 PCSAFS130: Session with node 10.600
    terminated b
    y system administrator
    Jan 28 17:37:22 localhost: 4025 PCSAFS130: Node 10.600 connection
    closed
    Jan 28 17:37:22 localhost: 4040 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:22 localhost: 4004 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:22 localhost: 4004 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:22 localhost: 4038 PCSAFS130: Node 10.804 terminated by
    Broken pipe
     signal at pc 431548
    Jan 28 17:37:22 localhost: 1513 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:22 localhost: 4045 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:23 localhost: 4036 PCSAFS130: Node dhcpholladay.tri
    terminated by B
    roken pipe signal at pc 431548
    Jan 28 17:37:23 localhost: 4248 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:23 localhost: 4250 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:23 localhost: 4006 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:23 localhost: 4006 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:23 localhost: 4035 PCSAFS130: Session with node
    dhcpholladay.tri te
    rminated by system administrator
    Jan 28 17:37:23 localhost: 4035 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:24 localhost: 4251 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:24 localhost: 4020 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:24 localhost: 4020 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:25 localhost: 4042 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:25 localhost: 4043 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:25 localhost: 4043 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:25 localhost: 4042 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:25 localhost: 4048 PCSAFS130: Connection to node 10.804
    terminated 
    due to fatal error - Invalid argument
    Jan 28 17:37:25 localhost: 4048 PCSAFS130: Node 10.804 connection
    closed
    Jan 28 17:37:25 localhost: 2836 PCSAFS130: Session with node 10.519
    terminated b
    y system administrator
    Jan 28 17:37:25 localhost: 2836 PCSAFS130: Node 10.519 connection
    closed
    Jan 28 17:37:28 localhost: 4041 PCSAFS130: Session with node 10.600
    terminated b
    y system administrator
    Jan 28 17:37:28 localhost: 4023 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:28 localhost: 4023 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:28 localhost: 4022 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:28 localhost: 4047 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:28 localhost: 4047 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:28 localhost: 4022 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:28 localhost: 4033 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:28 localhost: 4033 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:30 localhost: 4041 PCSAFS130: Session with node 10.600
    terminated b
    y system administrator
    Jan 28 17:37:33 localhost: 4041 PCSAFS130: Node 10.600 connection
    closed
    Jan 28 17:37:33 localhost: 1570 PCSAFS130: Session with node 10.343
    terminated b
    y system administrator
    Jan 28 17:37:33 localhost: 4026 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:33 localhost: 4040 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:33 localhost: 4040 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:33 localhost: 4046 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:33 localhost: 4046 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:33 localhost: 4044 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:33 localhost: 4044 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:33 localhost: 4032 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:33 localhost: 4032 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:33 localhost: 4018 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:33 localhost: 4018 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:33 localhost: 4026 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 4027 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 4027 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 2933 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 2933 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 4038 PCSAFS130: Connection to node 10.804
    terminated 
    due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 4038 PCSAFS130: Node 10.804 connection
    closed
    Jan 28 17:37:34 localhost: 4034 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 4034 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 4028 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 4039 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 4039 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 1513 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 1513 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 4036 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 4036 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 4028 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 4045 PCSAFS130: Connection to node
    dhcpholladay.tri t
    erminated due to fatal error - Invalid argument
    Jan 28 17:37:34 localhost: 4045 PCSAFS130: Node dhcpholladay.tri
    connection clos
    ed
    Jan 28 17:37:34 localhost: 175 PCSANBUD130: Process Terminated normally
    Jan 28 17:37:34 localhost: 1570 PCSAFS130: Session with node 10.343
    terminated b
    y system administrator
    Jan 28 17:37:34 localhost: 1570 PCSAFS130: Node 10.343 connection
    closed
    Jan 28 17:37:37 localhost: 4252 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:37 localhost: 4253 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:45 localhost: 4254 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:46 localhost: 173 PCSAADMD130: Server stopped
    Jan 28 17:37:48 localhost: 4259 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:50 localhost: 4260 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:51 localhost: 4261 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:52 localhost: 4262 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:53 localhost: 4263 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:54 localhost: 4264 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:37:56 localhost: 4265 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:38:06 localhost: 4266 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:38:07 localhost: 4267 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:38:07 localhost: 4268 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:38:08 localhost: 4269 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:38:09 localhost: 4270 PCSAFS130: Unable to open pcsaadmd
    message queue
     - No such file or directory
    Jan 28 17:38:19 localhost: 4273 PCSAADMD130: Server started
    Jan 28 17:38:19 localhost: 4273 PCSAADMD130: Size of sess_info  40 *
    512  = 2048
    0
    Jan 28 17:38:19 localhost: 4273 PCSAADMD130: Size of tid_info  216 *
    2048  = 442
    368
    Jan 28 17:38:19 localhost: 4273 PCSAADMD130: Size of file_data_base 
    124 * 2048 
    = 253952
    Jan 28 17:38:20 localhost: 4273 PCSAADMD130: Size of server_statistics 
    48
    Jan 28 17:38:20 localhost: 4273 PCSAADMD130: Size of server_common  36
    Jan 28 17:38:20 localhost: 4273 PCSAADMD130: Size of lanman_ini  316
    Jan 28 17:38:20 localhost: 4273 PCSAADMD130: Size of unique open file
    table 24 *
     2048 = 49152
    Jan 28 17:38:20 localhost: 4273 PCSAADMD130: Size of server lock table
    20 * 2048
     = 40960
    Jan 28 17:38:20 localhost: 4273 PCSAADMD130: Total shared memory size =
    807312
    Jan 28 17:38:20 localhost: 4275 PCSANBUD130: Starting NetBIOS Utilities
    (PCSANBU
    D) V1.1 
    Jan 28 17:38:20 localhost: 4275 PCSANBUD130: DLI/DECnet ethernet
    controller: ln0
    Jan 28 17:38:20 localhost: 4275 PCSANBUD130: UDP/TCP Transport
    Avaliable
    Jan 28 17:38:20 localhost: 4275 PCSANBUD130: DLI/DECnet Transport
    Avaliable
    Jan 28 17:38:20 localhost: 4275 PCSANBUD130: Scope[0] = (null)
    Jan 28 17:38:23 localhost: 4291 PCSAFS130: Starting server with 10.684
    and netbi
    os name PC684
    Jan 28 17:38:25 localhost: 4291 PCSAFS130: Connect 0 Session 0  start
    on node 10
    .684 user pcguest for service netbats
    Jan 28 17:38:25 localhost: 4291 PCSAFS130: Connect 1 Session 0  start
    on node 10
    .684 user pcguest for service pcsav41
    Jan 28 17:38:42 localhost: 4303 PCSAFS130: Starting server with 10.747
    and netbi
    os name PC747
    Jan 28 17:38:42 localhost: 4302 PCSAFS130: Starting server with
    dhcpholladay.tri
     and netbios name PC308
    Jan 28 17:38:42 localhost: 4302 PCSAFS130: Connect 2 Session 1  start
    on node dh
    cpholladay.tri user ltkuser for service lrvspec
    Jan 28 17:38:42 localhost: 4303 PCSAFS130: Connect 3 Session 2  start
    on node 10
    .747 user pcguest for service pcsav41
    Jan 28 17:38:42 localhost: 4304 PCSAFS130: Starting server with 10.747
    and netbi
    os name PC747
    
    
    Jan 21 04:05:01 syslog restart
    Jan 21 05:55:24 localhost: 3761 PCSAFS130: Node 172.18.4.25 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 05:55:24 localhost: 3761 PCSAFS130: Node 172.18.4.25 connection
    closed
    Jan 21 05:55:34 localhost: 3762 PCSAFS130: Node 172.18.4.25 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 05:55:34 localhost: 3762 PCSAFS130: Node 172.18.4.25 connection
    closed
    Jan 21 05:56:59 localhost: 3765 PCSAFS130: Node 172.18.4.24 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 05:56:59 localhost: 3765 PCSAFS130: Node 172.18.4.24 connection
    closed
    Jan 21 05:57:09 localhost: 3766 PCSAFS130: Starting server with
    172.18.4.24 and 
    netbios name PC529
    Jan 21 05:58:38 localhost: 3766 PCSAFS130: Node 172.18.4.24 connection
    closed
    Jan 21 05:59:43 localhost: 3768 PCSAFS130: Node 172.18.4.24 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 05:59:43 localhost: 3768 PCSAFS130: Node 172.18.4.24 connection
    closed
    Jan 21 05:59:53 localhost: 3769 PCSAFS130: Node 172.18.4.24 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 05:59:53 localhost: 3769 PCSAFS130: Node 172.18.4.24 connection
    closed
    Jan 21 06:01:03 localhost: 3775 PCSAFS130: Node 172.18.4.24 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:01:03 localhost: 3775 PCSAFS130: Node 172.18.4.24 connection
    closed
    Jan 21 06:08:44 localhost: 3777 PCSAFS130: Node 172.18.4.14 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:08:44 localhost: 3777 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:09:12 localhost: 3778 PCSAFS130: Node 172.18.4.14 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:09:12 localhost: 3778 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:09:22 localhost: 3779 PCSAFS130: Starting server with
    172.18.4.14 and 
    netbios name PC788
    Jan 21 06:09:22 localhost: 3779 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:10:29 localhost: 3782 PCSAFS130: Node 172.18.4.14 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:10:29 localhost: 3782 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:10:51 localhost: 3783 PCSAFS130: Node 172.18.4.14 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:10:51 localhost: 3783 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:11:01 localhost: 3784 PCSAFS130: Node 172.18.4.14 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:11:01 localhost: 3784 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:14:20 localhost: 3788 PCSAFS130: Node 172.18.4.24 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:14:20 localhost: 3788 PCSAFS130: Node 172.18.4.24 connection
    closed
    Jan 21 06:20:59 localhost: 3793 PCSAFS130: Node 172.18.4.26 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:20:59 localhost: 3793 PCSAFS130: Node 172.18.4.26 connection
    closed
    Jan 21 06:21:09 localhost: 3794 PCSAFS130: Node 172.18.4.26 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:21:09 localhost: 3794 PCSAFS130: Node 172.18.4.26 connection
    closed
    Jan 21 06:22:17 localhost: 3797 PCSAFS130: Node 172.18.4.26 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:22:17 localhost: 3797 PCSAFS130: Node 172.18.4.26 connection
    closed
    Jan 21 06:22:57 localhost: 3798 PCSAFS130: Node 172.18.4.25 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:22:57 localhost: 3798 PCSAFS130: Node 172.18.4.25 connection
    closed
    Jan 21 06:24:40 localhost: 3801 PCSAFS130: Node 172.18.4.0 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 06:24:40 localhost: 3801 PCSAFS130: Node 172.18.4.0 connection
    closed
    Jan 21 06:24:50 localhost: 3802 PCSAFS130: Node 172.18.4.0 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 06:24:50 localhost: 3802 PCSAFS130: Node 172.18.4.0 connection
    closed
    Jan 21 06:25:16 localhost: 3803 PCSAFS130: Node 172.18.4.0 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 06:25:16 localhost: 3803 PCSAFS130: Node 172.18.4.0 connection
    closed
    Jan 21 06:26:58 localhost: 3807 PCSAFS130: Node 172.18.4.0 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 06:26:58 localhost: 3807 PCSAFS130: Node 172.18.4.0 connection
    closed
    Jan 21 06:27:08 localhost: 3808 PCSAFS130: Node 172.18.4.0 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 06:27:08 localhost: 3808 PCSAFS130: Node 172.18.4.0 connection
    closed
    Jan 21 06:31:45 localhost: 3816 PCSAFS130: Starting server with 10.734
    and netbi
    os name PC734
    Jan 21 06:31:45 localhost: 3816 PCSAFS130: Connect 4 Session 145  start
    on node 
    10.734 user pcguest for service ccd
    Jan 21 06:32:33 localhost: 3814 PCSAFS130: Node 172.18.4.14 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:32:33 localhost: 3814 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:32:43 localhost: 3815 PCSAFS130: Node 172.18.4.14 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:32:43 localhost: 3815 PCSAFS130: Node 172.18.4.14 connection
    closed
    Jan 21 06:40:12 localhost: 3821 PCSAFS130: Node 172.18.4.140 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 06:40:12 localhost: 3821 PCSAFS130: Node 172.18.4.140 connection
    closed
    Jan 21 06:42:55 localhost: 3823 PCSAFS130: Node 172.18.4.131 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 06:42:55 localhost: 3823 PCSAFS130: Node 172.18.4.131 connection
    closed
    Jan 21 06:43:05 localhost: 3824 PCSAFS130: Node 172.18.4.131 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 06:43:05 localhost: 3824 PCSAFS130: Node 172.18.4.131 connection
    closed
    Jan 21 06:43:53 localhost: 3825 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:43:53 localhost: 3825 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:44:38 localhost: 3828 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:44:38 localhost: 3828 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:45:39 localhost: 3831 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:45:39 localhost: 3831 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:46:24 localhost: 3835 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:46:24 localhost: 3835 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:47:50 localhost: 3838 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:47:50 localhost: 3838 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:48:35 localhost: 3839 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:48:35 localhost: 3839 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:49:43 localhost: 3842 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:49:43 localhost: 3842 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:50:28 localhost: 3843 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:50:28 localhost: 3843 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 06:53:26 localhost: 3846 PCSAFS130: Node 172.18.4.27 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:53:26 localhost: 3846 PCSAFS130: Node 172.18.4.27 connection
    closed
    Jan 21 06:53:36 localhost: 3847 PCSAFS130: Node 172.18.4.27 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:53:36 localhost: 3847 PCSAFS130: Node 172.18.4.27 connection
    closed
    Jan 21 06:54:00 localhost: 3848 PCSAFS130: Node 172.18.4.27 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 06:54:00 localhost: 3848 PCSAFS130: Node 172.18.4.27 connection
    closed
    Jan 21 06:57:20 localhost: 3852 PCSAFS130: Starting server with 10.666
    and netbi
    os name PC666
    Jan 21 06:57:20 localhost: 3852 PCSAFS130: Connect 6 Session 162  start
    on node 
    10.666 user pcguest for service ccm
    Jan 21 06:57:21 localhost: 3852 PCSAFS130: Connect 7 Session 162  start
    on node 
    10.666 user pcguest for service ccd
    Jan 21 06:59:58 localhost: 3864 PCSAFS130: Starting server with 10.655
    and netbi
    os name WS_ADDR
    Jan 21 06:59:58 localhost: 3864 PCSAFS130: Connect 8 Session 163  start
    on node 
    10.655 user pcguest for service ccm
    Jan 21 06:59:59 localhost: 3864 PCSAFS130: Connect 9 Session 163  start
    on node 
    10.655 user pcguest for service ccd
    Jan 21 07:01:17 localhost: 3872 PCSAFS130: Starting server with 10.778
    and netbi
    os name PC778
    Jan 21 07:01:17 localhost: 3872 PCSAFS130: Connect 10 Session 164 
    start on node
     10.778 user pcguest for service ccm
    Jan 21 07:01:18 localhost: 3872 PCSAFS130: Connect 11 Session 164 
    start on node
     10.778 user pcguest for service ccd
    Jan 21 07:08:08 localhost: 3873 PCSAFS130: Node 172.18.4.34 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:08:08 localhost: 3873 PCSAFS130: Node 172.18.4.34 connection
    closed
    Jan 21 07:11:04 localhost: 3875 PCSAFS130: Node 172.18.4.131 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 07:11:05 localhost: 3875 PCSAFS130: Node 172.18.4.131 connection
    closed
    Jan 21 07:11:12 localhost: 3876 PCSAFS130: Node 172.18.4.34 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:11:12 localhost: 3876 PCSAFS130: Node 172.18.4.34 connection
    closed
    Jan 21 07:11:23 localhost: 3877 PCSAFS130: Node 172.18.4.131 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 07:11:23 localhost: 3877 PCSAFS130: Node 172.18.4.131 connection
    closed
    Jan 21 07:12:01 localhost: 3878 PCSAFS130: Node 172.18.4.131 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 07:12:01 localhost: 3878 PCSAFS130: Node 172.18.4.131 connection
    closed
    Jan 21 07:12:09 localhost: 3880 PCSAFS130: Node 172.18.4.40 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:12:09 localhost: 3880 PCSAFS130: Node 172.18.4.40 connection
    closed
    Jan 21 07:12:17 localhost: 3882 PCSAFS130: Node 172.18.4.131 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 07:12:17 localhost: 3882 PCSAFS130: Node 172.18.4.131 connection
    closed
    Jan 21 07:12:19 localhost: 3883 PCSAFS130: Node 172.18.4.40 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:12:19 localhost: 3883 PCSAFS130: Node 172.18.4.40 connection
    closed
    Jan 21 07:12:40 localhost: 3885 PCSAFS130: Node 172.18.4.131 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 07:12:40 localhost: 3885 PCSAFS130: Node 172.18.4.131 connection
    closed
    Jan 21 07:15:13 localhost: 3891 PCSAFS130: Node 172.18.4.25 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:15:13 localhost: 3891 PCSAFS130: Node 172.18.4.25 connection
    closed
    Jan 21 07:15:56 localhost: 3896 PCSAFS130: Starting server with 10.273
    and netbi
    os name PC273
    Jan 21 07:15:56 localhost: 3896 PCSAFS130: Connect 12 Session 178 
    start on node
     10.273 user pcguest for service ccm
    Jan 21 07:15:57 localhost: 3896 PCSAFS130: Connect 13 Session 178 
    start on node
     10.273 user pcguest for service ccd
    Jan 21 07:19:02 localhost: 3897 PCSAFS130: Node 172.18.4.40 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:19:02 localhost: 3897 PCSAFS130: Node 172.18.4.40 connection
    closed
    Jan 21 07:20:45 localhost: 3899 PCSAFS130: Node 172.18.4.40 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:20:45 localhost: 3899 PCSAFS130: Node 172.18.4.40 connection
    closed
    Jan 21 07:20:55 localhost: 3900 PCSAFS130: Node 172.18.4.40 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:20:55 localhost: 3900 PCSAFS130: Node 172.18.4.40 connection
    closed
    Jan 21 07:21:11 localhost: 3905 PCSAFS130: Starting server with 10.670
    and netbi
    os name PC670
    Jan 21 07:21:11 localhost: 3905 PCSAFS130: Connect 14 Session 183 
    start on node
     10.670 user pcguest for service ccd
    Jan 21 07:21:20 localhost: 3901 PCSAFS130: Node 172.18.4.40 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:21:20 localhost: 3901 PCSAFS130: Node 172.18.4.40 connection
    closed
    Jan 21 07:21:39 localhost: 3902 PCSAFS130: Node 172.18.4.40 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:21:39 localhost: 3902 PCSAFS130: Node 172.18.4.40 connection
    closed
    Jan 21 07:22:23 localhost: 3896 PCSAFS130: Client 10.273 user pcguest
    stopped co
    nnection tid 12
    Jan 21 07:22:24 localhost: 3896 PCSAFS130: Client 10.273 user pcguest
    stopped co
    nnection tid 13
    Jan 21 07:22:24 localhost: 3896 PCSAFS130: Node 10.273 connection
    closed
    Jan 21 07:22:46 localhost: 3908 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:22:46 localhost: 3908 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:22:56 localhost: 3909 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:22:56 localhost: 3909 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:23:30 localhost: 3910 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:23:30 localhost: 3910 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:23:55 localhost: 3912 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:23:55 localhost: 3912 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:24:13 localhost: 3914 PCSAFS130: Node 172.18.4.38 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:24:13 localhost: 3914 PCSAFS130: Node 172.18.4.38 connection
    closed
    Jan 21 07:24:24 localhost: 3915 PCSAFS130: Node 172.18.4.38 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:24:24 localhost: 3915 PCSAFS130: Node 172.18.4.38 connection
    closed
    Jan 21 07:24:35 localhost: 3917 PCSAFS130: Node 172.18.4.38 terminated
    by Broken
     pipe signal at pc 431548
     Jan 21 07:24:35 localhost: 3917 PCSAFS130: Node 172.18.4.38 connection
    closed
    Jan 21 07:24:45 localhost: 3918 PCSAFS130: Node 172.18.4.38 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:24:45 localhost: 3918 PCSAFS130: Node 172.18.4.38 connection
    closed
    Jan 21 07:24:50 localhost: 3919 PCSAFS130: Node 172.18.4.32 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:24:50 localhost: 3919 PCSAFS130: Node 172.18.4.32 connection
    closed
    Jan 21 07:25:00 localhost: 3921 PCSAFS130: Node 172.18.4.32 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:25:00 localhost: 3921 PCSAFS130: Node 172.18.4.32 connection
    closed
    Jan 21 07:25:59 localhost: 3927 PCSAFS130: Node 172.18.4.22 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:25:59 localhost: 3927 PCSAFS130: Node 172.18.4.22 connection
    closed
    Jan 21 07:26:09 localhost: 3929 PCSAFS130: Node 172.18.4.22 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:26:09 localhost: 3929 PCSAFS130: Node 172.18.4.22 connection
    closed
    Jan 21 07:26:26 localhost: 3930 PCSAFS130: Node 172.18.4.35 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:26:26 localhost: 3930 PCSAFS130: Node 172.18.4.35 connection
    closed
    Jan 21 07:26:36 localhost: 3931 PCSAFS130: Node 172.18.4.35 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:26:36 localhost: 3931 PCSAFS130: Node 172.18.4.35 connection
    closed
    Jan 21 07:27:27 localhost: 3939 PCSAFS130: Starting server with 10.639
    and netbi
    os name PC639
    Jan 21 07:27:27 localhost: 3939 PCSAFS130: Connect 12 Session 203 
    start on node
     10.639 user pcguest for service ccm
    Jan 21 07:27:28 localhost: 3939 PCSAFS130: Connect 13 Session 203 
    start on node
     10.639 user pcguest for service ccd
    Jan 21 07:28:15 localhost: 3936 PCSAFS130: Node 172.18.4.35 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:28:15 localhost: 3936 PCSAFS130: Node 172.18.4.35 connection
    closed
    Jan 21 07:28:21 localhost: 3937 PCSAFS130: Node 172.18.4.22 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:28:21 localhost: 3937 PCSAFS130: Node 172.18.4.22 connection
    closed
    Jan 21 07:28:25 localhost: 3938 PCSAFS130: Node 172.18.4.35 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:28:25 localhost: 3938 PCSAFS130: Node 172.18.4.35 connection
    closed
    Jan 21 07:28:31 localhost: 3940 PCSAFS130: Node 172.18.4.22 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:28:31 localhost: 3940 PCSAFS130: Node 172.18.4.22 connection
    closed
    Jan 21 07:29:18 localhost: 3942 PCSAFS130: Node 172.18.4.35 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:29:18 localhost: 3942 PCSAFS130: Node 172.18.4.35 connection
    closed
    Jan 21 07:32:13 localhost: 3950 PCSAFS130: Node 172.18.4.32 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:32:13 localhost: 3950 PCSAFS130: Node 172.18.4.32 connection
    closed
    Jan 21 07:34:54 localhost: 3953 PCSAFS130: Node 172.18.4.55 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:34:54 localhost: 3953 PCSAFS130: Node 172.18.4.55 connection
    closed
    Jan 21 07:35:04 localhost: 3954 PCSAFS130: Node 172.18.4.55 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:35:04 localhost: 3954 PCSAFS130: Node 172.18.4.55 connection
    closed
    Jan 21 07:35:18 localhost: 3962 PCSAFS130: Starting server with 10.251
    and netbi
    os name PC251
    Jan 21 07:35:18 localhost: 3962 PCSAFS130: Connect 15 Session 212 
    start on node
     10.251 user pcguest for service ccd
    Jan 21 07:35:37 localhost: 3955 PCSAFS130: Node 172.18.4.32 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:35:37 localhost: 3955 PCSAFS130: Node 172.18.4.32 connection
    closed
    Jan 21 07:35:40 localhost: 3965 PCSAFS130: Starting server with 10.369
    and netbi
    os name PC369
    Jan 21 07:35:40 localhost: 3965 PCSAFS130: Connect 16 Session 214 
    start on node
     10.369 user pcguest for service netc_data
    Jan 21 07:35:41 localhost: 3966 PCSAFS130: Starting server with 10.370
    and netbi
    os name PC370
    Jan 21 07:35:41 localhost: 3966 PCSAFS130: Connect 17 Session 215 
    start on node
     10.370 user pcguest for service netc_data
    
    Jan 21 07:35:42 localhost: 3965 PCSAFS130: Client 10.369 user pcguest
    stopped co
    nnection tid 16
    Jan 21 07:35:42 localhost: 3965 PCSAFS130: Node 10.369 connection
    closed
    Jan 21 07:35:43 localhost: 3966 PCSAFS130: Client 10.370 user pcguest
    stopped co
    nnection tid 17
    Jan 21 07:35:43 localhost: 3966 PCSAFS130: Node 10.370 connection
    closed
    Jan 21 07:35:47 localhost: 3956 PCSAFS130: Node 172.18.4.32 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:35:47 localhost: 3956 PCSAFS130: Node 172.18.4.32 connection
    closed
    Jan 21 07:35:51 localhost: 3939 PCSAFS130: Connect 16 Session 203 
    start on node
     10.639 user pcguest for service win_excel
    Jan 21 07:35:57 localhost: 3958 PCSAFS130: Node 172.18.4.55 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:35:57 localhost: 3958 PCSAFS130: Node 172.18.4.55 connection
    closed
    Jan 21 07:36:07 localhost: 3960 PCSAFS130: Node 172.18.4.55 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:36:07 localhost: 3960 PCSAFS130: Node 172.18.4.55 connection
    closed
    Jan 21 07:36:13 localhost: 3961 PCSAFS130: Node 172.18.4.53 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:36:13 localhost: 3961 PCSAFS130: Node 172.18.4.53 connection
    closed
    Jan 21 07:36:23 localhost: 3963 PCSAFS130: Node 172.18.4.53 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:36:23 localhost: 3963 PCSAFS130: Node 172.18.4.53 connection
    closed
    Jan 21 07:37:05 localhost: 3969 PCSAFS130: Node 172.18.4.39 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:37:06 localhost: 3969 PCSAFS130: Node 172.18.4.39 connection
    closed
    Jan 21 07:37:16 localhost: 3972 PCSAFS130: Node 172.18.4.39 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:37:16 localhost: 3972 PCSAFS130: Node 172.18.4.39 connection
    closed
    Jan 21 07:37:44 localhost: 3974 PCSAFS130: Node 172.18.4.43 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:37:44 localhost: 3974 PCSAFS130: Node 172.18.4.43 connection
    closed
    Jan 21 07:37:54 localhost: 3975 PCSAFS130: Node 172.18.4.43 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:37:54 localhost: 3975 PCSAFS130: Node 172.18.4.43 connection
    closed
    Jan 21 07:38:05 localhost: 3981 PCSAFS130: Starting server with 10.370
    and netbi
    os name PC370
    Jan 21 07:38:05 localhost: 3981 PCSAFS130: Connect 17 Session 228 
    start on node
     10.370 user pcguest for service ccd
    Jan 21 07:38:40 localhost: 3978 PCSAFS130: Node 172.18.4.53 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:38:40 localhost: 3978 PCSAFS130: Node 172.18.4.53 connection
    closed
    Jan 21 07:39:22 localhost: 3984 PCSAFS130: Starting server with 10.684
    and netbi
    os name PC684
    Jan 21 07:39:22 localhost: 3984 PCSAFS130: Connect 18 Session 234 
    start on node
     10.684 user pcguest for service ccm
    Jan 21 07:39:23 localhost: 3984 PCSAFS130: Connect 19 Session 234 
    start on node
     10.684 user pcguest for service ccd
    Jan 21 07:40:02 localhost: 3983 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:40:02 localhost: 3983 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:40:47 localhost: 3985 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:40:47 localhost: 3985 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:40:53 localhost: 3986 PCSAFS130: Node 172.18.4.34 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:40:53 localhost: 3986 PCSAFS130: Node 172.18.4.34 connection
    closed
    Jan 21 07:41:44 localhost: 3991 PCSAFS130: Starting server with 10.787
    and netbi
    os name PC787
    Jan 21 07:41:44 localhost: 3991 PCSAFS130: Connect 20 Session 239 
    start on node
     10.787 user pcguest for service ccm
    Jan 21 07:41:45 localhost: 3991 PCSAFS130: Connect 21 Session 239 
    start on node
     10.787 user pcguest for service ccd
    Jan 21 07:42:01 localhost: 3990 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:42:01 localhost: 3990 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:42:04 localhost: 742 PCSAFS130: Connect 22 Session 338  start
    on node 
    172.18.4.28 user pcguest for service win_excel
    Jan 21 07:42:16 localhost: 742 PCSAFS130: Client 172.18.4.28 user
    pcguest stoppe
    d connection tid 22
    Jan 21 07:42:46 localhost: 3992 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:42:46 localhost: 3992 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:44:47 localhost: 3995 PCSAFS130: Node 172.18.4.9 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 07:44:47 localhost: 3995 PCSAFS130: Node 172.18.4.9 connection
    closed
    Jan 21 07:45:09 localhost: 3996 PCSAFS130: Node 172.18.4.154 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 07:45:09 localhost: 3996 PCSAFS130: Node 172.18.4.154 connection
    closed
    Jan 21 07:45:12 localhost: 3997 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:45:12 localhost: 3997 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:45:19 localhost: 3998 PCSAFS130: Node 172.18.4.154 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 07:45:19 localhost: 3998 PCSAFS130: Node 172.18.4.154 connection
    closed
    Jan 21 07:45:57 localhost: 4000 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:45:57 localhost: 4000 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:46:32 localhost: 4014 PCSAFS130: Starting server with 10.369
    and netbi
    os name PC369
    Jan 21 07:46:32 localhost: 4014 PCSAFS130: Connect 22 Session 251 
    start on node
     10.369 user pcguest for service ccd
    Jan 21 07:46:32 localhost: 4007 PCSAFS130: Node 172.18.4.0 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 07:46:32 localhost: 4007 PCSAFS130: Node 172.18.4.0 connection
    closed
    Jan 21 07:46:36 localhost: 4016 PCSAFS130: Starting server with 10.638
    and netbi
    os name MODEM1
    Jan 21 07:46:36 localhost: 4016 PCSAFS130: Connect 23 Session 253 
    start on node
     10.638 user pcguest for service ccm
    Jan 21 07:46:36 localhost: 4016 PCSAFS130: Connect 24 Session 253 
    start on node
     10.638 user pcguest for service ccd
    Jan 21 07:46:38 localhost: 4008 PCSAFS130: Node 172.18.4.15 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:46:38 localhost: 4008 PCSAFS130: Node 172.18.4.15 connection
    closed
    Jan 21 07:46:42 localhost: 4009 PCSAFS130: Node 172.18.4.0 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 07:46:43 localhost: 4009 PCSAFS130: Node 172.18.4.0 connection
    closed
    Jan 21 07:46:48 localhost: 4010 PCSAFS130: Starting server with
    172.18.4.15 and 
    netbios name PC663
    Jan 21 07:46:51 localhost: 4011 PCSAFS130: Node 172.18.4.39 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:46:51 localhost: 4011 PCSAFS130: Node 172.18.4.39 connection
    closed
    Jan 21 07:46:55 localhost: 4010 PCSAFS130: Node 172.18.4.15 connection
    closed
    Jan 21 07:47:00 localhost: 4022 PCSAFS130: Starting server with 10.811
    and netbi
    os name PC811
    Jan 21 07:47:00 localhost: 4022 PCSAFS130: Connect 25 Session 258 
    start on node
     10.811 user pcguest for service netc_data
    Jan 21 07:47:01 localhost: 4013 PCSAFS130: Node 172.18.4.39 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:47:01 localhost: 4013 PCSAFS130: Node 172.18.4.39 connection
    closed
    Jan 21 07:47:03 localhost: 4022 PCSAFS130: Client 10.811 user pcguest
    stopped co
    nnection tid 25
    Jan 21 07:47:03 localhost: 4022 PCSAFS130: Node 10.811 connection
    closed
    Jan 21 07:47:17 localhost: 4026 PCSAFS130: Starting server with 10.811
    and netbi
    os name PC811
    Jan 21 07:47:17 localhost: 4026 PCSAFS130: Connect 25 Session 261 
    start on node
     10.811 user pcguest for service ccd
    Jan 21 07:47:39 localhost: 4018 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:47:39 localhost: 4018 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:47:49 localhost: 4020 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:47:49 localhost: 4020 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:48:02 localhost: 4024 telnetd: Connect from 172.18.4.29
    Jan 21 07:48:02 localhost: 4024 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 07:48:05 localhost: 4025 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:48:05 localhost: 4025 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:48:18 localhost: 4027 PCSAFS130: Node 172.18.4.42 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:48:18 localhost: 4027 PCSAFS130: Node 172.18.4.42 connection
    closed
    Jan 21 07:48:19 localhost: 4038 PCSAFS130: Starting server with 10.379
    and netbi
    os name PC379
    Jan 21 07:48:19 localhost: 4038 PCSAFS130: Connect 26 Session 267 
    start on node
     10.379 user pcguest for service ccm
    Jan 21 07:48:19 localhost: 4038 PCSAFS130: Connect 27 Session 267 
    start on node
     10.379 user pcguest for service ccd
    Jan 21 07:48:28 localhost: 4028 PCSAFS130: Node 172.18.4.42 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:48:28 localhost: 4028 PCSAFS130: Node 172.18.4.42 connection
    closed
    Jan 21 07:48:29 localhost: 4029 PCSAFS130: Node 172.18.4.22 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:48:29 localhost: 4029 PCSAFS130: Node 172.18.4.22 connection
    closed
    Jan 21 07:48:34 localhost: 4030 PCSAFS130: Node 172.18.4.49 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:48:34 localhost: 4030 PCSAFS130: Node 172.18.4.49 connection
    closed
    Jan 21 07:48:44 localhost: 4032 PCSAFS130: Node 172.18.4.49 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:48:44 localhost: 4032 PCSAFS130: Node 172.18.4.49 connection
    closed
    Jan 21 07:49:07 localhost: 4035 telnetd: Connect from 172.18.4.29
    Jan 21 07:49:07 localhost: 4035 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 07:49:07 localhost: 4046 PCSAFS130: Starting server with 10.671
    and netbi
    os name PC671
    Jan 21 07:49:07 localhost: 4046 PCSAFS130: Connect 28 Session 272 
    start on node
     10.671 user pcguest for service ccm
    Jan 21 07:49:08 localhost: 4046 PCSAFS130: Connect 29 Session 272 
    start on node
     10.671 user pcguest for service ccd
    Jan 21 07:49:09 localhost: 4036 PCSAFS130: Node 172.18.4.49 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:49:09 localhost: 4036 PCSAFS130: Node 172.18.4.49 connection
    closed
    Jan 21 07:49:20 localhost: 4048 PCSAFS130: Starting server with 10.791
    and netbi
    os name 10.998
    Jan 21 07:49:20 localhost: 4048 PCSAFS130: Connect 30 Session 274 
    start on node
     10.791 user pcguest for service ccm
    Jan 21 07:49:21 localhost: 4039 PCSAFS130: Starting server with
    172.18.4.15 and 
    netbios name PC663
    Jan 21 07:49:21 localhost: 4048 PCSAFS130: Connect 31 Session 274 
    start on node
     10.791 user pcguest for service ccd
    Jan 21 07:49:40 localhost: 4043 telnetd: Connect from 172.18.4.29
    Jan 21 07:49:40 localhost: 4043 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 07:49:57 localhost: 4045 telnetd: Connect from 172.18.4.29
    Jan 21 07:49:57 localhost: 4045 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 07:50:23 localhost: 4049 PCSAFS130: Node 172.18.4.23 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:50:23 localhost: 4049 PCSAFS130: Node 172.18.4.23 connection
    closed
    Jan 21 07:50:25 localhost: 4050 telnetd: Connect from 172.18.4.29
    Jan 21 07:50:25 localhost: 4050 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 07:50:33 localhost: 4051 PCSAFS130: Node 172.18.4.23 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:50:33 localhost: 4051 PCSAFS130: Node 172.18.4.23 connection
    closed
    Jan 21 07:51:01 localhost: 4052 PCSAFS130: Node 172.18.4.23 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:01 localhost: 4052 PCSAFS130: Node 172.18.4.23 connection
    closed
    Jan 21 07:51:06 localhost: 4053 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:06 localhost: 4053 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:51:21 localhost: 4054 PCSAFS130: Node 172.18.4.49 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:21 localhost: 4054 PCSAFS130: Node 172.18.4.49 connection
    closed
    Jan 21 07:51:31 localhost: 4056 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:31 localhost: 4056 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:51:31 localhost: 4057 PCSAFS130: Node 172.18.4.49 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:31 localhost: 4057 PCSAFS130: Node 172.18.4.49 connection
    closed
    Jan 21 07:51:45 localhost: 4059 PCSAFS130: Node 172.18.4.37 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:45 localhost: 4059 PCSAFS130: Node 172.18.4.37 connection
    closed
    Jan 21 07:51:47 localhost: 4060 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:47 localhost: 4060 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:51:53 localhost: 4061 PCSAFS130: Node 172.18.4.25 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:53 localhost: 4061 PCSAFS130: Node 172.18.4.25 connection
    closed
    Jan 21 07:51:55 localhost: 4062 PCSAFS130: Node 172.18.4.37 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:51:55 localhost: 4062 PCSAFS130: Node 172.18.4.37 connection
    closed
    Jan 21 07:52:14 localhost: 4075 PCSAFS130: Starting server with 10.994
    and netbi
    os name PC994
    Jan 21 07:52:14 localhost: 4075 PCSAFS130: Connect 33 Session 298 
    start on node
     10.994 user pcguest for service netc_data
    Jan 21 07:52:18 localhost: 4075 PCSAFS130: Client 10.994 user pcguest
    stopped co
    nnection tid 33
    Jan 21 07:52:18 localhost: 4075 PCSAFS130: Node 10.994 connection
    closed
    Jan 21 07:52:41 localhost: 4068 telnetd: Connect from 172.18.4.29
    Jan 21 07:52:41 localhost: 4068 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 07:52:49 localhost: 4071 PCSAFS130: Node 172.18.4.57 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:52:49 localhost: 4071 PCSAFS130: Node 172.18.4.57 connection
    closed
    Jan 21 07:52:49 localhost: 4078 PCSAFS130: Starting server with 10.994
    and netbi
    os name PC994
    Jan 21 07:52:49 localhost: 4078 PCSAFS130: Connect 33 Session 300 
    start on node
     10.994 user pcguest for service ccd
    Jan 21 07:52:51 localhost: 4078 PCSAFS130: Connect 34 Session 300 
    start on node
     10.994 user pcguest for service netc_data
    Jan 21 07:52:55 localhost: 4078 PCSAFS130: Client 10.994 user pcguest
    stopped co
    nnection tid 34
    Jan 21 07:52:59 localhost: 4079 PCSAFS130: Starting server with 10.745
    and netbi
    os name PC745
    Jan 21 07:52:59 localhost: 4074 PCSAFS130: Node 172.18.4.57 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:52:59 localhost: 4079 PCSAFS130: Connect 34 Session 305 
    start on node
     10.745 user pcguest for service vscan
    Jan 21 07:52:59 localhost: 4074 PCSAFS130: Node 172.18.4.57 connection
    closed
    Jan 21 07:53:29 localhost: 4048 PCSAFS130: Client 10.791 user pcguest
    stopped co
    nnection tid 30
    Jan 21 07:53:29 localhost: 4048 PCSAFS130: Client 10.791 user pcguest
    stopped co
    nnection tid 31
    Jan 21 07:53:29 localhost: 4048 PCSAFS130: Node 10.791 connection
    closed
    Jan 21 07:53:42 localhost: 4076 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:53:42 localhost: 4076 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 07:53:47 localhost: 4082 PCSAFS130: Starting server with 10.791
    and netbi
    os name 10.998
    Jan 21 07:53:47 localhost: 4082 PCSAFS130: Connect 30 Session 308 
    start on node
     10.791 user pcguest for service ccm
    Jan 21 07:53:48 localhost: 4082 PCSAFS130: Connect 31 Session 308 
    start on node
     10.791 user pcguest for service ccd
    Jan 21 07:54:36 localhost: 4039 PCSAFS130: Node 172.18.4.15 connection
    closed
    Jan 21 07:55:10 localhost: 4083 PCSAFS130: Node 172.18.4.67 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:55:10 localhost: 4083 PCSAFS130: Node 172.18.4.67 connection
    closed
    Jan 21 07:55:19 localhost: 4084 telnetd: Connect from 172.18.4.29
    Jan 21 07:55:20 localhost: 4085 PCSAFS130: Node 172.18.4.67 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:55:20 localhost: 4085 PCSAFS130: Node 172.18.4.67 connection
    closed
    Jan 21 07:55:31 localhost: 4092 PCSAFS130: Starting server with 10.102
    and netbi
    os name PC102
    Jan 21 07:55:31 localhost: 4092 PCSAFS130: Connect 35 Session 311 
    start on node
     10.102 user pcguest for service netc_data
    Jan 21 07:55:32 localhost: 4092 PCSAFS130: Client 10.102 user pcguest
    stopped co
    nnection tid 35
    Jan 21 07:55:33 localhost: 4092 PCSAFS130: Node 10.102 connection
    closed
    Jan 21 07:55:56 localhost: 4086 PCSAFS130: Node 172.18.4.57 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:55:56 localhost: 4086 PCSAFS130: Node 172.18.4.57 connection
    closed
    Jan 21 07:56:06 localhost: 4087 PCSAFS130: Node 172.18.4.57 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:56:06 localhost: 4087 PCSAFS130: Node 172.18.4.57 connection
    closed
    Jan 21 07:56:29 localhost: 4091 PCSAFS130: Node 172.18.4.77 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:56:29 localhost: 4091 PCSAFS130: Node 172.18.4.77 connection
    closed
    Jan 21 07:56:32 localhost: 4093 PCSAFS130: Node 172.18.4.67 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:56:32 localhost: 4093 PCSAFS130: Node 172.18.4.67 connection
    closed
    Jan 21 07:56:32 localhost: 4094 PCSAFS130: Node 172.18.4.53 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:56:32 localhost: 4094 PCSAFS130: Node 172.18.4.53 connection
    closed
    Jan 21 07:56:40 localhost: 4095 PCSAFS130: Node 172.18.4.46 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:56:40 localhost: 4095 PCSAFS130: Node 172.18.4.46 connection
    closed
    Jan 21 07:56:41 localhost: 4106 PCSAFS130: Starting server with 10.789
    and netbi
    os name PC789
    Jan 21 07:56:41 localhost: 4106 PCSAFS130: Connect 35 Session 327 
    start on node
     10.789 user pcguest for service ccm
    Jan 21 07:56:42 localhost: 4106 PCSAFS130: Connect 36 Session 327 
    start on node
     10.789 user pcguest for service ccd
    Jan 21 07:56:42 localhost: 4096 PCSAFS130: Node 172.18.4.67 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:56:42 localhost: 4096 PCSAFS130: Node 172.18.4.67 connection
    closed
    Jan 21 07:56:53 localhost: 4108 PCSAFS130: Starting server with 10.102
    and netbi
    os name PC102
    Jan 21 07:56:53 localhost: 4108 PCSAFS130: Connect 37 Session 329 
    start on node
     10.102 user pcguest for service ccd
    Jan 21 07:57:02 localhost: 4079 PCSAFS130: Client 10.745 user pcguest
    stopped co
    nnection tid 34
    Jan 21 07:57:02 localhost: 4079 PCSAFS130: Node 10.745 connection
    closed
    Jan 21 07:57:02 localhost: 4109 PCSAFS130: Starting server with 10.745
    and netbi
    os name PC745
    Jan 21 07:57:02 localhost: 4109 PCSAFS130: Connect 34 Session 331 
    start on node
     10.745 user pcguest for service netc_data
    Jan 21 07:57:05 localhost: 4098 PCSAFS130: Node 172.18.4.22 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:57:05 localhost: 4098 PCSAFS130: Node 172.18.4.22 connection
    closed
    Jan 21 07:57:06 localhost: 4109 PCSAFS130: Client 10.745 user pcguest
    stopped co
    nnection tid 34
    Jan 21 07:57:06 localhost: 4109 PCSAFS130: Node 10.745 connection
    closed
    Jan 21 07:57:18 localhost: 4100 PCSAFS130: Node 172.18.4.15 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:57:18 localhost: 4100 PCSAFS130: Node 172.18.4.15 connection
    closed
    Jan 21 07:57:28 localhost: 4101 PCSAFS130: Node 172.18.4.15 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:57:28 localhost: 4101 PCSAFS130: Node 172.18.4.15 connection
    closed
    Jan 21 07:57:45 localhost: 4084 telnetd: Connection closed from host
    172.18.4.29
    Jan 21 07:58:17 localhost: 4111 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:58:17 localhost: 4111 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:58:39 localhost: 4106 PCSAFS130: Connect 34 Session 327 
    start on node
     10.789 user pcguest for service win_word
    Jan 21 07:58:44 localhost: 4082 PCSAFS130: Client 10.791 user pcguest
    stopped co
    nnection tid 30
    Jan 21 07:58:44 localhost: 4082 PCSAFS130: Client 10.791 user pcguest
    stopped co
    nnection tid 31
    Jan 21 07:58:44 localhost: 4082 PCSAFS130: Node 10.791 connection
    closed
    Jan 21 07:58:54 localhost: 4114 telnetd: Connect from 172.18.4.29
    Jan 21 07:58:54 localhost: 4114 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 07:59:00 localhost: 4119 PCSAFS130: Starting server with 10.791
    and netbi
    os name 10.998
    Jan 21 07:59:01 localhost: 4119 PCSAFS130: Connect 30 Session 339 
    start on node
     10.791 user pcguest for service ccm
    Jan 21 07:59:01 localhost: 4119 PCSAFS130: Connect 31 Session 339 
    start on node
     10.791 user pcguest for service ccd
    Jan 21 07:59:02 localhost: 4115 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:59:02 localhost: 4115 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 07:59:36 localhost: 4117 PCSAFS130: Node 172.18.4.67 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:59:36 localhost: 4117 PCSAFS130: Node 172.18.4.67 connection
    closed
    Jan 21 07:59:46 localhost: 4118 PCSAFS130: Node 172.18.4.67 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 07:59:46 localhost: 4118 PCSAFS130: Node 172.18.4.67 connection
    closed
    Jan 21 08:00:05 localhost: 4038 PCSAFS130: Connect 38 Session 267 
    start on node
     10.379 user pcguest for service win_word
    Jan 21 08:00:10 localhost: 4128 PCSAFS130: Starting server with 10.743
    and netbi
    os name PC743
    Jan 21 08:00:10 localhost: 4128 PCSAFS130: Connect 39 Session 345 
    start on node
     10.743 user pcguest for service netc_data
    Jan 21 08:00:12 localhost: 4128 PCSAFS130: Client 10.743 user pcguest
    stopped co
    nnection tid 39
    Jan 21 08:00:12 localhost: 4128 PCSAFS130: Node 10.743 connection
    closed
    Jan 21 08:00:24 localhost: 4129 PCSAFS130: Starting server with 10.745
    and netbi
    os name PC745
    Jan 21 08:00:24 localhost: 4129 PCSAFS130: Connect 39 Session 346 
    start on node
     10.745 user pcguest for service ccd
    Jan 21 08:00:26 localhost: 4129 PCSAFS130: Connect 40 Session 346 
    start on node
     10.745 user pcguest for service netc_data
    Jan 21 08:00:28 localhost: 4129 PCSAFS130: Client 10.745 user pcguest
    stopped co
    nnection tid 40
    Jan 21 08:00:29 localhost: 4130 PCSAFS130: Starting server with 10.743
    and netbi
    os name PC743
    Jan 21 08:00:29 localhost: 4130 PCSAFS130: Connect 40 Session 347 
    start on node
     10.743 user pcguest for service ccd
    Jan 21 08:00:36 localhost: 4122 telnetd: Connect from 172.18.4.29
    Jan 21 08:00:36 localhost: 4122 telnetd: ttloop:  peer died: Connection
    timed ou
    t
    Jan 21 08:01:04 localhost: 4127 PCSAFS130: Node 172.18.4.33 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:01:04 localhost: 4127 PCSAFS130: Node 172.18.4.33 connection
    closed
    Jan 21 08:01:32 localhost: 4131 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:01:32 localhost: 4131 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 08:01:47 localhost: 4139 PCSAFS130: Starting server with 10.185
    and netbi
    os name PC185
    Jan 21 08:01:47 localhost: 4139 PCSAFS130: Connect 41 Session 353 
    start on node
     10.185 user pcguest for service ccm
    Jan 21 08:01:48 localhost: 4139 PCSAFS130: Connect 42 Session 353 
    start on node
     10.185 user pcguest for service ccd
    Jan 21 08:02:17 localhost: 4133 PCSAFS130: Node 172.18.4.29 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:02:17 localhost: 4133 PCSAFS130: Node 172.18.4.29 connection
    closed
    Jan 21 08:02:18 localhost: 4134 PCSAFS130: Node 172.18.4.57 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:02:18 localhost: 4134 PCSAFS130: Node 172.18.4.57 connection
    closed
    Jan 21 08:02:28 localhost: 4135 PCSAFS130: Node 172.18.4.57 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:02:28 localhost: 4135 PCSAFS130: Node 172.18.4.57 connection
    closed
    Jan 21 08:02:31 localhost: 4136 PCSAFS130: Node 172.18.4.13 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:02:32 localhost: 4136 PCSAFS130: Node 172.18.4.13 connection
    closed
    Jan 21 08:02:42 localhost: 4138 PCSAFS130: Node 172.18.4.13 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:02:42 localhost: 4138 PCSAFS130: Node 172.18.4.13 connection
    closed
    Jan 21 08:02:58 localhost: 4140 PCSAFS130: Node 172.18.4.149 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 08:02:58 localhost: 4140 PCSAFS130: Node 172.18.4.149 connection
    closed
    Jan 21 08:03:08 localhost: 4141 PCSAFS130: Node 172.18.4.149 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 08:03:08 localhost: 4141 PCSAFS130: Node 172.18.4.149 connection
    closed
    Jan 21 08:03:31 localhost: 4147 PCSAFS130: Node 172.18.4.149 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 08:03:31 localhost: 4147 PCSAFS130: Node 172.18.4.149 connection
    closed
    Jan 21 08:03:33 localhost: 4149 PCSAFS130: Node 172.18.4.38 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:03:33 localhost: 4149 PCSAFS130: Node 172.18.4.38 connection
    closed
    Jan 21 08:03:39 localhost: 4150 PCSAFS130: Node 172.18.0.8 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 08:03:39 localhost: 4150 PCSAFS130: Node 172.18.0.8 connection
    closed
    Jan 21 08:03:44 localhost: 4152 PCSAFS130: Node 172.18.4.38 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:03:44 localhost: 4152 PCSAFS130: Node 172.18.4.38 connection
    closed
    Jan 21 08:03:57 localhost: 4155 PCSAFS130: Starting server with
    172.18.4.38 and 
    netbios name PC664
    Jan 21 08:04:06 localhost: 4157 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:04:07 localhost: 4157 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 08:04:17 localhost: 4161 PCSAFS130: Node 172.18.4.45 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:04:17 localhost: 4161 PCSAFS130: Node 172.18.4.45 connection
    closed
    Jan 21 08:04:24 localhost: 4162 PCSAFS130: Node 172.18.0.8 terminated
    by Broken 
    pipe signal at pc 431548
    Jan 21 08:04:25 localhost: 4162 PCSAFS130: Node 172.18.0.8 connection
    closed
    Jan 21 08:05:08 localhost: 4168 PCSAFS130: Node 172.18.4.77 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:05:08 localhost: 4168 PCSAFS130: Node 172.18.4.77 connection
    closed
    Jan 21 08:05:14 localhost: 4171 PCSAFS130: Node 172.18.4.63 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:05:14 localhost: 4171 PCSAFS130: Node 172.18.4.63 connection
    closed
    Jan 21 08:05:24 localhost: 4175 PCSAFS130: Node 172.18.4.63 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:05:25 localhost: 4175 PCSAFS130: Node 172.18.4.63 connection
    closed
    Jan 21 08:05:40 localhost: 4178 PCSAFS130: Node 172.18.4.78 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:05:40 localhost: 4178 PCSAFS130: Node 172.18.4.78 connection
    closed
    Jan 21 08:06:42 localhost: 4185 PCSAFS130: Node 172.18.4.103 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 08:06:42 localhost: 4185 PCSAFS130: Node 172.18.4.103 connection
    closed
    Jan 21 08:06:52 localhost: 4186 PCSAFS130: Node 172.18.4.103 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 08:06:52 localhost: 4186 PCSAFS130: Node 172.18.4.103 connection
    closed
    Jan 21 08:06:53 localhost: 4139 PCSAFS130: Connect 43 Session 353 
    start on node
     10.185 user pcguest for service win_wp52
    Jan 21 08:07:00 localhost: 4187 PCSAFS130: Node 172.18.4.37 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:07:00 localhost: 4187 PCSAFS130: Node 172.18.4.37 connection
    closed
    Jan 21 08:07:04 localhost: 4188 PCSAFS130: Node 172.18.4.47 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:07:04 localhost: 4188 PCSAFS130: Node 172.18.4.47 connection
    closed
    Jan 21 08:07:14 localhost: 4189 PCSAFS130: Node 172.18.4.47 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:07:14 localhost: 4189 PCSAFS130: Node 172.18.4.47 connection
    closed
    Jan 21 08:07:24 localhost: 4190 PCSAFS130: Node 172.18.4.47 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:07:24 localhost: 4190 PCSAFS130: Node 172.18.4.47 connection
    closed
    Jan 21 08:07:37 localhost: 4204 PCSAFS130: Starting server with 10.295
    and netbi
    os name PC295
    Jan 21 08:07:37 localhost: 4204 PCSAFS130: Connect 44 Session 391 
    start on node
     10.295 user pcguest for service netc_data
    Jan 21 08:07:39 localhost: 4204 PCSAFS130: Client 10.295 user pcguest
    stopped co
    nnection tid 44
    Jan 21 08:07:39 localhost: 4204 PCSAFS130: Node 10.295 connection
    closed
    Jan 21 08:07:41 localhost: 4191 PCSAFS130: Node 172.18.4.47 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:07:41 localhost: 4191 PCSAFS130: Node 172.18.4.47 connection
    closed
    Jan 21 08:07:50 localhost: 4193 PCSAFS130: Node 172.18.4.44 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:07:50 localhost: 4193 PCSAFS130: Node 172.18.4.44 connection
    closed
    Jan 21 08:07:51 localhost: 4194 PCSAFS130: Node 172.18.4.47 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:07:51 localhost: 4194 PCSAFS130: Node 172.18.4.47 connection
    closed
    Jan 21 08:07:58 localhost: 4196 PCSAFS130: Node 172.18.4.103 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 08:07:58 localhost: 4196 PCSAFS130: Node 172.18.4.103 connection
    closed
    Jan 21 08:08:00 localhost: 3390 telnetd: Connection closed from host
    pc8056.trim
    et.org
    Jan 21 08:08:00 localhost: 4198 PCSAFS130: Node 172.18.4.44 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:08:00 localhost: 4198 PCSAFS130: Node 172.18.4.44 connection
    closed
    Jan 21 08:08:08 localhost: 4200 PCSAFS130: Node 172.18.4.103 terminated
    by Broke
    n pipe signal at pc 431548
    Jan 21 08:08:08 localhost: 4200 PCSAFS130: Node 172.18.4.103 connection
    closed
    Jan 21 08:08:31 localhost: 4129 PCSAFS130: Node 10.745 connection
    closed
    Jan 21 08:09:20 localhost: 4218 PCSAFS130: Starting server with 10.181
    and netbi
    os name PC181
    Jan 21 08:09:20 localhost: 4218 PCSAFS130: Connect 39 Session 403 
    start on node
     10.181 user pcguest for service ccm
    Jan 21 08:09:21 localhost: 4218 PCSAFS130: Connect 44 Session 403 
    start on node
     10.181 user pcguest for service ccd
    Jan 21 08:09:36 localhost: 4223 PCSAFS130: Starting server with 10.680
    and netbi
    os name PC680
    Jan 21 08:09:36 localhost: 4223 PCSAFS130: Connect 45 Session 404 
    start on node
     10.680 user pcguest for service ccm
    Jan 21 08:09:37 localhost: 4223 PCSAFS130: Connect 46 Session 404 
    start on node
     10.680 user pcguest for service ccd
    Jan 21 08:09:41 localhost: 4225 PCSAFS130: Starting server with 10.745
    and netbi
    os name PC745
    Jan 21 08:09:41 localhost: 4225 PCSAFS130: Connect 47 Session 405 
    start on node
     10.745 user pcguest for service ccd
    Jan 21 08:10:21 localhost: 4219 PCSAFS130: Node 172.18.4.68 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:10:21 localhost: 4219 PCSAFS130: Node 172.18.4.68 connection
    closed
    Jan 21 08:10:22 localhost: 4220 PCSAFS130: Node 172.18.4.81 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:10:22 localhost: 4220 PCSAFS130: Node 172.18.4.81 connection
    closed
    Jan 21 08:10:32 localhost: 4221 PCSAFS130: Node 172.18.4.68 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:10:32 localhost: 4221 PCSAFS130: Node 172.18.4.68 connection
    closed
    Jan 21 08:10:32 localhost: 4222 PCSAFS130: Node 172.18.4.81 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:10:32 localhost: 4222 PCSAFS130: Node 172.18.4.81 connection
    closed
    Jan 21 08:10:52 localhost: 4226 PCSAFS130: Node 172.18.4.74 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:10:52 localhost: 4226 PCSAFS130: Node 172.18.4.74 connection
    closed
    Jan 21 08:11:02 localhost: 4227 PCSAFS130: Node 172.18.4.74 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:11:02 localhost: 4227 PCSAFS130: Node 172.18.4.74 connection
    closed
    
                            here, I stopped and restarted pathworks
                            (pscsamgr)
    
    Jan 21 08:11:26 syslog: shutdown within 30 seconds
    Jan 21 08:11:26 localhost: 4230 PCSAFS130: Node 172.18.4.74 terminated
    by Broken
     pipe signal at pc 431548
    Jan 21 08:11:27 localhost: 4230 PCSAFS130: Node 172.18.4.74 connection
    closed
    Jan 21 08:11:28 localhost: 166 snmpd: Exit snmpd at Tue Jan 21 08:11:27
    1997
    Jan 21 08:12:44 syslog restart
    Jan 21 08:12:45 localhost: 127 PCSAFS130: Starting server with 10.689
    and netbio
    s name PC689
    Jan 21 08:12:45 localhost: 127 PCSAFS130: Unable to open pcsafs message
    queue - 
    No such file or directory
    Jan 21 08:12:45 localhost: 129 PCSAFS130: Starting server with 10.689
    and netbio
    s name PC689
    Jan 21 08:12:45 localhost: 129 PCSAFS130: Unable to open pcsafs message
    queue - 
    No such file or directory
    Jan 21 08:12:46 localhost: 144 PCSAFS130: Starting server with 10.689
    and netbio
    s name PC689
    Jan 21 08:12:46 localhost: 144 PCSAFS130: Unable to open pcsafs message
    queue - 
    No such file or directory
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Server started
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of sess_info  40 * 512 
    = 20480
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of tid_info  216 *
    2048  = 4423
    68
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of file_data_base  124
    * 2048 =
     253952
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of server_statistics 
    48
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of server_common  36
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of lanman_ini  316
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of unique open file
    table 24 * 
    2048 = 49152
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Size of server lock table
    20 * 2048 
    = 40960
    Jan 21 08:12:46 localhost: 145 PCSAADMD130: Total shared memory size =
    807312
    Jan 21 08:12:47 localhost: 150 PCSANBUD130: Starting NetBIOS Utilities
    (PCSANBUD
    ) V1.1 
    Jan 21 08:12:47 localhost: 150 PCSANBUD130: DLI/DECnet ethernet
    controller: ln0
    Jan 21 08:12:47 localhost: 150 PCSANBUD130: UDP/TCP Transport Avaliable
    Jan 21 08:12:47 localhost: 150 PCSANBUD130: DLI/DECnet Transport
    Avaliable
    Jan 21 08:12:48 localhost: 150 PCSANBUD130: Scope[0] = (null)
    Jan 21 08:12:48 localhost: 174 snmpd: Start snmpd version 3.2 at Tue
    Jan 21 08:1
    2:48 1997
    Jan 21 08:12:48 localhost: 174 snmpd: warning: scs_system_id not found
    in nameli
    st
    Jan 21 08:12:49 localhost: 113 named: No root nameservers for class 1
    Jan 21 08:12:50 localhost: 197 PCSAFS130: Starting server with 10.811
    and netbio
    s name PC811
    Jan 21 08:12:55 localhost: 219 PCSAFS130: Starting server with
    172.18.4.87 and n
    etbios name THE
    Jan 21 08:12:55 localhost: 219 PCSAFS130: Connect 0 Session 1  start on
    node 172
    .18.4.87 user pcguest for service ccd
    Jan 21 08:12:55 localhost: 197 PCSAFS130: Connect 1 Session 0  start on
    node 10.
    811 user pcguest for service ccd
    Jan 21 08:12:56 localhost: 200 PW_hplaserof: Can't print a empty data
    file. 
    Jan 21 08:12:56 localhost: 200 PW_hplaserof: Failed to output data
    Jan 21 08:12:56 localhost: 219 PCSAFS130: Connect 2 Session 1  start on
    node 172
    .18.4.87 user douglas for service isw
    Jan 21 08:12:56 localhost: 219 PCSAFS130: Connect 3 Session 1  start on
    node 172
    .18.4.87 user douglas for service ac
    Jan 21 08:13:06 localhost: 228 PCSAFS130: Starting server with 10.672
    and netbio
    s name CARLSEN
    Jan 21 08:13:06 localhost: 228 PCSAFS130: Connect 4 Session 2  start on
    node 10.
    672 user pcguest for service ccd
    Jan 21 08:13:08 localhost: 229 PCSAFS130: Starting server with
    172.18.4.76 and n
    etbios name PC651
    Jan 21 08:13:08 localhost: 229 PCSAFS130: Connect 5 Session 3  start on
    node 172
    .18.4.76 user pcguest for service ccm
    Jan 21 08:13:08 localhost: 229 PCSAFS130: Connect 6 Session 3  start on
    node 172
    .18.4.76 user pcguest for service ccd
    Jan 21 08:13:19 localhost: 232 PCSAFS130: Starting server with
    172.18.4.101 and 
    netbios name PC626
    Jan 21 08:13:19 localhost: 232 PCSAFS130: Connect 7 Session 4  start on
    node 172
    .18.4.101 user pcguest for service ccd
    Jan 21 08:13:28 localhost: 235 PCSAFS130: Starting server with
    172.18.4.18 and n
    etbios name PC190
    Jan 21 08:13:28 localhost: 235 PCSAFS130: Connect 8 Session 5  start on
    node 172
    .18.4.18 user pcguest for service ccd
    Jan 21 08:13:38 localhost: 237 PCSAFS130: Starting server with 10.295
    and netbio
    s name PC295
    Jan 21 08:13:38 localhost: 237 PCSAFS130: Connect 9 Session 6  start on
    node 10.
    295 user pcguest for service netc_data
    Jan 21 08:13:39 localhost: 238 PCSAFS130: Starting server with 10.702
    and netbio
    s name PC702
    Jan 21 08:13:39 localhost: 238 PCSAFS130: Connect 10 Session 7  start
    on node 10
    .702 user pcguest for service ccd
    Jan 21 08:13:40 localhost: 237 PCSAFS130: Client 10.295 user pcguest
    stopped con
    nection tid 9
    Jan 21 08:13:40 localhost: 237 PCSAFS130: Node 10.295 connection closed
    Jan 21 08:13:44 localhost: 239 PCSAFS130: Starting server with 10.532
    and netbio
    s name PC532
    Jan 21 08:13:44 localhost: 239 PCSAFS130: Connect 11 Session 8  start
    on node 10
    .532 user pcguest for service ccm
    Jan 21 08:13:44 localhost: 239 PCSAFS130: Connect 12 Session 8  start
    on node 10
    .532 user pcguest for service ccd
    Jan 21 08:13:45 localhost: 240 PCSAFS130: Starting server with 10.639
    and netbio
    s name PC639
    Jan 21 08:13:45 localhost: 240 PCSAFS130: Connect 13 Session 9  start
    on node 10
    .639 user pcguest for service win_excel
    Jan 21 08:13:49 localhost: 241 PCSAFS130: Starting server with 10.741
    and netbio
    s name PC741
    Jan 21 08:13:49 localhost: 241 PCSAFS130: Connect 14 Session 10  start
    on node 1
    0.741 user pcguest for service ccd
    Jan 21 08:13:51 localhost: 242 PCSAFS130: Starting server with 10.677
    and netbio
    s name PC677
    Jan 21 08:13:51 localhost: 242 PCSAFS130: Connect 15 Session 11  start
    on node 1
    0.677 user pcguest for service ccm
    Jan 21 08:13:52 localhost: 242 PCSAFS130: Connect 16 Session 11  start
    on node 1
    0.677 user pcguest for service ccd
    Jan 21 08:14:07 localhost: 249 PCSAFS130: Starting server with
    172.18.4.54 and n
    etbios name PC658
    Jan 21 08:14:07 localhost: 249 PCSAFS130: Connect 17 Session 12  start
    on node 1
    72.18.4.54 user pcguest for service win_wp52
    Jan 21 08:14:16 localhost: 250 PCSAFS130: Starting server with
    172.18.4.79 and n
    etbios name PC652
    Jan 21 08:14:16 localhost: 250 PCSAFS130: Connect 18 Session 13  start
    on node 1
    72.18.4.79 user pcguest for service ccm
    Jan 21 08:14:16 localhost: 250 PCSAFS130: Connect 19 Session 13  start
    on node 1
    72.18.4.79 user pcguest for service ccd
    Jan 21 08:14:21 localhost: 219 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 0
    Jan 21 08:14:21 localhost: 219 PCSAFS130: Client 172.18.4.87 user
    douglas stoppe
    d connection tid 2
    
    Jan 21 08:14:21 localhost: 219 PCSAFS130: Client 172.18.4.87 user
    douglas stoppe
    d connection tid 3
    Jan 21 08:14:21 localhost: 219 PCSAFS130: Node 172.18.4.87 connection
    closed
    Jan 21 08:14:29 localhost: 250 PCSAFS130: Connect 20 Session 13  start
    on node 1
    72.18.4.79 user pcguest for service win_word
    Jan 21 08:14:31 localhost: 251 PCSAFS130: Starting server with 10.676
    and netbio
    s name PC676
    Jan 21 08:14:31 localhost: 251 PCSAFS130: Connect 21 Session 14  start
    on node 1
    0.676 user pcguest for service ccd
    Jan 21 08:14:43 localhost: 252 PCSAFS130: Starting server with
    pc8056.trimet.or 
    and netbios name PC8056
    Jan 21 08:14:43 localhost: 252 PCSAFS130: Connect 22 Session 15  start
    on node p
    c8056.trimet.or user thoren for service ac
    Jan 21 08:14:51 localhost: 252 PCSAFS130: Connect 23 Session 15  start
    on node p
    c8056.trimet.or user thoren for service ccm
    Jan 21 08:14:59 localhost: 252 PCSAFS130: Connect 24 Session 15  start
    on node p
    c8056.trimet.or user pcguest for service ccd
    Jan 21 08:15:03 localhost: 264 PCSAFS130: Starting server with
    172.18.4.69 and n
    etbios name PC757
    Jan 21 08:15:03 localhost: 264 PCSAFS130: Connect 25 Session 16  start
    on node 1
    72.18.4.69 user pcguest for service ccm
    Jan 21 08:15:03 localhost: 264 PCSAFS130: Connect 26 Session 16  start
    on node 1
    72.18.4.69 user pcguest for service ccd
    Jan 21 08:15:04 localhost: 265 PCSAFS130: Starting server with
    172.18.4.10 and n
    etbios name PC668
    Jan 21 08:15:04 localhost: 265 PCSAFS130: Connect 27 Session 17  start
    on node 1
    72.18.4.10 user pcguest for service ccm
    Jan 21 08:15:04 localhost: 265 PCSAFS130: Connect 28 Session 17  start
    on node 1
    72.18.4.10 user pcguest for service ccd
    Jan 21 08:15:05 localhost: 266 PCSAFS130: Starting server with 10.295
    and netbio
    s name PC295
    Jan 21 08:15:05 localhost: 266 PCSAFS130: Connect 29 Session 18  start
    on node 1
    0.295 user pcguest for service ccd
    Jan 21 08:15:06 localhost: 267 PCSAFS130: Starting server with 10.256
    and netbio
    s name PC256
    Jan 21 08:15:06 localhost: 267 PCSAFS130: Connect 30 Session 19  start
    on node 1
    0.256 user pcguest for service ccd
    Jan 21 08:15:07 localhost: 266 PCSAFS130: Connect 31 Session 18  start
    on node 1
    0.295 user pcguest for service netc_data
    Jan 21 08:15:10 localhost: 266 PCSAFS130: Client 10.295 user pcguest
    stopped con
    nection tid 31
    Jan 21 08:15:21 localhost: 266 PCSAFS130: Connect 32 Session 18  start
    on node 1
    0.295 user pcguest for service ccm
    Jan 21 08:15:22 localhost: 266 PCSAFS130: Client 10.295 user pcguest
    stopped con
    nection tid 29
    
    Jan 21 08:15:22 localhost: 266 PCSAFS130: Connect 33 Session 18  start
    on node 1
    0.295 user pcguest for service ccd
    Jan 21 08:15:23 localhost: 268 PCSAFS130: Starting server with
    172.18.4.59 and n
    etbios name PC816
    Jan 21 08:15:23 localhost: 268 PCSAFS130: Connect 34 Session 20  start
    on node 1
    72.18.4.59 user pcguest for service ccm
    Jan 21 08:15:23 localhost: 268 PCSAFS130: Connect 35 Session 20  start
    on node 1
    72.18.4.59 user pcguest for service ccd
    Jan 21 08:15:32 localhost: 269 PCSAFS130: Starting server with
    172.18.4.45 and n
    etbios name CD501
    Jan 21 08:15:32 localhost: 269 PCSAFS130: Connect 36 Session 21  start
    on node 1
    72.18.4.45 user pcguest for service win_word
    Jan 21 08:15:40 localhost: 270 PCSAFS130: Starting server with 10.689
    and netbio
    s name PC689
    Jan 21 08:15:40 localhost: 270 PCSAFS130: Connect 37 Session 22  start
    on node 1
    0.689 user pcguest for service ccm
    Jan 21 08:15:41 localhost: 270 PCSAFS130: Connect 38 Session 22  start
    on node 1
    0.689 user pcguest for service ccd
    Jan 21 08:15:42 localhost: 271 PCSAFS130: Starting server with
    172.18.4.68 and n
    etbios name PC838
    Jan 21 08:15:42 localhost: 271 PCSAFS130: Connect 39 Session 23  start
    on node 1
    72.18.4.68 user pcguest for service ccm
    Jan 21 08:15:42 localhost: 271 PCSAFS130: Connect 40 Session 23  start
    on node 1
    72.18.4.68 user pcguest for service ccd
    Jan 21 08:15:46 localhost: 272 PCSAFS130: Starting server with
    172.18.4.26 and n
    etbios name PC340
    Jan 21 08:15:46 localhost: 272 PCSAFS130: Connect 41 Session 24  start
    on node 1
    72.18.4.26 user pcguest for service ccm
    Jan 21 08:15:46 localhost: 272 PCSAFS130: Connect 42 Session 24  start
    on node 1
    72.18.4.26 user pcguest for service ccd
    Jan 21 08:16:16 localhost: 273 PCSAFS130: Starting server with
    172.18.4.41 and n
    etbios name PC248
    Jan 21 08:16:16 localhost: 273 PCSAFS130: Connect 43 Session 25  start
    on node 1
    72.18.4.41 user pcguest for service ccd
    Jan 21 08:16:22 localhost: 249 PCSAFS130: Connect 44 Session 12  start
    on node 1
    72.18.4.54 user pcguest for service win_excel
    Jan 21 08:16:33 localhost: 274 PCSAFS130: Starting server with 10.369
    and netbio
    s name PC369
    Jan 21 08:16:33 localhost: 274 PCSAFS130: Connect 45 Session 26  start
    on node 1
    0.369 user pcguest for service ccd
    Jan 21 08:16:41 localhost: 275 PCSAFS130: Starting server with
    172.18.4.60 and n
    etbios name PC736
    Jan 21 08:16:41 localhost: 275 PCSAFS130: Connect 46 Session 27  start
    on node 1
    72.18.4.60 user pcguest for service win_excel
    Jan 21 08:16:52 localhost: 276 PCSAFS130: Starting server with 10.319
    and netbio
    s name PC319
    Jan 21 08:16:52 localhost: 276 PCSAFS130: Connect 47 Session 28  start
    on node 1
    0.319 user pcguest for service ccd
    Jan 21 08:17:06 localhost: 240 PCSAFS130: Connect 48 Session 9  start
    on node 10
    .639 user pcguest for service ccm
    Jan 21 08:17:06 localhost: 240 PCSAFS130: Connect 49 Session 9  start
    on node 10
    .639 user pcguest for service ccd
    Jan 21 08:17:30 localhost: 276 PCSAFS130: Connect 50 Session 28  start
    on node 1
    0.319 user pcguest for service ccm
    Jan 21 08:17:52 localhost: 277 PCSAFS130: Starting server with 10.635
    and netbio
    s name PC635
    Jan 21 08:17:52 localhost: 277 PCSAFS130: Connect 51 Session 29  start
    on node 1
    0.635 user pcguest for service ccd
    Jan 21 08:17:53 localhost: 278 PCSAFS130: Starting server with
    172.18.4.112 and 
    netbios name PC754
    Jan 21 08:17:53 localhost: 278 PCSAFS130: Connect 52 Session 30  start
    on node 1
    72.18.4.112 user pcguest for service ccm
    Jan 21 08:17:53 localhost: 278 PCSAFS130: Connect 53 Session 30  start
    on node 1
    72.18.4.112 user pcguest for service ccd
    Jan 21 08:18:00 localhost: 268 PCSAFS130: Connect 54 Session 20  start
    on node 1
    72.18.4.59 user pcguest for service win_word
    Jan 21 08:18:04 localhost: 271 PCSAFS130: Connect 55 Session 23  start
    on node 1
    72.18.4.68 user pcguest for service freelance
    Jan 21 08:19:08 localhost: 279 PCSAFS130: Starting server with 10.655
    and netbio
    s name WS_ADDR
    Jan 21 08:19:09 localhost: 279 PCSAFS130: Connect 56 Session 31  start
    on node 1
    0.655 user pcguest for service ccm
    Jan 21 08:19:20 localhost: 279 PCSAFS130: Connect 57 Session 31  start
    on node 1
    0.655 user pcguest for service ccd
    Jan 21 08:19:31 localhost: 280 PCSAFS130: Starting server with
    172.18.4.53 and n
    etbios name PC360
    Jan 21 08:19:31 localhost: 280 PCSAFS130: Connect 58 Session 32  start
    on node 1
    72.18.4.53 user pcguest for service ccm
    Jan 21 08:19:31 localhost: 280 PCSAFS130: Connect 59 Session 32  start
    on node 1
    72.18.4.53 user pcguest for service ccd
    Jan 21 08:19:52 localhost: 281 PCSAFS130: Starting server with
    172.18.4.4 and ne
    tbios name PC699
    Jan 21 08:19:52 localhost: 281 PCSAFS130: Connect 60 Session 33  start
    on node 1
    72.18.4.4 user pcguest for service ccm
    Jan 21 08:19:52 localhost: 281 PCSAFS130: Connect 61 Session 33  start
    on node 1
    72.18.4.4 user pcguest for service ccd
    Jan 21 08:20:01 localhost: 282 PCSAFS130: Starting server with
    172.18.4.23 and n
    etbios name PC249
    Jan 21 08:20:01 localhost: 282 PCSAFS130: Connect 62 Session 34  start
    on node 1
    72.18.4.23 user pcguest for service wp51
    Jan 21 08:20:05 localhost: 283 PCSAFS130: Starting server with 10.732
    and netbio
    s name PC732
    Jan 21 08:20:05 localhost: 283 PCSAFS130: Connect 63 Session 35  start
    on node 1
    0.732 user pcguest for service ccm
    Jan 21 08:20:06 localhost: 283 PCSAFS130: Connect 64 Session 35  start
    on node 1
    0.732 user pcguest for service ccd
    Jan 21 08:20:12 localhost: 284 PCSAFS130: Starting server with
    172.18.4.141 and 
    netbios name PC531
    Jan 21 08:20:12 localhost: 284 PCSAFS130: Connect 65 Session 36  start
    on node 1
    72.18.4.141 user pcguest for service ccm
    Jan 21 08:20:12 localhost: 284 PCSAFS130: Connect 66 Session 36  start
    on node 1
    72.18.4.141 user pcguest for service ccd
    Jan 21 08:20:16 localhost: 285 PCSAFS130: Starting server with
    172.18.4.65 and n
    etbios name PC828
    Jan 21 08:20:16 localhost: 285 PCSAFS130: Connect 67 Session 37  start
    on node 1
    72.18.4.65 user pcguest for service ccm
    Jan 21 08:20:17 localhost: 285 PCSAFS130: Connect 68 Session 37  start
    on node 1
    72.18.4.65 user pcguest for service ccd
    Jan 21 08:20:25 localhost: 286 PCSAFS130: Starting server with 10.789
    and netbio
    s name PC789
    Jan 21 08:20:25 localhost: 286 PCSAFS130: Connect 69 Session 38  start
    on node 1
    0.789 user pcguest for service win_word
    Jan 21 08:20:47 localhost: 287 PCSAFS130: Starting server with 10.379
    and netbio
    s name PC379
    Jan 21 08:20:47 localhost: 287 PCSAFS130: Connect 70 Session 39  start
    on node 1
    0.379 user pcguest for service win_word
    Jan 21 08:21:01 localhost: 284 PCSAFS130: Connect 71 Session 36  start
    on node 1
    72.18.4.141 user pcguest for service win_excel
    Jan 21 08:21:30 localhost: 288 PCSAFS130: Starting server with 10.185
    and netbio
    s name PC185
    Jan 21 08:21:30 localhost: 288 PCSAFS130: Connect 72 Session 40  start
    on node 1
    0.185 user pcguest for service win_wp52
    Jan 21 08:21:33 localhost: 289 PCSAFS130: Starting server with
    172.18.4.96 and n
    etbios name PC678
    Jan 21 08:21:33 localhost: 289 PCSAFS130: Connect 73 Session 41  start
    on node 1
    72.18.4.96 user pcguest for service ccm
    Jan 21 08:21:33 localhost: 289 PCSAFS130: Connect 74 Session 41  start
    on node 1
    72.18.4.96 user pcguest for service ccd
    Jan 21 08:21:39 localhost: 252 PCSAFS130: NETBIOS packet error,
    expecting SESSIO
    N_MESSAGE
    Jan 21 08:21:39 localhost: 252 PCSAFS130: Node pc8056.trimet.or
    connection close
    d
    Jan 21 08:21:54 localhost: 290 PCSAFS130: Starting server with
    172.18.4.87 and n
    etbios name THE
    Jan 21 08:21:54 localhost: 290 PCSAFS130: Connect 75 Session 42  start
    on node 1
    72.18.4.87 user pcguest for service ccm
    Jan 21 08:21:54 localhost: 290 PCSAFS130: Connect 76 Session 42  start
    on node 1
    72.18.4.87 user pcguest for service ccd
    Jan 21 08:21:58 localhost: 290 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 75
    Jan 21 08:21:59 localhost: 290 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 76
    Jan 21 08:21:59 localhost: 290 PCSAFS130: Node 172.18.4.87 connection
    closed
    Jan 21 08:22:05 localhost: 291 PCSAFS130: Starting server with
    172.18.4.87 and n
    etbios name THE
    Jan 21 08:22:05 localhost: 291 PCSAFS130: Connect 77 Session 43  start
    on node 1
    72.18.4.87 user pcguest for service ccm
    Jan 21 08:22:05 localhost: 291 PCSAFS130: Connect 78 Session 43  start
    on node 1
    72.18.4.87 user pcguest for service ccd
    Jan 21 08:22:05 localhost: 291 PCSAFS130: Connect 79 Session 43  start
    on node 1
    72.18.4.87 user douglas for service isw
    Jan 21 08:22:05 localhost: 291 PCSAFS130: Connect 80 Session 43  start
    on node 1
    72.18.4.87 user douglas for service ac
    Jan 21 08:22:18 localhost: 292 PCSAFS130: Starting server with 10.684
    and netbio
    s name PC684
    Jan 21 08:22:18 localhost: 292 PCSAFS130: Connect 81 Session 44  start
    on node 1
    0.684 user pcguest for service win_word
    Jan 21 08:22:18 localhost: 292 PCSAFS130: Node 10.684 connection closed
    Jan 21 08:22:18 localhost: 293 PCSAFS130: Starting server with 10.684
    and netbio
    s name PC684
    Jan 21 08:22:18 localhost: 293 PCSAFS130: Connect 82 Session 45  start
    on node 1
    0.684 user pcguest for service win_word
    Jan 21 08:22:18 localhost: 293 PCSAFS130: Client 10.684 user pcguest
    stopped con
    nection tid 82
    Jan 21 08:22:18 localhost: 293 PCSAFS130: Node 10.684 connection closed
    Jan 21 08:22:18 localhost: 294 PCSAFS130: Starting server with 10.684
    and netbio
    s name PC684
    Jan 21 08:22:18 localhost: 294 PCSAFS130: Connect 83 Session 46  start
    on node 1
    0.684 user pcguest for service win_word
    Jan 21 08:22:25 localhost: 295 PCSAFS130: Starting server with 10.775
    and netbio
    s name PC775
    Jan 21 08:22:25 localhost: 295 PCSAFS130: Connect 84 Session 47  start
    on node 1
    0.775 user pcguest for service ccm
    Jan 21 08:22:26 localhost: 295 PCSAFS130: Connect 85 Session 47  start
    on node 1
    0.775 user pcguest for service ccd
    Jan 21 08:23:16 localhost: 296 PCSAFS130: Starting server with 10.183
    and netbio
    s name PC183
    Jan 21 08:23:16 localhost: 296 PCSAFS130: Connect 86 Session 48  start
    on node 1
    0.183 user pcguest for service netc_data
    Jan 21 08:23:20 localhost: 296 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 86
    Jan 21 08:23:20 localhost: 296 PCSAFS130: Node 10.183 connection closed
    Jan 21 08:24:34 localhost: 297 PCSAFS130: Starting server with 10.181
    and netbio
    s name PC181
    Jan 21 08:24:34 localhost: 297 PCSAFS130: Connect 87 Session 49  start
    on node 1
    0.181 user pcguest for service ccm
    Jan 21 08:24:44 localhost: 297 PCSAFS130: Connect 88 Session 49  start
    on node 1
    0.181 user pcguest for service ccd
    Jan 21 08:24:53 localhost: 298 PCSAFS130: Starting server with
    172.18.4.57 and n
    etbios name PC727
    Jan 21 08:24:53 localhost: 298 PCSAFS130: Connect 89 Session 50  start
    on node 1
    72.18.4.57 user pcguest for service ccm
    Jan 21 08:24:53 localhost: 298 PCSAFS130: Connect 90 Session 50  start
    on node 1
    72.18.4.57 user pcguest for service ccd
    Jan 21 08:24:59 localhost: 300 PCSAFS130: Starting server with 10.837
    and netbio
    s name PC837
    Jan 21 08:24:59 localhost: 300 PCSAFS130: Connect 91 Session 51  start
    on node 1
    0.837 user pcguest for service ccm
    Jan 21 08:24:59 localhost: 300 PCSAFS130: Connect 92 Session 51  start
    on node 1
    0.837 user pcguest for service ccd
    Jan 21 08:25:19 localhost: 288 PCSAFS130: Connect 93 Session 40  start
    on node 1
    0.185 user pcguest for service ccd
    Jan 21 08:25:24 localhost: 301 PCSAFS130: Starting server with 10.990
    and netbio
    s name PC990
    Jan 21 08:25:24 localhost: 301 PCSAFS130: Connect 94 Session 52  start
    on node 1
    0.990 user pcguest for service ccm
    Jan 21 08:25:24 localhost: 301 PCSAFS130: Connect 95 Session 52  start
    on node 1
    0.990 user pcguest for service ccd
    Jan 21 08:25:26 localhost: 291 PCSAFS130: Connect 96 Session 43  start
    on node 1
    72.18.4.87 user pcguest for service win_excel
    Jan 21 08:26:09 localhost: 302 PCSAFS130: Starting server with
    172.18.4.153 and 
    netbios name PC836
    Jan 21 08:26:09 localhost: 302 PCSAFS130: Connect 97 Session 53  start
    on node 1
    72.18.4.153 user pcguest for service ccm
    Jan 21 08:26:09 localhost: 302 PCSAFS130: Connect 98 Session 53  start
    on node 1
    72.18.4.153 user pcguest for service ccd
    Jan 21 08:26:11 localhost: 289 PCSAFS130: Connect 99 Session 41  start
    on node 1
    72.18.4.96 user pcguest for service win_excel
    Jan 21 08:26:49 localhost: 303 PCSAFS130: Starting server with 10.183
    and netbio
    s name PC183
    Jan 21 08:26:49 localhost: 303 PCSAFS130: Connect 100 Session 54  start
    on node 
    10.183 user pcguest for service ccd
    Jan 21 08:26:50 localhost: 303 PCSAFS130: Connect 101 Session 54  start
    on node 
    10.183 user pcguest for service netc_data
    Jan 21 08:26:54 localhost: 303 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 101
    Jan 21 08:27:04 localhost: 304 PCSAFS130: Starting server with 10.316
    and netbio
    s name PC316
    Jan 21 08:27:04 localhost: 304 PCSAFS130: Connect 102 Session 55  start
    on node 
    10.316 user pcguest for service ccd
    Jan 21 08:27:06 localhost: 304 PCSAFS130: Connect 103 Session 55  start
    on node 
    10.316 user pcguest for service netc_data
    Jan 21 08:27:08 localhost: 304 PCSAFS130: Client 10.316 user pcguest
    stopped con
    nection tid 103
    Jan 21 08:27:23 localhost: 304 PCSAFS130: Connect 104 Session 55  start
    on node 
    10.316 user pcguest for service ccm
    Jan 21 08:27:23 localhost: 304 PCSAFS130: Client 10.316 user pcguest
    stopped con
    nection tid 102
    Jan 21 08:27:23 localhost: 304 PCSAFS130: Connect 105 Session 55  start
    on node 
    10.316 user pcguest for service ccd
    Jan 21 08:27:29 localhost: 305 PCSAFS130: Starting server with
    172.18.4.25 and n
    etbios name PC261
    Jan 21 08:27:29 localhost: 305 PCSAFS130: Connect 106 Session 56  start
    on node 
    172.18.4.25 user pcguest for service wp51
    Jan 21 08:27:42 localhost: 306 PCSAFS130: Starting server with
    pc8056.trimet.or 
    and netbios name PC8056
    Jan 21 08:27:42 localhost: 306 PCSAFS130: Connect 107 Session 57  start
    on node 
    pc8056.trimet.or user thoren for service isw
    Jan 21 08:27:43 localhost: 307 PCSAFS130: Starting server with
    172.18.4.70 and n
    etbios name PC510
    Jan 21 08:27:43 localhost: 307 PCSAFS130: Connect 108 Session 58  start
    on node 
    172.18.4.70 user pcguest for service ccm
    Jan 21 08:27:43 localhost: 307 PCSAFS130: Connect 109 Session 58  start
    on node 
    172.18.4.70 user pcguest for service ccd
    Jan 21 08:27:52 localhost: 305 PCSAFS130: Client 172.18.4.25 user
    pcguest stoppe
    d connection tid 106
    Jan 21 08:27:52 localhost: 305 PCSAFS130: Node 172.18.4.25 connection
    closed
    Jan 21 08:28:08 localhost: 308 PCSAFS130: Starting server with
    172.18.4.99 and n
    etbios name PC722
    Jan 21 08:28:08 localhost: 308 PCSAFS130: Connect 110 Session 59  start
    on node 
    172.18.4.99 user pcguest for service win_word
    Jan 21 08:28:43 localhost: 309 PCSAFS130: Starting server with
    172.18.4.25 and n
    etbios name PC261
    Jan 21 08:28:43 localhost: 309 PCSAFS130: Connect 111 Session 60  start
    on node 
    172.18.4.25 user pcguest for service wp51
    Jan 21 08:29:20 localhost: 310 PCSAFS130: Starting server with
    172.18.4.35 and n
    etbios name PC724
    Jan 21 08:29:20 localhost: 310 PCSAFS130: Connect 112 Session 61  start
    on node 
    172.18.4.35 user pcguest for service ccm
    Jan 21 08:29:21 localhost: 310 PCSAFS130: Connect 113 Session 61  start
    on node 
    172.18.4.35 user pcguest for service ccd
    Jan 21 08:29:54 localhost: 311 PCSAFS130: Starting server with 10.180
    and netbio
    s name PC180
    Jan 21 08:29:54 localhost: 311 PCSAFS130: Connect 114 Session 62  start
    on node 
    10.180 user pcguest for service netc_data
    Jan 21 08:29:57 localhost: 311 PCSAFS130: Client 10.180 user pcguest
    stopped con
    nection tid 114
    Jan 21 08:29:57 localhost: 311 PCSAFS130: Node 10.180 connection closed
    Jan 21 08:30:13 localhost: 315 PCSAFS130: Starting server with
    172.18.4.22 and n
    etbios name PC278
    Jan 21 08:30:13 localhost: 315 PCSAFS130: Connect 115 Session 63  start
    on node 
    172.18.4.22 user pcguest for service ccm
    Jan 21 08:30:14 localhost: 315 PCSAFS130: Connect 116 Session 63  start
    on node 
    172.18.4.22 user pcguest for service ccd
    Jan 21 08:30:18 localhost: 316 PCSAFS130: Starting server with
    172.18.4.94 and n
    etbios name PC695
    Jan 21 08:30:18 localhost: 316 PCSAFS130: Connect 117 Session 64  start
    on node 
    172.18.4.94 user pcguest for service ccm
    Jan 21 08:30:18 localhost: 316 PCSAFS130: Connect 118 Session 64  start
    on node 
    172.18.4.94 user pcguest for service ccd
    Jan 21 08:30:28 localhost: 315 PCSAFS130: Connect 119 Session 63  start
    on node 
    172.18.4.22 user pcguest for service win_wp52
    Jan 21 08:30:34 localhost: 309 PCSAFS130: Client 172.18.4.25 user
    pcguest stoppe
    d connection tid 111
    Jan 21 08:30:34 localhost: 309 PCSAFS130: Node 172.18.4.25 connection
    closed
    Jan 21 08:30:46 localhost: 317 PCSAFS130: Starting server with
    172.18.4.63 and n
    etbios name PC662
    Jan 21 08:30:46 localhost: 317 PCSAFS130: Connect 120 Session 65  start
    on node 
    172.18.4.63 user pcguest for service ccm
    Jan 21 08:30:46 localhost: 317 PCSAFS130: Connect 121 Session 65  start
    on node 
    172.18.4.63 user pcguest for service ccd
    Jan 21 08:31:03 localhost: 318 PCSAFS130: Starting server with
    172.18.4.82 and n
    etbios name PC632
    Jan 21 08:31:03 localhost: 318 PCSAFS130: Connect 122 Session 66  start
    on node 
    172.18.4.82 user pcguest for service ccm
    Jan 21 08:31:03 localhost: 318 PCSAFS130: Connect 123 Session 66  start
    on node 
    172.18.4.82 user pcguest for service ccd
    Jan 21 08:31:19 localhost: 319 PCSAFS130: Starting server with 10.101
    and netbio
    s name PC101
    Jan 21 08:31:19 localhost: 319 PCSAFS130: Connect 124 Session 67  start
    on node 
    10.101 user pcguest for service netc_data
    Jan 21 08:31:21 localhost: 319 PCSAFS130: Client 10.101 user pcguest
    stopped con
    nection tid 124
                                Press RETURN to continue
    Jan 21 08:31:21 localhost: 319 PCSAFS130: Node 10.101 connection closed
    Jan 21 08:31:22 localhost: 320 PCSAFS130: Starting server with
    172.18.4.39 and n
    etbios name PC674
    Jan 21 08:31:22 localhost: 320 PCSAFS130: Connect 125 Session 68  start
    on node 
    172.18.4.39 user pcguest for service ccm
    Jan 21 08:31:22 localhost: 320 PCSAFS130: Connect 126 Session 68  start
    on node 
    172.18.4.39 user pcguest for service ccd
    Jan 21 08:31:38 localhost: 321 PCSAFS130: Starting server with
    172.18.4.98 and n
    etbios name PC610
    Jan 21 08:31:38 localhost: 321 PCSAFS130: Connect 127 Session 69  start
    on node 
    172.18.4.98 user pcguest for service ccm
    Jan 21 08:31:38 localhost: 321 PCSAFS130: Connect 128 Session 69  start
    on node 
    172.18.4.98 user pcguest for service ccd
    Jan 21 08:31:38 localhost: 320 PCSAFS130: Connect 129 Session 68  start
    on node 
    172.18.4.39 user pcguest for service wp51
    Jan 21 08:31:42 localhost: 322 PCSAFS130: Starting server with 10.680
    and netbio
    s name PC680
    Jan 21 08:31:42 localhost: 322 PCSAFS130: Connect 130 Session 70  start
    on node 
    10.680 user pcguest for service ccm
    Jan 21 08:31:48 localhost: 288 PCSAFS130: Connect 131 Session 40  start
    on node 
    10.185 user pcguest for service ccm
    Jan 21 08:31:53 localhost: 322 PCSAFS130: Connect 132 Session 70  start
    on node 
    10.680 user pcguest for service ccd
    Jan 21 08:31:55 localhost: 323 PCSAFS130: Starting server with
    172.18.4.106 and 
    netbios name PC765
    Jan 21 08:31:55 localhost: 323 PCSAFS130: Connect 133 Session 71  start
    on node 
    172.18.4.106 user pcguest for service ccm
    Jan 21 08:31:55 localhost: 323 PCSAFS130: Connect 134 Session 71  start
    on node 
    172.18.4.106 user pcguest for service ccd
    Jan 21 08:31:55 localhost: 229 PCSAFS130: Connect 135 Session 3  start
    on node 1
    72.18.4.76 user pcguest for service win_word
    Jan 21 08:31:57 localhost: 324 PCSAFS130: Starting server with 10.520
    and netbio
    s name PC520
    Jan 21 08:31:57 localhost: 324 PCSAFS130: Connect 136 Session 72  start
    on node 
    10.520 user pcguest for service ccm
    Jan 21 08:31:58 localhost: 324 PCSAFS130: Connect 137 Session 72  start
    on node 
    10.520 user pcguest for service ccd
    Jan 21 08:32:03 localhost: 325 PCSAFS130: Starting server with 10.293
    and netbio
    s name PC293
    Jan 21 08:32:03 localhost: 325 PCSAFS130: Connect 138 Session 73  start
    on node 
    10.293 user pcguest for service netc_data
    Jan 21 08:32:05 localhost: 325 PCSAFS130: Client 10.293 user pcguest
    stopped con
    nection tid 138
    Jan 21 08:32:05 localhost: 325 PCSAFS130: Node 10.293 connection closed
    Jan 21 08:32:41 localhost: 326 telnetd: Connect from pc8056.trimet.org
    Jan 21 08:33:44 localhost: 310 PCSAFS130: Connect 139 Session 61  start
    on node 
    172.18.4.35 user pcguest for service win_word
    Jan 21 08:33:45 localhost: 318 PCSAFS130: Connect 140 Session 66  start
    on node 
    172.18.4.82 user pcguest for service win_word
    Jan 21 08:33:56 localhost: 335 PCSAFS130: Starting server with 10.343
    and netbio
    s name PC343
    Jan 21 08:33:56 localhost: 335 PCSAFS130: Connect 141 Session 74  start
    on node 
    10.343 user pcguest for service ccd
    Jan 21 08:33:56 localhost: 335 PCSAFS130: Connect 142 Session 74  start
    on node 
    10.343 user pcguest for service ccm
    Jan 21 08:34:01 localhost: 336 PCSAFS130: Starting server with
    172.18.4.91 and n
    etbios name PC637
    Jan 21 08:34:01 localhost: 336 PCSAFS130: Connect 143 Session 75  start
    on node 
    172.18.4.91 user pcguest for service ccm
    Jan 21 08:34:01 localhost: 336 PCSAFS130: Connect 144 Session 75  start
    on node 
    172.18.4.91 user pcguest for service ccd
    Jan 21 08:34:02 localhost: 337 PCSAFS130: Starting server with
    172.18.4.58 and n
    etbios name PC270
    Jan 21 08:34:02 localhost: 337 PCSAFS130: Connect 145 Session 76  start
    on node 
    172.18.4.58 user pcguest for service ccm
    Jan 21 08:34:02 localhost: 337 PCSAFS130: Connect 146 Session 76  start
    on node 
    172.18.4.58 user pcguest for service ccd
    Jan 21 08:34:09 localhost: 318 PCSAFS130: Client 172.18.4.82 user
    pcguest stoppe
    d connection tid 140
    Jan 21 08:34:20 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:34:20 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:34:20 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service thoren
    Jan 21 08:34:20 localhost: 232 PCSAFS130: Connect 147 Session 4  start
    on node 1
    72.18.4.101 user pcguest for service win_word
    Jan 21 08:34:21 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:34:21 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:34:21 localhost: 306 PCSAFS130: Connect 148 Session 57  start
    on node 
    pc8056.trimet.or user thoren for service thoren
    Jan 21 08:34:22 localhost: 338 PCSAFS130: Starting server with 10.774
    and netbio
    s name PC750
    Jan 21 08:34:22 localhost: 338 PCSAFS130: Connect 149 Session 77  start
    on node 
    10.774 user pcguest for service ccm
    Jan 21 08:34:25 localhost: 232 PCSAFS130: Connect 150 Session 4  start
    on node 1
    72.18.4.101 user pcguest for service ccm
    Jan 21 08:34:27 localhost: 338 PCSAFS130: Connect 151 Session 77  start
    on node 
    10.774 user pcguest for service ccd
    Jan 21 08:34:29 localhost: 339 PCSAFS130: Starting server with 10.180
    and netbio
    s name PC180
    Jan 21 08:34:29 localhost: 339 PCSAFS130: Connect 152 Session 78  start
    on node 
    10.180 user pcguest for service ccd
    Jan 21 08:34:45 localhost: 239 PCSAFS130: Connect 153 Session 8  start
    on node 1
    0.532 user pcguest for service win_word
    Jan 21 08:35:00 localhost: 229 PCSAFS130: Client 172.18.4.76 user
    pcguest stoppe
    d connection tid 135
    Jan 21 08:35:38 localhost: 341 PCSAFS130: Starting server with
    172.18.4.100 and 
    netbios name PC373
    Jan 21 08:35:38 localhost: 341 PCSAFS130: Connect 154 Session 79  start
    on node 
    172.18.4.100 user pcguest for service ccm
    Jan 21 08:35:38 localhost: 341 PCSAFS130: Connect 155 Session 79  start
    on node 
    172.18.4.100 user pcguest for service ccd
    Jan 21 08:35:48 localhost: 283 PCSAFS130: Node 10.732 connection closed
    Jan 21 08:36:08 localhost: 342 PCSAFS130: Starting server with
    172.18.4.32 and n
    etbios name PC769
    Jan 21 08:36:08 localhost: 342 PCSAFS130: Connect 156 Session 80  start
    on node 
    172.18.4.32 user pcguest for service ccm
    Jan 21 08:36:08 localhost: 342 PCSAFS130: Connect 157 Session 80  start
    on node 
    Jan 21 08:36:39 localhost: 317 PCSAFS130: Connect 158 Session 65  start
    on node 
    172.18.4.63 user pcguest for service win_word
    Jan 21 08:36:50 localhost: 288 PCSAFS130: Connect 159 Session 40  start
    on node 
    10.185 user pcguest for service win_wp52
    Jan 21 08:36:55 localhost: 343 PCSAFS130: Starting server with
    172.18.4.17 and n
    etbios name PC508
    Jan 21 08:36:55 localhost: 343 PCSAFS130: Connect 160 Session 81  start
    on node 
    172.18.4.17 user pcguest for service ccd
    Jan 21 08:36:56 localhost: 343 PCSAFS130: Connect 161 Session 81  start
    on node 
    172.18.4.17 user pcguest for service appl_common
    Jan 21 08:37:03 localhost: 344 PCSAFS130: Starting server with 10.101
    and netbio
    s name PC101
    Jan 21 08:37:03 localhost: 344 PCSAFS130: Connect 162 Session 82  start
    on node 
    10.101 user pcguest for service netc_data
    Jan 21 08:37:04 localhost: 344 PCSAFS130: Client 10.101 user pcguest
    stopped con
    nection tid 162
    Jan 21 08:37:04 localhost: 344 PCSAFS130: Node 10.101 connection closed
    Jan 21 08:37:09 localhost: 343 PCSAFS130: Connect 163 Session 81  start
    on node 
    172.18.4.17 user pcguest for service ccm
    Jan 21 08:37:09 localhost: 343 PCSAFS130: Connect 164 Session 81  start
    on node 
    172.18.4.17 user gorton for service isw
    Jan 21 08:37:14 localhost: 345 PCSAFS130: Starting server with 10.101
    and netbio
    s name PC101
    Jan 21 08:37:14 localhost: 345 PCSAFS130: Connect 165 Session 83  start
    on node 
    10.101 user pcguest for service ccd
    Jan 21 08:37:41 localhost: 337 PCSAFS130: Connect 166 Session 76  start
    on node 
    172.18.4.58 user pcguest for service pdox35
    
    Jan 21 08:37:58 localhost: 346 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en pipe signal at pc 431548
    Jan 21 08:37:58 localhost: 346 PCSAFS130: Node 192.168.12.100
    connection closed
    
    Jan 21 08:38:07 localhost: 350 PCSAFS130: Starting server with 10.348
    and netbio
    s name PC348
    Jan 21 08:38:07 localhost: 350 PCSAFS130: Connect 167 Session 85  start
    on node 
    10.348 user pcguest for service ccm
    Jan 21 08:38:08 localhost: 350 PCSAFS130: Connect 168 Session 85  start
    on node 
    10.348 user pcguest for service ccd
    
    Jan 21 08:38:08 localhost: 347 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en signal at pc 431548
    Jan 21 08:38:08 localhost: 347 PCSAFS130: Node 192.168.12.100
    connection closed
    
    Jan 21 08:38:14 localhost: 352 PCSAFS130: Starting server with
    172.18.4.158 and 
    netbios name PC700
    Jan 21 08:38:14 localhost: 352 PCSAFS130: Connect 169 Session 87  start
    on node 
    172.18.4.158 user pcguest for service ccm
    Jan 21 08:38:14 localhost: 352 PCSAFS130: Connect 170 Session 87  start
    on node 
    172.18.4.158 user pcguest for service ccd
    
    Jan 21 08:38:18 localhost: 349 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en  signal at pc 431548
    Jan 21 08:38:18 localhost: 349 PCSAFS130: Node 192.168.12.100
    connection closed
    Jan 21 08:38:24 localhost: 232 PCSAFS130: Node 172.18.4.101 connection
    closed
    Jan 21 08:38:29 localhost: 354 PCSAFS130: Starting server with
    172.18.4.101 and 
    netbios name PC626
    Jan 21 08:38:29 localhost: 354 PCSAFS130: Connect 171 Session 89  start
    on node 
    172.18.4.101 user pcguest for service ccm
    Jan 21 08:38:29 localhost: 354 PCSAFS130: Connect 172 Session 89  start
    on node 
    172.18.4.101 user pcguest for service ccd
    Jan 21 08:38:34 localhost: 356 PCSAFS130: Starting server with 10.293
    and netbio
    s name PC293
    Jan 21 08:38:34 localhost: 356 PCSAFS130: Connect 173 Session 90  start
    on node 
    10.293 user pcguest for service netc_data
    Jan 21 08:38:36 localhost: 356 PCSAFS130: Client 10.293 user pcguest
    stopped con
    nection tid 173
    Jan 21 08:38:36 localhost: 356 PCSAFS130: Node 10.293 connection closed
    Jan 21 08:38:43 localhost: 357 PCSAFS130: Starting server with 10.293
    and netbio
    s name PC293
    Jan 21 08:38:43 localhost: 357 PCSAFS130: Connect 174 Session 91  start
    on node 
    10.293 user pcguest for service netc_data
    Jan 21 08:38:45 localhost: 357 PCSAFS130: Client 10.293 user pcguest
    stopped con
    nection tid 174
    Jan 21 08:38:45 localhost: 357 PCSAFS130: Node 10.293 connection closed
    Jan 21 08:38:47 localhost: 358 PCSAFS130: Starting server with 10.638
    and netbio
    s name MODEM1
    Jan 21 08:38:47 localhost: 358 PCSAFS130: Connect 175 Session 92  start
    on node 
    10.638 user pcguest for service ccd
    
    Jan 21 08:38:49 localhost: 355 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en pipe signal at pc 431548
    Jan 21 08:38:49 localhost: 355 PCSAFS130: Node 192.168.12.100
    connection closed
    Jan 21 08:38:50 localhost: 360 PCSAFS130: Starting server with
    172.18.4.46 and n
    etbios name PC742
    Jan 21 08:38:50 localhost: 360 PCSAFS130: Connect 176 Session 94  start
    on node 
    172.18.4.46 user pcguest for service win_wp61
    Jan 21 08:38:52 localhost: 361 PCSAFS130: Starting server with
    172.18.4.78 and n
    etbios name PC302
    Jan 21 08:38:52 localhost: 361 PCSAFS130: Connect 177 Session 95  start
    on node 
    172.18.4.78 user pcguest for service ccd
    Jan 21 08:38:54 localhost: 362 PCSAFS130: Starting server with
    172.18.4.88 and n
    etbios name PC831
    Jan 21 08:38:54 localhost: 362 PCSAFS130: Connect 178 Session 96  start
    on node 
    172.18.4.88 user pcguest for service ccm
    Jan 21 08:38:54 localhost: 362 PCSAFS130: Connect 179 Session 96  start
    on node 
    172.18.4.88 user pcguest for service ccd
    Jan 21 08:39:08 localhost: 363 PCSAFS130: Starting server with 10.293
    and netbio
    s name PC293
    Jan 21 08:39:08 localhost: 363 PCSAFS130: Connect 180 Session 97  start
    on node 
    10.293 user pcguest for service netc_data
    Jan 21 08:39:10 localhost: 363 PCSAFS130: Client 10.293 user pcguest
    stopped con
    nection tid 180
    Jan 21 08:39:10 localhost: 363 PCSAFS130: Node 10.293 connection closed
    Jan 21 08:39:28 localhost: 360 PCSAFS130: Client 172.18.4.46 user
    pcguest stoppe
    d connection tid 176
    Jan 21 08:39:28 localhost: 360 PCSAFS130: Node 172.18.4.46 connection
    closed
    Jan 21 08:39:35 localhost: 364 PCSAFS130: Starting server with 10.293
    and netbio
    s name PC293
    Jan 21 08:39:35 localhost: 364 PCSAFS130: Connect 181 Session 98  start
    on node 
    10.293 user pcguest for service ccd
    Jan 21 08:39:49 localhost: 304 PCSAFS130: Node 10.316 connection closed
    Jan 21 08:39:55 localhost: 365 PCSAFS130: Starting server with
    172.18.4.92 and n
    etbios name PC268
    Jan 21 08:39:55 localhost: 365 PCSAFS130: Connect 182 Session 99  start
    on node 
    172.18.4.92 user pcguest for service ccm
    Jan 21 08:39:55 localhost: 365 PCSAFS130: Connect 183 Session 99  start
    on node 
    172.18.4.92 user pcguest for service ccd
    Jan 21 08:39:56 localhost: 366 PCSAFS130: Starting server with 10.316
    and netbio
    s name PC316
    Jan 21 08:39:56 localhost: 366 PCSAFS130: Connect 184 Session 100 
    start on node
     10.316 user pcguest for service netc_data
    Jan 21 08:39:58 localhost: 366 PCSAFS130: Client 10.316 user pcguest
    stopped con
    nection tid 184
    Jan 21 08:39:58 localhost: 366 PCSAFS130: Node 10.316 connection closed
    Jan 21 08:40:15 localhost: 342 PCSAFS130: Connect 185 Session 80  start
    on node 
    172.18.4.32 user pcguest for service win_word
    Jan 21 08:40:32 localhost: 367 PCSAFS130: Starting server with 10.732
    and netbio
    s name PC732
    Jan 21 08:40:32 localhost: 367 PCSAFS130: Connect 186 Session 101 
    start on node
     10.732 user pcguest for service ccm
    Jan 21 08:40:33 localhost: 367 PCSAFS130: Connect 187 Session 101 
    start on node
     10.732 user pcguest for service ccd
    Jan 21 08:40:45 localhost: 352 PCSAFS130: Connect 188 Session 87  start
    on node 
    172.18.4.158 user pcguest for service win_word
    Jan 21 08:41:02 localhost: 285 PCSAFS130: Connect 189 Session 37  start
    on node 
    172.18.4.65 user pcguest for service win_proj
    Jan 21 08:41:06 localhost: 294 PCSAFS130: Client 10.684 user pcguest
    stopped con
    nection tid 83
    Jan 21 08:41:06 localhost: 294 PCSAFS130: Node 10.684 connection closed
    Jan 21 08:41:07 localhost: 358 PCSAFS130: Node 10.638 connection closed
    Jan 21 08:41:15 localhost: 368 PCSAFS130: Starting server with 10.638
    and netbio
    s name MODEM1
    Jan 21 08:41:15 localhost: 368 PCSAFS130: Connect 190 Session 102 
    start on node
     10.638 user pcguest for service netc_data
    Jan 21 08:41:16 localhost: 369 PCSAFS130: Starting server with 10.364
    and netbio
    s name PC364
    Jan 21 08:41:17 localhost: 369 PCSAFS130: Connect 191 Session 103 
    start on node
     10.364 user pcguest for service ccd
    Jan 21 08:41:17 localhost: 368 PCSAFS130: Client 10.638 user pcguest
    stopped con
    nection tid 190
    Jan 21 08:41:17 localhost: 368 PCSAFS130: Node 10.638 connection closed
    Jan 21 08:41:18 localhost: 370 PCSAFS130: Starting server with 10.638
    and netbio
    s name MODEM1
    Jan 21 08:41:18 localhost: 370 PCSAFS130: Connect 192 Session 104 
    start on node
     10.638 user pcguest for service aw
    Jan 21 08:41:20 localhost: 370 PCSAFS130: Client 10.638 user pcguest
    stopped con
    nection tid 192
    Jan 21 08:41:20 localhost: 370 PCSAFS130: Node 10.638 connection closed
    Jan 21 08:41:30 localhost: 371 PCSAFS130: Starting server with
    172.18.4.49 and n
    etbios name PC218
    Jan 21 08:41:30 localhost: 371 PCSAFS130: Connect 193 Session 105 
    start on node
     172.18.4.49 user pcguest for service ccm
    Jan 21 08:41:31 localhost: 371 PCSAFS130: Connect 194 Session 105 
    start on node
     172.18.4.49 user pcguest for service ccd
    Jan 21 08:41:55 localhost: 372 PCSAFS130: Starting server with
    172.18.4.13 and n
    etbios name PC781
    Jan 21 08:41:56 localhost: 372 PCSAFS130: Connect 195 Session 106 
    start on node
     172.18.4.13 user pcguest for service win_wp52
    Jan 21 08:42:12 localhost: 373 PCSAFS130: Starting server with
    172.18.4.93 and n
    etbios name PC627
    Jan 21 08:42:12 localhost: 373 PCSAFS130: Connect 196 Session 107 
    start on node
     172.18.4.93 user pcguest for service ccm
    Jan 21 08:42:12 localhost: 373 PCSAFS130: Connect 197 Session 107 
    start on node
     172.18.4.93 user pcguest for service ccd
    Jan 21 08:42:16 localhost: 354 PCSAFS130: Connect 198 Session 89  start
    on node 
    172.18.4.101 user pcguest for service win_word
    Jan 21 08:42:20 localhost: 374 PCSAFS130: Starting server with
    172.18.4.75 and n
    etbios name PC647
    Jan 21 08:42:20 localhost: 374 PCSAFS130: Connect 199 Session 108 
    start on node
     172.18.4.75 user pcguest for service ccm
    Jan 21 08:42:20 localhost: 374 PCSAFS130: Connect 200 Session 108 
    start on node
     172.18.4.75 user pcguest for service ccd
    Jan 21 08:42:28 localhost: 375 PCSAFS130: Starting server with
    172.18.4.129 and 
    netbios name PC646
    Jan 21 08:42:28 localhost: 375 PCSAFS130: Connect 201 Session 109 
    start on node
     172.18.4.129 user pcguest for service ccm
    Jan 21 08:42:28 localhost: 375 PCSAFS130: Connect 202 Session 109 
    start on node
     172.18.4.129 user pcguest for service ccd
    Jan 21 08:42:32 localhost: 376 PCSAFS130: Starting server with
    172.18.4.25 and n
    etbios name PC261
    Jan 21 08:42:32 localhost: 376 PCSAFS130: Connect 203 Session 110 
    start on node
     172.18.4.25 user pcguest for service ccm
    Jan 21 08:42:32 localhost: 376 PCSAFS130: Connect 204 Session 110 
    start on node
     172.18.4.25 user pcguest for service ccd
    Jan 21 08:42:56 localhost: 377 PCSAFS130: Starting server with
    172.18.4.36 and n
    etbios name PC744
    Jan 21 08:42:57 localhost: 377 PCSAFS130: Connect 205 Session 111 
    start on node
     172.18.4.36 user pcguest for service ccd
    Jan 21 08:42:57 localhost: 377 PCSAFS130: Connect 206 Session 111 
    start on node
     172.18.4.36 user pcguest for service ccm
    Jan 21 08:43:15 localhost: 378 PCSAFS130: Starting server with 10.753
    and netbio
    s name PC753
    Jan 21 08:43:15 localhost: 378 PCSAFS130: Connect 207 Session 112 
    start on node
     10.753 user pcguest for service ccm
    Jan 21 08:43:16 localhost: 378 PCSAFS130: Connect 208 Session 112 
    start on node
     10.753 user pcguest for service ccd
    Jan 21 08:43:17 localhost: 379 PCSAFS130: Starting server with
    172.18.4.89 and n
    etbios name PC522
    Jan 21 08:43:17 localhost: 379 PCSAFS130: Connect 209 Session 113 
    start on node
     172.18.4.89 user pcguest for service ccm
    Jan 21 08:43:17 localhost: 379 PCSAFS130: Connect 210 Session 113 
    start on node
     172.18.4.89 user pcguest for service ccd
    Jan 21 08:43:39 localhost: 380 PCSAFS130: Starting server with
    172.18.4.90 and n
    etbios name PC752
    Jan 21 08:43:39 localhost: 380 PCSAFS130: Connect 211 Session 114 
    start on node
     172.18.4.90 user pcguest for service ccm
    Jan 21 08:43:39 localhost: 380 PCSAFS130: Connect 212 Session 114 
    start on node
     172.18.4.90 user pcguest for service ccd
    Jan 21 08:43:44 localhost: 381 PCSAFS130: Starting server with
    172.18.4.50 and n
    etbios name PC629
    Jan 21 08:43:44 localhost: 381 PCSAFS130: Connect 213 Session 115 
    start on node
     172.18.4.50 user pcguest for service ccm
    Jan 21 08:43:44 localhost: 381 PCSAFS130: Connect 214 Session 115 
    start on node
     172.18.4.50 user pcguest for service ccd
    Jan 21 08:44:01 localhost: 382 PCSAFS130: Starting server with
    172.18.4.114 and 
    netbios name PC770
    Jan 21 08:44:01 localhost: 382 PCSAFS130: Connect 215 Session 116 
    start on node
     172.18.4.114 user pcguest for service ccm
    Jan 21 08:44:01 localhost: 382 PCSAFS130: Connect 216 Session 116 
    start on node
     172.18.4.114 user pcguest for service ccd
    Jan 21 08:44:05 localhost: 382 PCSAFS130: Connect 217 Session 116 
    start on node
     172.18.4.114 user douglas for service isw
    Jan 21 08:44:05 localhost: 382 PCSAFS130: Connect 218 Session 116 
    start on node
     172.18.4.114 user douglas for service ac
    Jan 21 08:44:07 localhost: 383 PCSAFS130: Starting server with 10.316
    and netbio
    s name PC316
    Jan 21 08:44:07 localhost: 383 PCSAFS130: Connect 219 Session 117 
    start on node
     10.316 user pcguest for service ccd
    Jan 21 08:44:08 localhost: 381 PCSAFS130: Connect 220 Session 115 
    start on node
     172.18.4.50 user pcguest for service win_word
    Jan 21 08:44:08 localhost: 383 PCSAFS130: Connect 221 Session 117 
    start on node
     10.316 user pcguest for service netc_data
    Jan 21 08:44:11 localhost: 320 PCSAFS130: Client 172.18.4.39 user
    pcguest stoppe
    d connection tid 129
    Jan 21 08:44:11 localhost: 383 PCSAFS130: Client 10.316 user pcguest
    stopped con
    nection tid 221
    Jan 21 08:44:20 localhost: 383 PCSAFS130: Connect 222 Session 117 
    start on node
     10.316 user pcguest for service ccm
    Jan 21 08:44:21 localhost: 383 PCSAFS130: Client 10.316 user pcguest
    stopped con
    nection tid 219
    Jan 21 08:44:21 localhost: 383 PCSAFS130: Connect 223 Session 117 
    start on node
     10.316 user pcguest for service ccd
    Jan 21 08:44:29 localhost: 384 PCSAFS130: Starting server with 10.519
    and netbio
    s name PC519
    Jan 21 08:44:29 localhost: 384 PCSAFS130: Connect 224 Session 118 
    start on node
     10.519 user pcguest for service netc_data
    Jan 21 08:44:34 localhost: 384 PCSAFS130: Client 10.519 user pcguest
    stopped con
    nection tid 224
    Jan 21 08:44:34 localhost: 384 PCSAFS130: Node 10.519 connection closed
    Jan 21 08:44:55 localhost: 385 PCSAFS130: Starting server with 10.182
    and netbio
    s name PC182
    Jan 21 08:44:55 localhost: 385 PCSAFS130: Connect 225 Session 119 
    start on node
     10.182 user pcguest for service ccd
    Jan 21 08:44:56 localhost: 382 PCSAFS130: Connect 226 Session 116 
    start on node
     172.18.4.114 user pcguest for service win_proj
    Jan 21 08:44:57 localhost: 385 PCSAFS130: Connect 227 Session 119 
    start on node
     10.182 user pcguest for service netc_data
    Jan 21 08:45:01 localhost: 385 PCSAFS130: Client 10.182 user pcguest
    stopped con
    nection tid 227
    Jan 21 08:45:03 localhost: 317 PCSAFS130: Client 172.18.4.63 user
    pcguest stoppe
    d connection tid 158
    Jan 21 08:45:11 localhost: 381 PCSAFS130: Client 172.18.4.50 user
    pcguest stoppe
    d connection tid 220
    Jan 21 08:45:13 localhost: 389 PCSAFS130: Starting server with
    172.18.4.66 and n
    etbios name PC619
    Jan 21 08:45:14 localhost: 389 PCSAFS130: Connect 228 Session 120 
    start on node
     172.18.4.66 user pcguest for service ccm
    Jan 21 08:45:14 localhost: 389 PCSAFS130: Connect 229 Session 120 
    start on node
     172.18.4.66 user pcguest for service ccd
    Jan 21 08:45:14 localhost: 381 PCSAFS130: Client 172.18.4.50 user
    pcguest stoppe
    d connection tid 213
    Jan 21 08:45:14 localhost: 381 PCSAFS130: Client 172.18.4.50 user
    pcguest stoppe
    d connection tid 214
    Jan 21 08:45:14 localhost: 381 PCSAFS130: Node 172.18.4.50 connection
    closed
    Jan 21 08:45:36 localhost: 390 PCSAFS130: Starting server with
    172.18.4.16 and n
    etbios name PC656
    Jan 21 08:45:36 localhost: 390 PCSAFS130: Connect 230 Session 121 
    start on node
     172.18.4.16 user pcguest for service ccm
    Jan 21 08:45:36 localhost: 390 PCSAFS130: Connect 231 Session 121 
    start on node
     172.18.4.16 user pcguest for service ccd
    Jan 21 08:45:39 localhost: 391 PCSAFS130: Starting server with
    172.18.4.27 and n
    etbios name PC792
    Jan 21 08:45:39 localhost: 391 PCSAFS130: Connect 232 Session 122 
    start on node
     172.18.4.27 user pcguest for service ccm
    Jan 21 08:45:39 localhost: 391 PCSAFS130: Connect 233 Session 122 
    start on node
     172.18.4.27 user pcguest for service ccd
    Jan 21 08:45:47 localhost: 391 PCSAFS130: Connect 234 Session 122 
    start on node
     172.18.4.27 user pcguest for service win_word
    Jan 21 08:45:47 localhost: 322 PCSAFS130: Connect 235 Session 70  start
    on node 
    10.680 user pcguest for service win_excel
    Jan 21 08:46:01 localhost: 392 PCSAFS130: Starting server with
    172.18.4.107 and 
    netbios name PC829
    Jan 21 08:46:01 localhost: 392 PCSAFS130: Connect 236 Session 123 
    start on node
     172.18.4.107 user pcguest for service ccm
    Jan 21 08:46:01 localhost: 392 PCSAFS130: Connect 237 Session 123 
    start on node
     172.18.4.107 user pcguest for service ccd
    Jan 21 08:46:05 localhost: 382 PCSAFS130: Client 172.18.4.114 user
    pcguest stopp
    ed connection tid 215
    Jan 21 08:46:05 localhost: 382 PCSAFS130: Client 172.18.4.114 user
    pcguest stopp
    ed connection tid 216
    Jan 21 08:46:05 localhost: 382 PCSAFS130: Client 172.18.4.114 user
    douglas stopp
    ed connection tid 217
    Jan 21 08:46:05 localhost: 382 PCSAFS130: Client 172.18.4.114 user
    pcguest stopp
    ed connection tid 226
    Jan 21 08:46:05 localhost: 382 PCSAFS130: Client 172.18.4.114 user
    douglas stopp
    ed connection tid 218
    Jan 21 08:46:05 localhost: 382 PCSAFS130: Node 172.18.4.114 connection
    closed
    Jan 21 08:46:19 localhost: 322 PCSAFS130: Client 10.680 user pcguest
    stopped con
    nection tid 235
    Jan 21 08:46:30 localhost: 393 PCSAFS130: Starting server with
    172.18.4.114 and 
    netbios name PC770
    Jan 21 08:46:30 localhost: 393 PCSAFS130: Connect 238 Session 124 
    start on node
     172.18.4.114 user pcguest for service ccm
    Jan 21 08:46:30 localhost: 393 PCSAFS130: Connect 239 Session 124 
    start on node
     172.18.4.114 user pcguest for service ccd
    Jan 21 08:46:33 localhost: 393 PCSAFS130: Connect 240 Session 124 
    start on node
     172.18.4.114 user douglas for service isw
    Jan 21 08:46:33 localhost: 393 PCSAFS130: Connect 241 Session 124 
    start on node
     172.18.4.114 user douglas for service ac
    Jan 21 08:46:42 localhost: 394 PCSAFS130: Starting server with 10.787
    and netbio
    s name PC787
    Jan 21 08:46:42 localhost: 394 PCSAFS130: Connect 242 Session 125 
    start on node
     10.787 user pcguest for service ccd
    Jan 21 08:46:45 localhost: 394 PCSAFS130: Connect 243 Session 125 
    start on node
     10.787 user pcguest for service ccm
    Jan 21 08:46:47 localhost: 395 PCSAFS130: Starting server with
    172.18.4.38 and n
    etbios name PC664
    Jan 21 08:46:47 localhost: 395 PCSAFS130: Connect 244 Session 126 
    start on node
     172.18.4.38 user pcguest for service ccm
    Jan 21 08:46:47 localhost: 395 PCSAFS130: Connect 245 Session 126 
    start on node
     172.18.4.38 user pcguest for service ccd
    Jan 21 08:46:59 localhost: 395 PCSAFS130: Connect 246 Session 126 
    start on node
     172.18.4.38 user pcguest for service wp51
    Jan 21 08:47:14 localhost: 396 PCSAFS130: Starting server with
    172.18.4.15 and n
    etbios name PC663
    Jan 21 08:47:14 localhost: 396 PCSAFS130: Connect 247 Session 127 
    start on node
     172.18.4.15 user pcguest for service ccm
    Jan 21 08:47:14 localhost: 396 PCSAFS130: Connect 248 Session 127 
    start on node
     172.18.4.15 user pcguest for service ccd
    Jan 21 08:47:25 localhost: 396 PCSAFS130: Connect 249 Session 127 
    start on node
     172.18.4.15 user pcguest for service win_excel
    Jan 21 08:48:00 localhost: 393 PCSAFS130: Connect 250 Session 124 
    start on node
     172.18.4.114 user pcguest for service win_proj
    Jan 21 08:48:17 localhost: 397 PCSAFS130: Starting server with
    172.18.4.19 and n
    etbios name PC254
    Jan 21 08:48:17 localhost: 397 PCSAFS130: Connect 251 Session 128 
    start on node
     172.18.4.19 user pcguest for service ccm
    Jan 21 08:48:17 localhost: 397 PCSAFS130: Connect 252 Session 128 
    start on node
     172.18.4.19 user pcguest for service ccd
    Jan 21 08:48:29 localhost: 393 PCSAFS130: Client 172.18.4.114 user
    pcguest stopp
    ed connection tid 250
    Jan 21 08:48:36 localhost: 393 PCSAFS130: Client 172.18.4.114 user
    pcguest stopp
    ed connection tid 238
    Jan 21 08:48:36 localhost: 393 PCSAFS130: Client 172.18.4.114 user
    pcguest stopp
    ed connection tid 239
    Jan 21 08:48:36 localhost: 393 PCSAFS130: Client 172.18.4.114 user
    douglas stopp
    ed connection tid 240
    Jan 21 08:48:36 localhost: 393 PCSAFS130: Client 172.18.4.114 user
    douglas stopp
    ed connection tid 241
    Jan 21 08:48:36 localhost: 393 PCSAFS130: Node 172.18.4.114 connection
    closed
    Jan 21 08:48:37 localhost: 307 PCSAFS130: Connect 253 Session 58  start
    on node 
    172.18.4.70 user pcguest for service win_excel
    Jan 21 08:49:04 localhost: 322 PCSAFS130: Connect 254 Session 70  start
    on node 
    10.680 user pcguest for service win_excel
    Jan 21 08:49:04 localhost: 318 PCSAFS130: Connect 255 Session 66  start
    on node 
    172.18.4.82 user pcguest for service win_word
    Jan 21 08:49:08 localhost: 398 PCSAFS130: Starting server with 10.331
    and netbio
    s name PC331
    Jan 21 08:49:08 localhost: 398 PCSAFS130: Connect 256 Session 129 
    start on node
     10.331 user pcguest for service ccd
    Jan 21 08:49:19 localhost: 318 PCSAFS130: Client 172.18.4.82 user
    pcguest stoppe
    d connection tid 255
    Jan 21 08:49:25 localhost: 318 PCSAFS130: Connect 257 Session 66  start
    on node 
    172.18.4.82 user pcguest for service win_word
    Jan 21 08:49:35 localhost: 399 PCSAFS130: Starting server with
    172.18.4.28 and n
    etbios name PC771
    Jan 21 08:49:35 localhost: 399 PCSAFS130: Connect 258 Session 130 
    start on node
     172.18.4.28 user pcguest for service ccm
    Jan 21 08:49:39 localhost: 281 PCSAFS130: Connect 259 Session 33  start
    on node 
    172.18.4.4 user pcguest for service win_word
    Jan 21 08:49:40 localhost: 399 PCSAFS130: Connect 260 Session 130 
    start on node
     172.18.4.28 user pcguest for service ccd
    Jan 21 08:49:59 localhost: 318 PCSAFS130: Client 172.18.4.82 user
    pcguest stoppe
    d connection tid 257
    Jan 21 08:50:14 localhost: 318 PCSAFS130: Connect 261 Session 66  start
    on node 
    172.18.4.82 user pcguest for service win_word
    Jan 21 08:50:21 localhost: 318 PCSAFS130: Client 172.18.4.82 user
    pcguest stoppe
    d connection tid 261
    Jan 21 08:50:33 localhost: 318 PCSAFS130: Connect 262 Session 66  start
    on node 
    172.18.4.82 user pcguest for service vscan
    Jan 21 08:50:48 localhost: 239 PCSAFS130: Connect 263 Session 8  start
    on node 1
    0.532 user pcguest for service win_excel
    Jan 21 08:50:48 localhost: 400 PCSAFS130: Starting server with 10.705
    and netbio
    s name PC705
    Jan 21 08:50:48 localhost: 400 PCSAFS130: Connect 264 Session 131 
    start on node
     10.705 user pcguest for service ccd
    Jan 21 08:51:06 localhost: 269 PCSAFS130: Connect 265 Session 21  start
    on node 
    172.18.4.45 user pcguest for service win_excel
    Jan 21 08:51:22 localhost: 401 PCSAFS130: Starting server with
    172.18.4.5 and ne
    tbios name MIKOTA
    Jan 21 08:51:23 localhost: 401 PCSAFS130: Connect 266 Session 132 
    start on node
     172.18.4.5 user pcguest for service ccm
    Jan 21 08:51:23 localhost: 401 PCSAFS130: Connect 267 Session 132 
    start on node
     172.18.4.5 user pcguest for service ccd
    Jan 21 08:51:23 localhost: 401 PCSAFS130: Connect 268 Session 132 
    start on node
     172.18.4.5 user mikota for service isw
    Jan 21 08:51:23 localhost: 401 PCSAFS130: Connect 269 Session 132 
    start on node
     172.18.4.5 user pcguest for service winbatch
    Jan 21 08:51:23 localhost: 316 PCSAFS130: Client 172.18.4.94 user
    pcguest stoppe
    d connection tid 117
    Jan 21 08:51:23 localhost: 316 PCSAFS130: Client 172.18.4.94 user
    pcguest stoppe
    d connection tid 118
    Jan 21 08:51:23 localhost: 316 PCSAFS130: Node 172.18.4.94 connection
    closed
    Jan 21 08:51:45 localhost: 390 PCSAFS130: Connect 270 Session 121 
    start on node
     172.18.4.16 user pcguest for service win_wp52
    Jan 21 08:52:11 localhost: 320 PCSAFS130: Connect 271 Session 68  start
    on node 
    172.18.4.39 user pcguest for service win_word
    Jan 21 08:52:19 localhost: 229 PCSAFS130: Connect 272 Session 3  start
    on node 1
    72.18.4.76 user pcguest for service win_wp52
    Jan 21 08:52:41 localhost: 403 PCSAFS130: Starting server with
    172.18.4.80 and n
    etbios name PC780
    Jan 21 08:52:42 localhost: 403 PCSAFS130: Connect 273 Session 133 
    start on node
     172.18.4.80 user pcguest for service ccm
    Jan 21 08:52:42 localhost: 403 PCSAFS130: Connect 274 Session 133 
    start on node
     172.18.4.80 user pcguest for service ccd
    Jan 21 08:52:49 localhost: 404 PCSAFS130: Starting server with
    172.18.4.74 and n
    etbios name PC728
    Jan 21 08:52:49 localhost: 404 PCSAFS130: Connect 275 Session 134 
    start on node
     172.18.4.74 user pcguest for service ccm
    Jan 21 08:52:49 localhost: 404 PCSAFS130: Connect 276 Session 134 
    start on node
     172.18.4.74 user pcguest for service ccd
    Jan 21 08:53:21 localhost: 405 PCSAFS130: Starting server with
    172.18.4.109 and 
    netbios name PC824
    Jan 21 08:53:21 localhost: 405 PCSAFS130: Connect 277 Session 135 
    start on node
     172.18.4.109 user pcguest for service ccm
    Jan 21 08:53:21 localhost: 405 PCSAFS130: Connect 278 Session 135 
    start on node
     172.18.4.109 user pcguest for service ccd
    Jan 21 08:53:43 localhost: 298 PCSAFS130: Connect 279 Session 50  start
    on node 
    172.18.4.57 user pcguest for service win_excel
    Jan 21 08:53:57 localhost: 405 PCSAFS130: Connect 280 Session 135 
    start on node
     172.18.4.109 user pcguest for service win_excel
    Jan 21 08:54:08 localhost: 406 PCSAFS130: Starting server with
    172.18.4.94 and n
    etbios name PC695
    Jan 21 08:54:08 localhost: 406 PCSAFS130: Connect 281 Session 136 
    start on node
     172.18.4.94 user pcguest for service ccm
    Jan 21 08:54:08 localhost: 406 PCSAFS130: Connect 282 Session 136 
    start on node
     172.18.4.94 user pcguest for service ccd
    Jan 21 08:54:37 localhost: 318 PCSAFS130: Client 172.18.4.82 user
    pcguest stoppe
    d connection tid 262
    Jan 21 08:54:55 localhost: 407 PCSAFS130: Starting server with
    172.18.4.37 and n
    etbios name PC669
    Jan 21 08:54:55 localhost: 407 PCSAFS130: Connect 283 Session 137 
    start on node
     172.18.4.37 user pcguest for service ccm
    Jan 21 08:54:55 localhost: 407 PCSAFS130: Connect 284 Session 137 
    start on node
     172.18.4.37 user pcguest for service ccd
    Jan 21 08:55:06 localhost: 408 PCSAFS130: Starting server with 10.759
    and netbio
    s name PC759
    Jan 21 08:55:06 localhost: 408 PCSAFS130: Connect 285 Session 138 
    start on node
     10.759 user pcguest for service ccm
    Jan 21 08:55:07 localhost: 408 PCSAFS130: Connect 286 Session 138 
    start on node
     10.759 user pcguest for service ccd
    Jan 21 08:55:32 localhost: 318 PCSAFS130: Connect 287 Session 66  start
    on node 
    172.18.4.82 user pcguest for service win_word
    Jan 21 08:55:34 localhost: 407 PCSAFS130: Connect 288 Session 137 
    start on node
     172.18.4.37 user pcguest for service win_word
    Jan 21 08:55:45 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:55:45 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:55:49 localhost: 407 PCSAFS130: Client 172.18.4.37 user
    pcguest stoppe
    d connection tid 288
    Jan 21 08:55:52 localhost: 409 PCSAFS130: Starting server with
    172.18.4.86 and n
    etbios name PC696
    Jan 21 08:55:52 localhost: 409 PCSAFS130: Connect 289 Session 139 
    start on node
     172.18.4.86 user pcguest for service ccm
    Jan 21 08:55:52 localhost: 409 PCSAFS130: Connect 290 Session 139 
    start on node
     172.18.4.86 user pcguest for service ccd
    Jan 21 08:55:58 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:55:58 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:56:09 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:56:09 localhost: 306 PCSAFS130: Invalid service name from
    node aspen u
    ser pcguest service ipc$
    Jan 21 08:56:23 localhost: 401 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 266
    Jan 21 08:56:23 localhost: 401 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 267
    Jan 21 08:56:23 localhost: 401 PCSAFS130: Client 172.18.4.5 user mikota
    stopped 
    connection tid 268
    Jan 21 08:56:23 localhost: 401 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 269
    Jan 21 08:56:23 localhost: 401 PCSAFS130: Node 172.18.4.5 connection
    closed
    Jan 21 08:56:23 localhost: 410 PCSAFS130: Starting server with
    172.18.4.155 and 
    netbios name PC834
    Jan 21 08:56:23 localhost: 410 PCSAFS130: Connect 291 Session 140 
    start on node
     172.18.4.155 user pcguest for service ccm
    Jan 21 08:56:24 localhost: 410 PCSAFS130: Connect 292 Session 140 
    start on node
     172.18.4.155 user pcguest for service ccd
    Jan 21 08:56:49 localhost: 404 PCSAFS130: Connect 293 Session 134 
    start on node
     172.18.4.74 user pcguest for service win_word
    Jan 21 08:56:51 localhost: 380 PCSAFS130: Connect 294 Session 114 
    start on node
     172.18.4.90 user pcguest for service wp51
    Jan 21 08:56:54 localhost: 411 PCSAFS130: Starting server with
    172.18.4.84 and n
    etbios name PC721
    Jan 21 08:56:54 localhost: 411 PCSAFS130: Connect 295 Session 141 
    start on node
     172.18.4.84 user pcguest for service ccm
    Jan 21 08:56:54 localhost: 411 PCSAFS130: Connect 296 Session 141 
    start on node
     172.18.4.84 user pcguest for service ccd
    Jan 21 08:56:56 localhost: 412 PCSAFS130: Starting server with 10.778
    and netbio
    s name PC778
    Jan 21 08:56:56 localhost: 412 PCSAFS130: Connect 297 Session 142 
    start on node
     10.778 user pcguest for service ccm
    Jan 21 08:57:50 localhost: 410 PCSAFS130: Connect 298 Session 140 
    start on node
     172.18.4.155 user pcguest for service vscan
    Jan 21 08:58:29 localhost: 413 PCSAFS130: Starting server with
    172.18.4.152 and 
    netbios name PC818
    Jan 21 08:58:29 localhost: 413 PCSAFS130: Connect 299 Session 143 
    start on node
     172.18.4.152 user pcguest for service ccm
    Jan 21 08:58:29 localhost: 413 PCSAFS130: Connect 300 Session 143 
    start on node
     172.18.4.152 user pcguest for service ccd
    Jan 21 08:59:05 localhost: 410 PCSAFS130: Client 172.18.4.155 user
    pcguest stopp
    ed connection tid 298
    Jan 21 08:59:21 localhost: 410 PCSAFS130: Connect 301 Session 140 
    start on node
     172.18.4.155 user pcguest for service vscan
    Jan 21 08:59:24 localhost: 414 PCSAFS130: Starting server with
    172.18.4.44 and n
    etbios name PC299
    Jan 21 08:59:24 localhost: 414 PCSAFS130: Connect 302 Session 144 
    start on node
     172.18.4.44 user pcguest for service ccm
    Jan 21 08:59:24 localhost: 414 PCSAFS130: Connect 303 Session 144 
    start on node
     172.18.4.44 user pcguest for service ccd
    Jan 21 08:59:30 localhost: 291 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 96
    Jan 21 08:59:36 localhost: 410 PCSAFS130: Client 172.18.4.155 user
    pcguest stopp
    ed connection tid 301
    Jan 21 09:00:09 localhost: 418 PCSAFS130: Starting server with
    172.18.4.3 and ne
    tbios name PC772
    Jan 21 09:00:09 localhost: 418 PCSAFS130: Connect 304 Session 145 
    start on node
     172.18.4.3 user pcguest for service ccd
    Jan 21 09:00:09 localhost: 419 PCSAFS130: Starting server with
    172.18.4.156 and 
    netbios name PC821
    Jan 21 09:00:09 localhost: 419 PCSAFS130: Connect 305 Session 146 
    start on node
     172.18.4.156 user pcguest for service ccm
    Jan 21 09:00:09 localhost: 419 PCSAFS130: Connect 306 Session 146 
    start on node
     172.18.4.156 user pcguest for service ccd
    Jan 21 09:00:11 localhost: 420 PCSAFS130: Starting server with
    172.18.4.40 and n
    etbios name PC289
    Jan 21 09:00:11 localhost: 420 PCSAFS130: Connect 307 Session 147 
    start on node
     172.18.4.40 user pcguest for service ccm
    Jan 21 09:00:11 localhost: 420 PCSAFS130: Connect 308 Session 147 
    start on node
     172.18.4.40 user pcguest for service ccd
    Jan 21 09:00:23 localhost: 420 PCSAFS130: Connect 309 Session 147 
    start on node
     172.18.4.40 user pcguest for service win_excel
    Jan 21 09:00:33 localhost: 421 PCSAFS130: Starting server with 10.636
    and netbio
    s name PC636
    Jan 21 09:00:33 localhost: 421 PCSAFS130: Connect 310 Session 148 
    start on node
     10.636 user pcguest for service ccm
    Jan 21 09:00:34 localhost: 421 PCSAFS130: Connect 311 Session 148 
    start on node
     10.636 user pcguest for service ccd
    Jan 21 09:00:38 localhost: 397 PCSAFS130: Connect 312 Session 128 
    start on node
     172.18.4.19 user pcguest for service win_wp52
    Jan 21 09:00:39 localhost: 342 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 185
    Jan 21 09:00:46 localhost: 342 PCSAFS130: Connect 313 Session 80  start
    on node 
    172.18.4.32 user pcguest for service win_word
    Jan 21 09:00:52 localhost: 396 PCSAFS130: Connect 314 Session 127 
    start on node
     172.18.4.15 user pcguest for service win_wp52
    Jan 21 09:00:57 localhost: 423 PCSAFS130: Starting server with 10.519
    and netbio
    s name PC519
    Jan 21 09:00:57 localhost: 423 PCSAFS130: Connect 315 Session 149 
    start on node
     Jan 21 09:00:58 localhost: 422 PCSAFS130: Starting server with
    172.18.4.7 and ne
    tbios name PC361
    Jan 21 09:00:58 localhost: 422 PCSAFS130: Connect 316 Session 150 
    start on node
     172.18.4.7 user pcguest for service ccm
    Jan 21 09:00:58 localhost: 422 PCSAFS130: Connect 317 Session 150 
    start on node
     172.18.4.7 user pcguest for service ccd
    Jan 21 09:02:12 localhost: 424 PCSAFS130: Starting server with 10.745
    and netbio
    s name PC745
    Jan 21 09:02:12 localhost: 424 PCSAFS130: Connect 318 Session 151 
    start on node
     10.745 user pcguest for service ccd
    Jan 21 09:02:26 localhost: 392 PCSAFS130: Connect 319 Session 123 
    start on node
     172.18.4.107 user pcguest for service win_word
    Jan 21 09:02:35 localhost: 425 PCSAFS130: Starting server with 10.684
    and netbio
    s name PC684
    Jan 21 09:02:35 localhost: 425 PCSAFS130: Connect 320 Session 152 
    start on node
     10.684 user pcguest for service win_word
    Jan 21 09:02:39 localhost: 291 PCSAFS130: Connect 321 Session 43  start
    on node 
    172.18.4.87 user pcguest for service pdox35
    Jan 21 09:02:39 localhost: 291 PCSAFS130: Connect 322 Session 43  start
    on node 
    172.18.4.87 user pcguest for service pdusrdata
    Jan 21 09:03:03 localhost: 426 PCSAFS130: Starting server with 10.743
    and netbio
    s name PC743
    Jan 21 09:03:03 localhost: 426 PCSAFS130: Connect 323 Session 153 
    start on node
     10.743 user pcguest for service ccd
    Jan 21 09:03:13 localhost: 298 PCSAFS130: Client 172.18.4.57 user
    pcguest stoppe
    d connection tid 279
    Jan 21 09:03:24 localhost: 298 PCSAFS130: Client 172.18.4.57 user
    pcguest stoppe
    d connection tid 89
    Jan 21 09:03:24 localhost: 298 PCSAFS130: Client 172.18.4.57 user
    pcguest stoppe
    d connection tid 90
    Jan 21 09:03:24 localhost: 298 PCSAFS130: Node 172.18.4.57 connection
    closed
    Jan 21 09:03:33 localhost: 317 PCSAFS130: Connect 324 Session 65  start
    on node 
    172.18.4.63 user pcguest for service win_excel
    Jan 21 09:03:36 localhost: 427 PCSAFS130: Starting server with
    172.18.4.122 and 
    netbios name HEIN_PC
    Jan 21 09:03:36 localhost: 427 PCSAFS130: Connect 325 Session 154 
    start on node
     172.18.4.122 user pcguest for service ccm
    Jan 21 09:03:36 localhost: 427 PCSAFS130: Connect 326 Session 154 
    start on node
     172.18.4.122 user pcguest for service ccd
    Jan 21 09:03:36 localhost: 427 PCSAFS130: Connect 327 Session 154 
    start on node
     172.18.4.122 user hein for service isw
    Jan 21 09:03:37 localhost: 427 PCSAFS130: Connect 328 Session 154 
    start on node
     172.18.4.122 user hein for service ac
    Jan 21 09:03:37 localhost: 427 PCSAFS130: Connect 329 Session 154 
    start on node
     172.18.4.122 user pcguest for service netc_data
    Jan 21 09:03:39 localhost: 428 PCSAFS130: Starting server with
    172.18.4.72 and n
    etbios name PC723
    Jan 21 09:03:39 localhost: 428 PCSAFS130: Connect 330 Session 155 
    start on node
     172.18.4.72 user pcguest for service ccm
    Jan 21 09:03:39 localhost: 428 PCSAFS130: Connect 331 Session 155 
    start on node
     172.18.4.72 user pcguest for service ccd
    Jan 21 09:03:48 localhost: 342 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 313
    Jan 21 09:03:49 localhost: 428 PCSAFS130: Connect 332 Session 155 
    start on node
     172.18.4.72 user pcguest for service pdox40
    Jan 21 09:03:53 localhost: 342 PCSAFS130: Connect 333 Session 80  start
    on node 
    172.18.4.32 user pcguest for service win_word
    Jan 21 09:03:56 localhost: 342 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 333
    Jan 21 09:04:01 localhost: 342 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 156
    Jan 21 09:04:01 localhost: 342 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 157
    Jan 21 09:04:01 localhost: 342 PCSAFS130: Node 172.18.4.32 connection
    closed
    Jan 21 09:04:05 localhost: 239 PCSAFS130: Client 10.532 user pcguest
    stopped con
    nection tid 263
    Jan 21 09:04:13 localhost: 428 PCSAFS130: Client 172.18.4.72 user
    pcguest stoppe
    d connection tid 332
    Jan 21 09:04:18 localhost: 239 PCSAFS130: Connect 334 Session 8  start
    on node 1
    0.532 user pcguest for service win_proj
    Jan 21 09:04:19 localhost: 428 PCSAFS130: Connect 335 Session 155 
    start on node
     172.18.4.72 user pcguest for service win_excel
    Jan 21 09:04:43 localhost: 429 PCSAFS130: Starting server with
    172.18.4.32 and n
    etbios name PC769
    Jan 21 09:04:44 localhost: 429 PCSAFS130: Connect 336 Session 156 
    start on node
     172.18.4.32 user pcguest for service ccm
    Jan 21 09:04:44 localhost: 429 PCSAFS130: Connect 337 Session 156 
    start on node
     172.18.4.32 user pcguest for service ccd
    Jan 21 09:04:47 localhost: 291 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 321
    Jan 21 09:04:47 localhost: 291 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 322
    Jan 21 09:04:48 localhost: 269 PCSAFS130: Client 172.18.4.45 user
    pcguest stoppe
    d connection tid 265
    Jan 21 09:04:53 localhost: 392 PCSAFS130: Client 172.18.4.107 user
    pcguest stopp
    ed connection tid 319
    Jan 21 09:04:53 localhost: 429 PCSAFS130: Connect 338 Session 156 
    start on node
     172.18.4.32 user pcguest for service win_word
    Jan 21 09:06:18 localhost: 431 PCSAFS130: Starting server with
    172.18.4.55 and n
    etbios name PC675
    Jan 21 09:06:18 localhost: 430 PCSAFS130: Starting server with
    172.18.4.132 and 
    netbios name PC823
    Jan 21 09:06:19 localhost: 430 PCSAFS130: Connect 339 Session 157 
    start on node
     172.18.4.132 user pcguest for service ccm
    Jan 21 09:06:19 localhost: 431 PCSAFS130: Connect 340 Session 158 
    start on node
     172.18.4.55 user pcguest for service ccm
    Jan 21 09:06:19 localhost: 430 PCSAFS130: Connect 341 Session 157 
    start on node
     172.18.4.132 user pcguest for service ccd
    Jan 21 09:06:19 localhost: 431 PCSAFS130: Connect 342 Session 158 
    start on node
     172.18.4.55 user pcguest for service ccd
    Jan 21 09:06:24 localhost: 432 PCSAFS130: Starting server with
    172.18.4.149 and 
    netbios name PC649
    Jan 21 09:06:24 localhost: 432 PCSAFS130: Connect 343 Session 159 
    start on node
     172.18.4.149 user pcguest for service ccm
    Jan 21 09:06:24 localhost: 432 PCSAFS130: Connect 344 Session 159 
    start on node
     172.18.4.149 user pcguest for service ccd
    Jan 21 09:06:51 localhost: 433 PCSAFS130: Starting server with
    172.18.4.95 and n
    etbios name PC372
    Jan 21 09:06:51 localhost: 433 PCSAFS130: Connect 345 Session 160 
    start on node
     172.18.4.95 user pcguest for service ccm
    Jan 21 09:06:51 localhost: 433 PCSAFS130: Connect 346 Session 160 
    start on node
     172.18.4.95 user pcguest for service ccd
    Jan 21 09:07:03 localhost: 432 PCSAFS130: Client 172.18.4.149 user
    pcguest stopp
    ed connection tid 343
    Jan 21 09:07:03 localhost: 432 PCSAFS130: Client 172.18.4.149 user
    pcguest stopp
    ed connection tid 344
    Jan 21 09:07:03 localhost: 432 PCSAFS130: Node 172.18.4.149 connection
    closed
    Jan 21 09:07:24 localhost: 392 PCSAFS130: Connect 347 Session 123 
    start on node
     172.18.4.107 user pcguest for service win_word
    Jan 21 09:07:40 localhost: 434 PCSAFS130: Starting server with
    172.18.4.111 and 
    netbios name 402
    Jan 21 09:07:40 localhost: 434 PCSAFS130: Connect 348 Session 161 
    start on node
     172.18.4.111 user pcguest for service ac
    Jan 21 09:07:50 localhost: 434 PCSAFS130: Connect 349 Session 161 
    start on node
     172.18.4.111 user pcguest for service ccm
    Jan 21 09:07:50 localhost: 434 PCSAFS130: Connect 350 Session 161 
    start on node
     172.18.4.111 user pcguest for service ccd
    Jan 21 09:07:55 localhost: 438 PCSAFS130: Starting server with
    172.18.4.116 and 
    netbios name PC701
    Jan 21 09:07:55 localhost: 438 PCSAFS130: Connect 351 Session 162 
    start on node
     172.18.4.116 user pcguest for service ccm
    Jan 21 09:07:55 localhost: 438 PCSAFS130: Connect 352 Session 162 
    start on node
     172.18.4.116 user pcguest for service ccd
    Jan 21 09:08:01 localhost: 427 PCSAFS130: Connect 353 Session 154 
    start on node
    Jan 21 09:08:04 localhost: 444 PCSAFS130: Starting server with
    172.18.4.113 and 
    netbios name PC512
    Jan 21 09:08:04 localhost: 444 PCSAFS130: Connect 354 Session 163 
    start on node
     172.18.4.113 user pcguest for service ccm
    Jan 21 09:08:04 localhost: 444 PCSAFS130: Connect 355 Session 163 
    start on node
     172.18.4.113 user pcguest for service ccd
    Jan 21 09:08:07 localhost: 269 PCSAFS130: Connect 356 Session 21  start
    on node 
    172.18.4.45 user pcguest for service win_excel
    Jan 21 09:08:22 localhost: 447 PCSAFS130: Starting server with
    172.18.4.149 and 
    netbios name PC649
    Jan 21 09:08:22 localhost: 447 PCSAFS130: Connect 357 Session 164 
    start on node
     172.18.4.149 user pcguest for service ccm
    Jan 21 09:08:22 localhost: 447 PCSAFS130: Connect 358 Session 164 
    start on node
     172.18.4.149 user pcguest for service ccd
    Jan 21 09:08:30 localhost: 447 PCSAFS130: Connect 359 Session 164 
    start on node
     172.18.4.149 user pcguest for service win_excel
    Jan 21 09:09:25 localhost: 468 PCSAFS130: Starting server with
    172.18.4.119 and 
    netbios name PC687
    Jan 21 09:09:25 localhost: 468 PCSAFS130: Connect 360 Session 165 
    start on node
     172.18.4.119 user pcguest for service ccm
    Jan 21 09:09:25 localhost: 468 PCSAFS130: Connect 361 Session 165 
    start on node
     172.18.4.119 user pcguest for service ccd
    Jan 21 09:09:59 localhost: 428 PCSAFS130: Client 172.18.4.72 user
    pcguest stoppe
    d connection tid 335
    Jan 21 09:10:07 localhost: 428 PCSAFS130: Connect 362 Session 155 
    start on node
     172.18.4.72 user pcguest for service pdox40
    Jan 21 09:10:15 localhost: 473 PCSAFS130: Starting server with
    172.18.4.1 and ne
    tbios name PC819
    Jan 21 09:10:15 localhost: 473 PCSAFS130: Connect 363 Session 166 
    start on node
     172.18.4.1 user pcguest for service ccm
    Jan 21 09:10:15 localhost: 473 PCSAFS130: Connect 364 Session 166 
    start on node
     172.18.4.1 user pcguest for service ccd
    Jan 21 09:10:48 localhost: 474 PCSAFS130: Starting server with
    172.18.4.50 and n
    etbios name PC629
    Jan 21 09:10:48 localhost: 474 PCSAFS130: Connect 365 Session 167 
    start on node
     172.18.4.50 user pcguest for service ccm
    Jan 21 09:10:48 localhost: 474 PCSAFS130: Connect 366 Session 167 
    start on node
     172.18.4.50 user pcguest for service ccd
    Jan 21 09:10:50 localhost: 475 PCSAFS130: Starting server with
    172.18.4.121 and 
    netbios name PC691
    Jan 21 09:10:50 localhost: 475 PCSAFS130: Connect 367 Session 168 
    start on node
     172.18.4.121 user pcguest for service ccm
    Jan 21 09:10:50 localhost: 475 PCSAFS130: Connect 368 Session 168 
    start on node
     172.18.4.121 user pcguest for service ccd
    Jan 21 09:10:53 localhost: 375 PCSAFS130: Connect 369 Session 109 
    start on node
     172.18.4.129 user pcguest for service win_word
    Jan 21 09:11:12 localhost: 269 PCSAFS130: Client 172.18.4.45 user
    pcguest stoppe
    d connection tid 356
    Jan 21 09:11:14 localhost: 429 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 338
    Jan 21 09:11:16 localhost: 433 PCSAFS130: Connect 370 Session 160 
    start on node
     172.18.4.95 user pcguest for service wp51
    Jan 21 09:11:44 localhost: 374 PCSAFS130: Connect 371 Session 108 
    start on node
     172.18.4.75 user pcguest for service wp51
    Jan 21 09:12:03 localhost: 476 PCSAFS130: Starting server with
    172.18.4.77 and n
    etbios name PC305
    Jan 21 09:12:03 localhost: 476 PCSAFS130: Connect 372 Session 169 
    start on node
     172.18.4.77 user pcguest for service ccd
    Jan 21 09:12:16 localhost: 318 PCSAFS130: Client 172.18.4.82 user
    pcguest stoppe
    d connection tid 287
    Jan 21 09:13:09 localhost: 427 PCSAFS130: Connect 373 Session 154 
    start on node
     172.18.4.122 user pcguest for service win_excel
    Jan 21 09:13:14 localhost: 478 PCSAFS130: Starting server with 10.272
    and netbio
    s name PC812
    Jan 21 09:13:14 localhost: 478 PCSAFS130: Connect 374 Session 170 
    start on node
     10.272 user pcguest for service ccm
    Jan 21 09:13:16 localhost: 478 PCSAFS130: Connect 375 Session 170 
    start on node
     10.272 user pcguest for service ccd
    Jan 21 09:13:27 localhost: 421 PCSAFS130: Connect 376 Session 148 
    start on node
     10.636 user pcguest for service win_excel
    Jan 21 09:13:30 localhost: 414 PCSAFS130: Connect 377 Session 144 
    start on node
     172.18.4.44 user pcguest for service wp51
    Jan 21 09:13:46 localhost: 410 PCSAFS130: Client 172.18.4.155 user
    pcguest stopp
    ed connection tid 291
    Jan 21 09:13:46 localhost: 410 PCSAFS130: Client 172.18.4.155 user
    pcguest stopp
    ed connection tid 292
    Jan 21 09:13:46 localhost: 410 PCSAFS130: Node 172.18.4.155 connection
    closed
    Jan 21 09:14:00 localhost: 479 PCSAFS130: Starting server with
    172.18.4.108 and 
    netbios name HIGBEE
    Jan 21 09:14:00 localhost: 479 PCSAFS130: Connect 378 Session 171 
    start on node
     172.18.4.108 user pcguest for service ccm
    Jan 21 09:14:01 localhost: 479 PCSAFS130: Connect 379 Session 171 
    start on node
     172.18.4.108 user pcguest for service ccd
    Jan 21 09:14:16 localhost: 480 PCSAFS130: Starting server with
    172.18.4.115 and 
    netbios name PC720
    Jan 21 09:14:16 localhost: 480 PCSAFS130: Connect 380 Session 172 
    start on node
     172.18.4.115 user pcguest for service ccm
    Jan 21 09:14:16 localhost: 480 PCSAFS130: Connect 381 Session 172 
    start on node
     172.18.4.115 user pcguest for service ccd
                                Press RETURN to continue
    Jan 21 09:14:41 localhost: 481 PCSAFS130: Starting server with
    172.18.4.117 and 
    netbios name PC665
    Jan 21 09:14:41 localhost: 481 PCSAFS130: Connect 382 Session 173 
    start on node
     172.18.4.117 user pcguest for service ccm
    Jan 21 09:14:41 localhost: 481 PCSAFS130: Connect 383 Session 173 
    start on node
     172.18.4.117 user pcguest for service ccd
    Jan 21 09:14:41 localhost: 318 PCSAFS130: Connect 384 Session 66  start
    on node 
    172.18.4.82 user pcguest for service win_word
    Jan 21 09:14:43 localhost: 482 PCSAFS130: Starting server with
    172.18.4.155 and 
    netbios name PC834
    Jan 21 09:14:43 localhost: 482 PCSAFS130: Connect 385 Session 174 
    start on node
     172.18.4.155 user pcguest for service ccm
    Jan 21 09:14:43 localhost: 482 PCSAFS130: Connect 386 Session 174 
    start on node
     172.18.4.155 user pcguest for service ccd
    Jan 21 09:15:05 localhost: 239 PCSAFS130: Client 10.532 user pcguest
    stopped con
    nection tid 153
    Jan 21 09:15:58 localhost: 372 PCSAFS130: Client 172.18.4.13 user
    pcguest stoppe
    d connection tid 195
    Jan 21 09:15:58 localhost: 372 PCSAFS130: Node 172.18.4.13 connection
    closed
    Jan 21 09:16:07 localhost: 284 PCSAFS130: Connect 387 Session 36  start
    on node 
    172.18.4.141 user pcguest for service win_word
    Jan 21 09:16:16 localhost: 481 PCSAFS130: Connect 388 Session 173 
    start on node
     172.18.4.117 user pcguest for service win_word
    Jan 21 09:16:22 localhost: 486 PCSAFS130: Starting server with
    172.18.4.13 and n
    etbios name PC781
    Jan 21 09:16:22 localhost: 486 PCSAFS130: Connect 389 Session 175 
    start on node
     172.18.4.13 user pcguest for service ccm
    Jan 21 09:16:22 localhost: 486 PCSAFS130: Connect 390 Session 175 
    start on node
     172.18.4.13 user pcguest for service ccd
    Jan 21 09:16:42 localhost: 478 PCSAFS130: Node 10.272 connection closed
    Jan 21 09:16:50 localhost: 487 PCSAFS130: Starting server with
    172.18.4.77 and n
    etbios name PC305
    Jan 21 09:16:50 localhost: 487 PCSAFS130: Connect 391 Session 176 
    start on node
     172.18.4.77 user pcguest for service ccd
    Jan 21 09:16:50 localhost: 426 PCSAFS130: Node 10.743 connection closed
    Jan 21 09:16:50 localhost: 300 PCSAFS130: Node 10.837 connection closed
    Jan 21 09:16:54 localhost: 488 PCSAFS130: Starting server with
    172.18.4.105 and 
    netbios name PC325
    Jan 21 09:16:54 localhost: 488 PCSAFS130: Connect 392 Session 177 
    start on node
     172.18.4.105 user pcguest for service ccm
    Jan 21 09:16:54 localhost: 488 PCSAFS130: Connect 393 Session 177 
    start on node
     172.18.4.105 user pcguest for service ccd
    Jan 21 09:16:56 localhost: 428 PCSAFS130: Client 172.18.4.72 user
    pcguest stoppe
    d connection tid 362
    Jan 21 09:16:56 localhost: 489 PCSAFS130: Starting server with
    172.18.4.132 and 
    netbios name PC823
    Jan 21 09:16:57 localhost: 489 PCSAFS130: Connect 394 Session 178 
    start on node
     172.18.4.132 user pcguest for service ccm
    Jan 21 09:17:05 localhost: 489 PCSAFS130: Connect 395 Session 178 
    start on node
     172.18.4.132 user pcguest for service ccd
    Jan 21 09:17:05 localhost: 490 PCSAFS130: Starting server with 10.272
    and netbio
    s name PC812
    Jan 21 09:17:05 localhost: 490 PCSAFS130: Connect 396 Session 179 
    start on node
     10.272 user pcguest for service ccm
    Jan 21 09:17:11 localhost: 490 PCSAFS130: Connect 397 Session 179 
    start on node
     10.272 user pcguest for service ccd
    Jan 21 09:17:13 localhost: 395 PCSAFS130: Client 172.18.4.38 user
    pcguest stoppe
    d connection tid 246
    Jan 21 09:17:23 localhost: 291 PCSAFS130: Connect 398 Session 43  start
    on node 
    172.18.4.87 user pcguest for service win_word
    Jan 21 09:17:25 localhost: 476 PCSAFS130: Node 172.18.4.77 connection
    closed
    Jan 21 09:17:29 localhost: 444 PCSAFS130: Connect 399 Session 163 
    start on node
     172.18.4.113 user pcguest for service win_excel
    Jan 21 09:17:32 localhost: 491 PCSAFS130: Starting server with
    172.18.4.103 and 
    netbios name PC833
    Jan 21 09:17:32 localhost: 491 PCSAFS130: Connect 400 Session 180 
    start on node
     172.18.4.103 user pcguest for service ccm
    Jan 21 09:17:32 localhost: 491 PCSAFS130: Connect 401 Session 180 
    start on node
     172.18.4.103 user pcguest for service ccd
    Jan 21 09:17:59 localhost: 492 PCSAFS130: Starting server with 10.638
    and netbio
    s name MODEM1
    Jan 21 09:17:59 localhost: 492 PCSAFS130: Connect 402 Session 181 
    start on node
     10.638 user pcguest for service ccm
    Jan 21 09:18:00 localhost: 492 PCSAFS130: Connect 403 Session 181 
    start on node
     10.638 user pcguest for service ccd
    Jan 21 09:18:02 localhost: 430 PCSAFS130: Node 172.18.4.132 connection
    closed
    Jan 21 09:18:05 localhost: 428 PCSAFS130: Connect 404 Session 155 
    start on node
     172.18.4.72 user pcguest for service win_excel
    Jan 21 09:19:01 localhost: 291 PCSAFS130: Connect 405 Session 43  start
    on node 
    172.18.4.87 user pcguest for service win_wp61
    Jan 21 09:20:09 localhost: 321 PCSAFS130: Connect 406 Session 69  start
    on node 
    172.18.4.98 user pcguest for service win_word
    Jan 21 09:20:18 localhost: 493 PCSAFS130: Starting server with
    172.18.4.46 and n
    etbios name PC742
    Jan 21 09:20:18 localhost: 493 PCSAFS130: Connect 407 Session 182 
    start on node
     172.18.4.46 user pcguest for service ccd
    Jan 21 09:20:34 localhost: 494 PCSAFS130: Starting server with
    172.18.4.140 and 
    netbios name PC308
    Jan 21 09:20:34 localhost: 494 PCSAFS130: Connect 408 Session 183 
    start on node
     172.18.4.140 user pcguest for service ccd
    Jan 21 09:21:07 localhost: 291 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 405
    Jan 21 09:21:34 localhost: 284 PCSAFS130: Client 172.18.4.141 user
    pcguest stopp
    ed connection tid 387
    Jan 21 09:21:39 localhost: 306 PCSAFS130: NETBIOS packet error,
    expecting SESSIO
    N_MESSAGE
    Jan 21 09:21:39 localhost: 306 PCSAFS130: Node pc8056.trimet.or
    connection close
    d
    Jan 21 09:21:40 localhost: 373 PCSAFS130: Connect 409 Session 107 
    start on node
     172.18.4.93 user pcguest for service wp51
    Jan 21 09:21:45 localhost: 320 PCSAFS130: Connect 410 Session 68  start
    on node 
    172.18.4.39 user pcguest for service win_wp61
    Jan 21 09:21:59 localhost: 291 PCSAFS130: Connect 411 Session 43  start
    on node 
    172.18.4.87 user pcguest for service win_wp61
    Jan 21 09:22:48 localhost: 493 PCSAFS130: Node 172.18.4.46 connection
    closed
    Jan 21 09:23:03 localhost: 495 PCSAFS130: Starting server with
    172.18.4.138 and 
    netbios name PC774
    Jan 21 09:23:03 localhost: 495 PCSAFS130: Connect 412 Session 184 
    start on node
     172.18.4.138 user pcguest for service ccm
    Jan 21 09:23:03 localhost: 495 PCSAFS130: Connect 413 Session 184 
    start on node
     172.18.4.138 user pcguest for service ccd
    Jan 21 09:23:03 localhost: 495 PCSAFS130: Connect 414 Session 184 
    start on node
     172.18.4.138 user webber for service isw
    Jan 21 09:23:07 localhost: 250 PCSAFS130: Client 172.18.4.79 user
    pcguest stoppe
    d connection tid 20
    Jan 21 09:23:12 localhost: 285 PCSAFS130: Client 172.18.4.65 user
    pcguest stoppe
    d connection tid 189
    Jan 21 09:23:28 localhost: 285 PCSAFS130: Connect 415 Session 37  start
    on node 
    172.18.4.65 user pcguest for service vscan
    Jan 21 09:23:52 localhost: 521 PCSAFS130: Starting server with
    172.18.4.46 and n
    etbios name PC742
    Jan 21 09:23:52 localhost: 521 PCSAFS130: Connect 416 Session 185 
    start on node
     172.18.4.46 user pcguest for service ccd
    Jan 21 09:23:59 localhost: 526 PCSAFS130: Starting server with
    172.18.4.14 and n
    etbios name PC788
    Jan 21 09:23:59 localhost: 526 PCSAFS130: Connect 417 Session 186 
    start on node
     172.18.4.14 user pcguest for service ccm
    Jan 21 09:23:59 localhost: 526 PCSAFS130: Connect 418 Session 186 
    start on node
     172.18.4.14 user pcguest for service ccd
    Jan 21 09:24:01 localhost: 491 PCSAFS130: Connect 419 Session 180 
    start on node
     172.18.4.103 user pcguest for service vscan
    Jan 21 09:24:09 localhost: 320 PCSAFS130: Client 172.18.4.39 user
    pcguest stoppe
    d connection tid 410
    Jan 21 09:24:18 localhost: 429 PCSAFS130: Connect 420 Session 156 
    start on node
     172.18.4.32 user pcguest for service pkware
    Jan 21 09:24:30 localhost: 534 PCSAFS130: Starting server with
    172.18.4.130 and 
    netbios name PC660
    Jan 21 09:24:31 localhost: 534 PCSAFS130: Connect 421 Session 187 
    start on node
     172.18.4.130 user pcguest for service ccm
    Jan 21 09:24:31 localhost: 534 PCSAFS130: Connect 422 Session 187 
    start on node
     172.18.4.130 user pcguest for service ccd
    Jan 21 09:24:32 localhost: 429 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 420
    Jan 21 09:24:46 localhost: 285 PCSAFS130: Client 172.18.4.65 user
    pcguest stoppe
    d connection tid 415
    Jan 21 09:24:49 localhost: 491 PCSAFS130: Client 172.18.4.103 user
    pcguest stopp
    ed connection tid 419
    Jan 21 09:24:53 localhost: 429 PCSAFS130: Connect 423 Session 156 
    start on node
     172.18.4.32 user pcguest for service pkware
    Jan 21 09:25:13 localhost: 285 PCSAFS130: Connect 424 Session 37  start
    on node 
    172.18.4.65 user pcguest for service vscan
    Jan 21 09:25:14 localhost: 491 PCSAFS130: Connect 425 Session 180 
    start on node
     172.18.4.103 user pcguest for service vscan
    Jan 21 09:25:19 localhost: 429 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 423
    Jan 21 09:26:05 localhost: 285 PCSAFS130: Client 172.18.4.65 user
    pcguest stoppe
    d connection tid 424
    Jan 21 09:26:11 localhost: 285 PCSAFS130: Connect 426 Session 37  start
    on node 
    172.18.4.65 user pcguest for service vscan
    Jan 21 09:26:23 localhost: 491 PCSAFS130: Client 172.18.4.103 user
    pcguest stopp
    ed connection tid 425
    Jan 21 09:26:32 localhost: 491 PCSAFS130: Connect 427 Session 180 
    start on node
     172.18.4.103 user pcguest for service vscan
    Jan 21 09:27:11 localhost: 345 PCSAFS130: Node 10.101 connection closed
    Jan 21 09:27:16 localhost: 562 PCSAFS130: Starting server with
    172.18.4.77 and n
    etbios name PC305
    Jan 21 09:27:16 localhost: 562 PCSAFS130: Connect 428 Session 188 
    start on node
     172.18.4.77 user pcguest for service ccd
    Jan 21 09:27:17 localhost: 364 PCSAFS130: Node 10.293 connection closed
    Jan 21 09:27:17 localhost: 324 PCSAFS130: Node 10.520 connection closed
    Jan 21 09:27:17 localhost: 266 PCSAFS130: Node 10.295 connection closed
    Jan 21 09:27:25 localhost: 274 PCSAFS130: Node 10.369 connection closed
    Jan 21 09:27:45 localhost: 291 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 411
    Jan 21 09:27:48 localhost: 494 PCSAFS130: Node 172.18.4.140 connection
    closed
    Jan 21 09:27:49 localhost: 563 PCSAFS130: Starting server with
    172.18.4.35 and n
    etbios name PC724
    Jan 21 09:27:49 localhost: 563 PCSAFS130: Connect 429 Session 189 
    start on node
     172.18.4.35 user pcguest for service win_word
    Jan 21 09:27:49 localhost: 491 PCSAFS130: Node 172.18.4.103 connection
    closed
    Jan 21 09:27:53 localhost: 564 PCSAFS130: Starting server with
    172.18.4.140 and 
    netbios name PC308
     Jan 21 09:27:53 localhost: 564 PCSAFS130: Connect 430 Session 190 
    start on node
     172.18.4.140 user pcguest for service ccd
    Jan 21 09:27:53 localhost: 487 PCSAFS130: Node 172.18.4.77 connection
    closed
    Jan 21 09:27:56 localhost: 489 PCSAFS130: Node 172.18.4.132 connection
    closed
    Jan 21 09:27:57 localhost: 565 PCSAFS130: Starting server with
    172.18.4.65 and n
    etbios name PC828
    Jan 21 09:27:57 localhost: 565 PCSAFS130: Connect 431 Session 191 
    start on node
     172.18.4.65 user pcguest for service vscan
    Jan 21 09:27:59 localhost: 566 PCSAFS130: Starting server with
    172.18.4.129 and 
    netbios name PC646
    Jan 21 09:28:00 localhost: 566 PCSAFS130: Connect 432 Session 192 
    start on node
     172.18.4.129 user pcguest for service win_word
    Jan 21 09:28:01 localhost: 565 PCSAFS130: Client 172.18.4.65 user
    pcguest stoppe
    d connection tid 431
    Jan 21 09:28:01 localhost: 565 PCSAFS130: Node 172.18.4.65 connection
    closed
    Jan 21 09:28:04 localhost: 375 PCSAFS130: Node 172.18.4.129 connection
    closed
    Jan 21 09:28:07 localhost: 562 PCSAFS130: Node 172.18.4.77 connection
    closed
    Jan 21 09:28:07 localhost: 567 PCSAFS130: Starting server with
    172.18.4.77 and n
    etbios name PC305
    Jan 21 09:28:07 localhost: 567 PCSAFS130: Connect 433 Session 193 
    start on node
     172.18.4.77 user pcguest for service ccd
    Jan 21 09:28:08 localhost: 310 PCSAFS130: Node 172.18.4.35 connection
    closed
    Jan 21 09:28:16 localhost: 284 PCSAFS130: Client 172.18.4.141 user
    pcguest stopp
    ed connection tid 71
    Jan 21 09:28:31 localhost: 395 PCSAFS130: Node 172.18.4.38 connection
    closed
    Jan 21 09:28:42 localhost: 414 PCSAFS130: Client 172.18.4.44 user
    pcguest stoppe
    d connection tid 377
    Jan 21 09:28:46 localhost: 285 PCSAFS130: Node 172.18.4.65 connection
    closed
    Jan 21 09:28:56 localhost: 235 PCSAFS130: Node 172.18.4.18 connection
    closed
    Jan 21 09:29:16 localhost: 568 PCSAFS130: Starting server with
    172.18.4.164 and 
    netbios name PC362
    Jan 21 09:29:16 localhost: 568 PCSAFS130: Connect 434 Session 194 
    start on node
     172.18.4.164 user pcguest for service ccd
    Jan 21 09:29:18 localhost: 389 PCSAFS130: Connect 435 Session 120 
    start on node
     172.18.4.66 user pcguest for service win_word
    Jan 21 09:29:25 localhost: 284 PCSAFS130: Connect 436 Session 36  start
    on node 
    172.18.4.141 user pcguest for service win_word
    Jan 21 09:29:40 localhost: 569 PCSAFS130: Starting server with
    172.18.4.103 and 
    netbios name PC833
    Jan 21 09:29:40 localhost: 569 PCSAFS130: Connect 437 Session 195 
    start on node
     172.18.4.103 user pcguest for service ccm
    Jan 21 09:29:40 localhost: 569 PCSAFS130: Connect 438 Session 195 
    start on node
     172.18.4.103 user pcguest for service ccd
    Jan 21 09:29:42 localhost: 409 PCSAFS130: Connect 439 Session 139 
    start on node
     172.18.4.86 user pcguest for service win_wp52
     Jan 21 09:30:00 localhost: 569 PCSAFS130: Connect 440 Session 195 
    start on node
     172.18.4.103 user pcguest for service vscan
    Jan 21 09:30:01 localhost: 573 PCSAFS130: Starting server with
    172.18.4.18 and n
    etbios name PC190
    Jan 21 09:30:01 localhost: 573 PCSAFS130: Connect 441 Session 196 
    start on node
     172.18.4.18 user pcguest for service ccd
    Jan 21 09:30:21 localhost: 563 PCSAFS130: Connect 442 Session 189 
    start on node
     172.18.4.35 user pcguest for service ccm
    Jan 21 09:30:21 localhost: 563 PCSAFS130: Connect 443 Session 189 
    start on node
     172.18.4.35 user pcguest for service ccd
    Jan 21 09:30:48 localhost: 569 PCSAFS130: Client 172.18.4.103 user
    pcguest stopp
    ed connection tid 440
    Jan 21 09:31:03 localhost: 569 PCSAFS130: Connect 444 Session 195 
    start on node
     172.18.4.103 user pcguest for service vscan
    Jan 21 09:31:08 localhost: 574 PCSAFS130: Starting server with
    172.18.4.123 and 
    netbios name PC832
    Jan 21 09:31:08 localhost: 574 PCSAFS130: Connect 445 Session 197 
    start on node
     172.18.4.123 user pcguest for service ccm
    Jan 21 09:31:08 localhost: 574 PCSAFS130: Connect 446 Session 197 
    start on node
     172.18.4.123 user pcguest for service ccd
    Jan 21 09:31:31 localhost: 575 PCSAFS130: Starting server with 10.369
    and netbio
    s name PC369
    Jan 21 09:31:31 localhost: 575 PCSAFS130: Connect 447 Session 198 
    start on node
     10.369 user pcguest for service ccd
    Jan 21 09:31:46 localhost: 576 PCSAFS130: Starting server with 10.101
    and netbio
    s name PC101
    Jan 21 09:31:46 localhost: 576 PCSAFS130: Connect 448 Session 199 
    start on node
     10.101 user pcguest for service ccd
    Jan 21 09:31:53 localhost: 405 PCSAFS130: Client 172.18.4.109 user
    pcguest stopp
    ed connection tid 280
    Jan 21 09:32:00 localhost: 569 PCSAFS130: Client 172.18.4.103 user
    pcguest stopp
    ed connection tid 444
    Jan 21 09:32:16 localhost: 577 PCSAFS130: Starting server with 9.623
    and netbios
     name RUSHTON
    Jan 21 09:32:16 localhost: 577 PCSAFS130: Connect 449 Session 200 
    start on node
     9.623 user pcguest for service ccd
    Jan 21 09:32:42 localhost: 534 PCSAFS130: Connect 450 Session 187 
    start on node
     172.18.4.130 user pcguest for service win_word
    Jan 21 09:32:55 localhost: 482 PCSAFS130: Client 172.18.4.155 user
    pcguest stopp
    ed connection tid 385
    Jan 21 09:32:55 localhost: 482 PCSAFS130: Client 172.18.4.155 user
    pcguest stopp
    ed connection tid 386
    Jan 21 09:32:55 localhost: 482 PCSAFS130: Node 172.18.4.155 connection
    closed
    Jan 21 09:33:30 localhost: 578 PCSAFS130: Starting server with
    172.18.4.47 and n
    etbios name PC309
    Jan 21 09:33:30 localhost: 578 PCSAFS130: Connect 451 Session 201 
    start on node
     172.18.4.47 user pcguest for service ccm
    Jan 21 09:34:14 localhost: 413 PCSAFS130: Client 172.18.4.152 user
    pcguest stopp
    ed connection tid 299
    Jan 21 09:34:14 localhost: 413 PCSAFS130: Client 172.18.4.152 user
    pcguest stopp
    ed connection tid 300
    Jan 21 09:34:14 localhost: 413 PCSAFS130: Node 172.18.4.152 connection
    closed
    Jan 21 09:35:08 localhost: 579 PCSAFS130: Starting server with 10.837
    and netbio
    s name PC837
    Jan 21 09:35:09 localhost: 579 PCSAFS130: Connect 452 Session 202 
    start on node
     10.837 user pcguest for service ccm
    Jan 21 09:35:09 localhost: 579 PCSAFS130: Connect 453 Session 202 
    start on node
     10.837 user pcguest for service ccd
    Jan 21 09:35:13 localhost: 580 PCSAFS130: Starting server with 10.818
    and netbio
    s name PC818
    Jan 21 09:35:13 localhost: 580 PCSAFS130: Connect 454 Session 203 
    start on node
     10.818 user pcguest for service ccm
    Jan 21 09:35:13 localhost: 580 PCSAFS130: Connect 455 Session 203 
    start on node
     10.818 user pcguest for service ccd
    Jan 21 09:35:34 localhost: 581 PCSAFS130: Starting server with 10.186
    and netbio
    s name PC186
    Jan 21 09:35:34 localhost: 581 PCSAFS130: Connect 456 Session 204 
    start on node
     10.186 user pcguest for service netc_data
    Jan 21 09:35:35 localhost: 581 PCSAFS130: Client 10.186 user pcguest
    stopped con
    nection tid 456
    Jan 21 09:35:35 localhost: 581 PCSAFS130: Node 10.186 connection closed
    Jan 21 09:35:39 localhost: 240 PCSAFS130: Connect 457 Session 9  start
    on node 1
    0.639 user pcguest for service win_word
    Jan 21 09:35:49 localhost: 397 PCSAFS130: Client 172.18.4.19 user
    pcguest stoppe
    d connection tid 312
    Jan 21 09:35:53 localhost: 582 PCSAFS130: Starting server with 10.186
    and netbio
    s name PC186
    Jan 21 09:35:54 localhost: 582 PCSAFS130: Connect 458 Session 205 
    start on node
     10.186 user pcguest for service ccd
    Jan 21 09:35:54 localhost: 582 PCSAFS130: Connect 459 Session 205 
    start on node
     10.186 user pcguest for service netc_data
    Jan 21 09:35:56 localhost: 582 PCSAFS130: Client 10.186 user pcguest
    stopped con
    nection tid 459
    Jan 21 09:36:27 localhost: 427 PCSAFS130: Client 172.18.4.122 user
    pcguest stopp
    ed connection tid 373
    Jan 21 09:36:51 localhost: 303 PCSAFS130: Connect 460 Session 54  start
    on node 
    10.183 user pcguest for service ccm
    Jan 21 09:36:52 localhost: 303 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 100
    Jan 21 09:36:52 localhost: 303 PCSAFS130: Connect 461 Session 54  start
    on node 
    10.183 user pcguest for service ccd
    Jan 21 09:37:07 localhost: 583 PCSAFS130: Starting server with
    172.18.4.155 and 
    netbios name PC834
    Jan 21 09:37:07 localhost: 583 PCSAFS130: Connect 462 Session 206 
    start on node
     172.18.4.155 user pcguest for service ccm
    Jan 21 09:37:07 localhost: 583 PCSAFS130: Connect 463 Session 206 
    start on node
     172.18.4.155 user pcguest for service ccd
    Jan 21 09:37:46 localhost: 584 PCSAFS130: Starting server with
    172.18.4.71 and n
    etbios name THE
    Jan 21 09:37:46 localhost: 584 PCSAFS130: Connect 464 Session 207 
    start on node
     172.18.4.71 user pcguest for service ccm
    Jan 21 09:37:46 localhost: 584 PCSAFS130: Connect 465 Session 207 
    start on node
     172.18.4.71 user pcguest for service ccd
    Jan 21 09:37:46 localhost: 584 PCSAFS130: Connect 466 Session 207 
    start on node
     172.18.4.71 user douglas for service isw
    Jan 21 09:37:46 localhost: 584 PCSAFS130: Connect 467 Session 207 
    start on node
     172.18.4.71 user douglas for service ac
    Jan 21 09:37:48 localhost: 585 PCSAFS130: Starting server with
    172.18.4.65 and n
    etbios name PC828
    Jan 21 09:37:48 localhost: 585 PCSAFS130: Connect 468 Session 208 
    start on node
     172.18.4.65 user pcguest for service ccm
    Jan 21 09:37:53 localhost: 586 PCSAFS130: Starting server with
    172.18.4.124 and 
    netbios name PC825
    Jan 21 09:37:53 localhost: 586 PCSAFS130: Connect 469 Session 209 
    start on node
     172.18.4.124 user pcguest for service ccm
    Jan 21 09:37:53 localhost: 586 PCSAFS130: Connect 470 Session 209 
    start on node
     172.18.4.124 user pcguest for service ccd
    Jan 21 09:37:53 localhost: 585 PCSAFS130: Connect 471 Session 208 
    start on node
     172.18.4.65 user pcguest for service ccd
    Jan 21 09:38:15 localhost: 269 PCSAFS130: Connect 472 Session 21  start
    on node 
    172.18.4.45 user pcguest for service win_excel
    Jan 21 09:38:59 localhost: 374 PCSAFS130: Client 172.18.4.75 user
    pcguest stoppe
    d connection tid 371
    Jan 21 09:39:03 localhost: 587 PCSAFS130: Starting server with
    172.18.4.114 and 
    netbios name PC770
    Jan 21 09:39:03 localhost: 587 PCSAFS130: Connect 473 Session 210 
    start on node
     172.18.4.114 user pcguest for service ccm
    Jan 21 09:39:03 localhost: 587 PCSAFS130: Connect 474 Session 210 
    start on node
     172.18.4.114 user pcguest for service ccd
    Jan 21 09:39:24 localhost: 587 PCSAFS130: Connect 475 Session 210 
    start on node
     172.18.4.114 user pcguest for service win_word
    Jan 21 09:39:33 localhost: 317 PCSAFS130: Client 172.18.4.63 user
    pcguest stoppe
    d connection tid 324
    Jan 21 09:39:38 localhost: 583 PCSAFS130: Node 172.18.4.155 connection
    closed
    Jan 21 09:39:50 localhost: 588 PCSAFS130: Starting server with
    172.18.4.155 and 
    netbios name PC834
    Jan 21 09:39:50 localhost: 588 PCSAFS130: Connect 476 Session 211 
    start on node
     172.18.4.155 user pcguest for service ccm
    Jan 21 09:39:50 localhost: 588 PCSAFS130: Connect 477 Session 211 
    start on node
     172.18.4.155 user pcguest for service ccd
    Jan 21 09:41:16 localhost: 589 PCSAFS130: Starting server with
    172.18.4.125 and 
    netbios name PC624
    Jan 21 09:41:16 localhost: 589 PCSAFS130: Connect 478 Session 212 
    start on node
     172.18.4.125 user pcguest for service ccm
    Jan 21 09:41:17 localhost: 589 PCSAFS130: Connect 479 Session 212 
    start on node
     172.18.4.125 user pcguest for service ccd
    Jan 21 09:41:29 localhost: 374 PCSAFS130: Connect 480 Session 108 
    start on node
     172.18.4.75 user pcguest for service win_excel
    Jan 21 09:41:35 localhost: 590 PCSAFS130: Starting server with
    172.18.4.9 and ne
    tbios name PC189
    Jan 21 09:41:35 localhost: 590 PCSAFS130: Connect 481 Session 213 
    start on node
     172.18.4.9 user pcguest for service ccd
    Jan 21 09:41:43 localhost: 284 PCSAFS130: Client 172.18.4.141 user
    pcguest stopp
    ed connection tid 436
    Jan 21 09:41:43 localhost: 284 PCSAFS130: Client 172.18.4.141 user
    pcguest stopp
    ed connection tid 65
    Jan 21 09:41:43 localhost: 284 PCSAFS130: Client 172.18.4.141 user
    pcguest stopp
    ed connection tid 66
    Jan 21 09:41:43 localhost: 284 PCSAFS130: Node 172.18.4.141 connection
    closed
    Jan 21 09:42:19 localhost: 591 PCSAFS130: Starting server with
    172.18.4.141 and 
    netbios name PC531
    Jan 21 09:42:19 localhost: 591 PCSAFS130: Connect 482 Session 214 
    start on node
     172.18.4.141 user pcguest for service ccm
    Jan 21 09:42:19 localhost: 591 PCSAFS130: Connect 483 Session 214 
    start on node
     172.18.4.141 user pcguest for service ccd
    
    Jan 21 09:42:36 localhost: 592 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en pipe signal at pc 431548
    Jan 21 09:42:36 localhost: 592 PCSAFS130: Node 192.168.12.100
    connection closed
    Jan 21 09:42:38 localhost: 591 PCSAFS130: Connect 484 Session 214 
    start on node
     172.18.4.141 user pcguest for service win_wp52
    Jan 21 09:42:48 localhost: 594 PCSAFS130: Starting server with
    172.18.4.120 and 
    netbios name PC694
    Jan 21 09:42:48 localhost: 594 PCSAFS130: Connect 485 Session 216 
    start on node
     172.18.4.120 user pcguest for service ccm
    Jan 21 09:42:48 localhost: 594 PCSAFS130: Connect 486 Session 216 
    start on node
     172.18.4.120 user pcguest for service ccd
    Jan 21 09:42:59 localhost: 490 PCSAFS130: Connect 487 Session 179 
    start on node
     10.272 user pcguest for service wp51
    Jan 21 09:43:00 localhost: 591 PCSAFS130: Client 172.18.4.141 user
    pcguest stopp
    ed connection tid 484
    Jan 21 09:43:05 localhost: 591 PCSAFS130: Connect 488 Session 214 
    start on node
     172.18.4.141 user pcguest for service win_wp61
    Jan 21 09:43:29 localhost: 589 PCSAFS130: Client 172.18.4.125 user
    pcguest stopp
    ed connection tid 478
    Jan 21 09:43:29 localhost: 589 PCSAFS130: Client 172.18.4.125 user
    pcguest stopp
    ed connection tid 479
    Jan 21 09:43:29 localhost: 589 PCSAFS130: Node 172.18.4.125 connection
    closed
    Jan 21 09:43:35 localhost: 594 PCSAFS130: Connect 489 Session 216 
    start on node
     172.18.4.120 user pcguest for service win_word
    Jan 21 09:43:46 localhost: 475 PCSAFS130: Connect 490 Session 168 
    start on node
     172.18.4.121 user pcguest for service win_word
    Jan 21 09:43:50 localhost: 595 PCSAFS130: Starting server with 10.370
    and netbio
    s name PC370
    Jan 21 09:43:51 localhost: 595 PCSAFS130: Connect 491 Session 217 
    start on node
     10.370 user pcguest for service ccd
    Jan 21 09:44:05 localhost: 407 PCSAFS130: Connect 492 Session 137 
    start on node
     172.18.4.37 user pcguest for service win_excel
    Jan 21 09:45:19 localhost: 371 PCSAFS130: Connect 493 Session 105 
    start on node
     172.18.4.49 user pcguest for service win_word
    Jan 21 09:45:35 localhost: 407 PCSAFS130: Connect 494 Session 137 
    start on node
     172.18.4.37 user pcguest for service win_word
    Jan 21 09:45:41 localhost: 291 PCSAFS130: Client 172.18.4.87 user
    pcguest stoppe
    d connection tid 398
    Jan 21 09:46:08 localhost: 599 PCSAFS130: Starting server with
    172.18.4.125 and 
    netbios name PC624
    Jan 21 09:46:08 localhost: 599 PCSAFS130: Connect 495 Session 218 
    start on node
     172.18.4.125 user pcguest for service ccm
    Jan 21 09:46:08 localhost: 599 PCSAFS130: Connect 496 Session 218 
    start on node
     172.18.4.125 user pcguest for service ccd
    Jan 21 09:46:27 localhost: 303 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 460
    Jan 21 09:46:27 localhost: 303 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 461
    Jan 21 09:46:27 localhost: 303 PCSAFS130: Node 10.183 connection closed
    Jan 21 09:46:30 localhost: 600 PCSAFS130: Starting server with 10.183
    and netbio
    s name PC183
    Jan 21 09:46:30 localhost: 600 PCSAFS130: Connect 497 Session 219 
    start on node
     10.183 user pcguest for service netc_data
    Jan 21 09:46:34 localhost: 600 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 497
    Jan 21 09:46:34 localhost: 600 PCSAFS130: Node 10.183 connection closed
    Jan 21 09:46:49 localhost: 495 PCSAFS130: Connect 498 Session 184 
    start on node
     172.18.4.138 user pcguest for service win_word
    Jan 21 09:46:59 localhost: 425 PCSAFS130: Node 10.684 connection closed
    Jan 21 09:47:00 localhost: 601 PCSAFS130: Starting server with
    172.18.4.5 and ne
    tbios name MIKOTA
    Jan 21 09:47:00 localhost: 601 PCSAFS130: Connect 499 Session 220 
    start on node
     172.18.4.5 user pcguest for service ccm
    Jan 21 09:47:00 localhost: 601 PCSAFS130: Connect 500 Session 220 
    start on node
     172.18.4.5 user pcguest for service ccd
    Jan 21 09:47:01 localhost: 601 PCSAFS130: Connect 501 Session 220 
    start on node
     172.18.4.5 user mikota for service isw
    Jan 21 09:47:01 localhost: 601 PCSAFS130: Connect 502 Session 220 
    start on node
     172.18.4.5 user pcguest for service winbatch
    Jan 21 09:47:07 localhost: 601 PCSAFS130: Connect 503 Session 220 
    start on node
     172.18.4.5 user pcguest for service win_wp52
    Jan 21 09:47:24 localhost: 602 PCSAFS130: Starting server with 10.684
    and netbio
    s name PC684
    Jan 21 09:47:24 localhost: 602 PCSAFS130: Connect 504 Session 221 
    start on node
     10.684 user pcguest for service ccm
    Jan 21 09:47:25 localhost: 601 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 503
    Jan 21 09:47:26 localhost: 602 PCSAFS130: Connect 505 Session 221 
    start on node
     10.684 user pcguest for service ccd
    Jan 21 09:47:45 localhost: 601 PCSAFS130: Connect 506 Session 220 
    start on node
     172.18.4.5 user pcguest for service win_excel
    Jan 21 09:47:53 localhost: 308 PCSAFS130: Node 172.18.4.99 connection
    closed
    Jan 21 09:47:57 localhost: 601 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 506
    Jan 21 09:48:21 localhost: 603 PCSAFS130: Starting server with 10.747
    and netbio
    s name PC747
    Jan 21 09:48:21 localhost: 603 PCSAFS130: Connect 507 Session 222 
    start on node
     10.747 user pcguest for service ccm
    Jan 21 09:48:22 localhost: 603 PCSAFS130: Connect 508 Session 222 
    start on node
     10.747 user pcguest for service ccd
    Jan 21 09:48:33 localhost: 604 PCSAFS130: Starting server with
    172.18.4.99 and n
    etbios name PC722
    Jan 21 09:48:33 localhost: 604 PCSAFS130: Connect 509 Session 223 
    start on node
     172.18.4.99 user pcguest for service ccm
    Jan 21 09:48:33 localhost: 604 PCSAFS130: Connect 510 Session 223 
    start on node
     172.18.4.99 user pcguest for service ccd
    Jan 21 09:49:28 localhost: 605 PCSAFS130: Starting server with 10.183
    and netbio
    s name PC183
    Jan 21 09:49:28 localhost: 605 PCSAFS130: Connect 511 Session 224 
    start on node
     10.183 user pcguest for service netc_data
    Jan 21 09:49:31 localhost: 605 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 511
    Jan 21 09:49:31 localhost: 605 PCSAFS130: Node 10.183 connection closed
    Jan 21 09:49:43 localhost: 591 PCSAFS130: Client 172.18.4.141 user
    pcguest stopp
    ed connection tid 488
    Jan 21 09:49:44 localhost: 591 PCSAFS130: Connect 512 Session 214 
    start on node
     172.18.4.141 user pcguest for service win_word
    Jan 21 09:49:47 localhost: 408 PCSAFS130: Node 10.759 connection closed
    Jan 21 09:49:50 localhost: 606 PCSAFS130: Starting server with 10.183
    and netbio
    s name PC183
    Jan 21 09:49:50 localhost: 606 PCSAFS130: Connect 513 Session 225 
    start on node
     10.183 user pcguest for service ccd
    Jan 21 09:49:52 localhost: 606 PCSAFS130: Connect 514 Session 225 
    start on node
     10.183 user pcguest for service netc_data
    Jan 21 09:49:53 localhost: 407 PCSAFS130: Client 172.18.4.37 user
    pcguest stoppe
    d connection tid 494
    Jan 21 09:49:56 localhost: 606 PCSAFS130: Client 10.183 user pcguest
    stopped con
    nection tid 514
    Jan 21 09:49:58 localhost: 317 PCSAFS130: Connect 515 Session 65  start
    on node 
    172.18.4.63 user pcguest for service win_excel
    Jan 21 09:50:23 localhost: 407 PCSAFS130: Client 172.18.4.37 user
    pcguest stoppe
    d connection tid 492
    Jan 21 09:51:40 localhost: 602 PCSAFS130: Client 10.684 user pcguest
    stopped con
    nection tid 504
    Jan 21 09:51:41 localhost: 602 PCSAFS130: Client 10.684 user pcguest
    stopped con
    nection tid 505
    Jan 21 09:51:41 localhost: 602 PCSAFS130: Node 10.684 connection closed
    Jan 21 09:51:55 localhost: 604 PCSAFS130: Connect 516 Session 223 
    start on node
     172.18.4.99 user pcguest for service win_word
    
    Jan 21 09:52:03 localhost: 607 PCSAFS130: Starting server with
    172.18.4.127 and 
    netbios name PC830
    Jan 21 09:52:03 localhost: 607 PCSAFS130: Connect 517 Session 226 
    start on node
     172.18.4.127 user pcguest for service ccm
    Jan 21 09:52:03 localhost: 607 PCSAFS130: Connect 518 Session 226 
    start on node
     172.18.4.127 user pcguest for service ccd
    Jan 21 09:52:38 localhost: 601 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 499
    Jan 21 09:52:38 localhost: 601 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 500
    Jan 21 09:52:38 localhost: 601 PCSAFS130: Client 172.18.4.5 user mikota
    stopped 
    connection tid 501
    Jan 21 09:52:38 localhost: 601 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 502
    Jan 21 09:52:38 localhost: 601 PCSAFS130: Node 172.18.4.5 connection
    closed
    Jan 21 09:53:01 localhost: 608 PCSAFS130: Starting server with 10.737
    and netbio
    s name PC737
    Jan 21 09:53:01 localhost: 608 PCSAFS130: Connect 519 Session 227 
    start on node
     10.737 user pcguest for service ccd
    Jan 21 09:53:02 localhost: 424 PCSAFS130: Node 10.745 connection closed
    Jan 21 09:53:05 localhost: 609 PCSAFS130: Starting server with
    172.18.4.77 and n
    etbios name PC305
    Jan 21 09:53:05 localhost: 609 PCSAFS130: Connect 520 Session 228 
    start on node
     172.18.4.77 user pcguest for service ccd
    Jan 21 09:53:06 localhost: 610 PCSAFS130: Starting server with
    172.18.4.5 and ne
    tbios name MIKOTA
    Jan 21 09:53:06 localhost: 610 PCSAFS130: Connect 521 Session 229 
    start on node
     172.18.4.5 user pcguest for service ccm
    Jan 21 09:53:07 localhost: 610 PCSAFS130: Connect 522 Session 229 
    start on node
     172.18.4.5 user pcguest for service ccd
    Jan 21 09:53:07 localhost: 610 PCSAFS130: Connect 523 Session 229 
    start on node
     172.18.4.5 user mikota for service isw
    Jan 21 09:53:07 localhost: 610 PCSAFS130: Connect 524 Session 229 
    start on node
     172.18.4.5 user pcguest for service winbatch
    Jan 21 09:53:41 localhost: 567 PCSAFS130: Node 172.18.4.77 connection
    closed
    Jan 21 09:53:42 localhost: 564 PCSAFS130: Node 172.18.4.140 connection
    closed
    Jan 21 09:53:53 localhost: 611 PCSAFS130: Starting server with 10.684
    and netbio
    s name PC684
    Jan 21 09:53:53 localhost: 611 PCSAFS130: Connect 525 Session 230 
    start on node
     10.684 user pcguest for service ccm
    Jan 21 09:53:54 localhost: 611 PCSAFS130: Connect 526 Session 230 
    start on node
     10.684 user pcguest for service ccd
    Jan 21 09:53:54 localhost: 613 PCSAFS130: Starting server with 10.759
    and netbio
    s name PC759
    Jan 21 09:53:54 localhost: 613 PCSAFS130: Connect 527 Session 231 
    start on node
     10.759 user pcguest for service ccm
    Jan 21 09:53:55 localhost: 613 PCSAFS130: Connect 528 Session 231 
    start on node
     10.759 user pcguest for service ccd
    Jan 21 09:53:57 localhost: 619 PCSAFS130: Starting server with
    172.18.4.140 and 
    netbios name PC308
    Jan 21 09:53:57 localhost: 619 PCSAFS130: Connect 529 Session 232 
    start on node
     172.18.4.140 user pcguest for service ccd
    Jan 21 09:54:06 localhost: 580 PCSAFS130: Client 10.818 user pcguest
    stopped con
    nection tid 454
    Jan 21 09:54:06 localhost: 580 PCSAFS130: Client 10.818 user pcguest
    stopped con
    nection tid 455
    Jan 21 09:54:06 localhost: 580 PCSAFS130: Node 10.818 connection closed
    Jan 21 09:54:34 localhost: 634 PCSAFS130: Starting server with 10.740
    and netbio
    s name PC740
    Jan 21 09:54:34 localhost: 634 PCSAFS130: Connect 530 Session 233 
    start on node
     10.740 user pcguest for service ccd
    Jan 21 09:54:36 localhost: 318 PCSAFS130: Client 172.18.4.82 user
    pcguest stoppe
    d connection tid 384
    Jan 21 09:54:44 localhost: 480 PCSAFS130: Connect 531 Session 172 
    start on node
     172.18.4.115 user pcguest for service wp51
    Jan 21 09:55:09 localhost: 268 PCSAFS130: Client 172.18.4.59 user
    pcguest stoppe
    d connection tid 54
    Jan 21 09:55:09 localhost: 268 PCSAFS130: Client 172.18.4.59 user
    pcguest stoppe
    d connection tid 34
    Jan 21 09:55:09 localhost: 268 PCSAFS130: Client 172.18.4.59 user
    pcguest stoppe
    d connection tid 35
    Jan 21 09:55:09 localhost: 268 PCSAFS130: Node 172.18.4.59 connection
    closed
    Jan 21 09:55:10 localhost: 647 PCSAFS130: Starting server with
    172.18.4.152 and 
    netbios name PC818
    Jan 21 09:55:10 localhost: 647 PCSAFS130: Connect 532 Session 234 
    start on node
     172.18.4.152 user pcguest for service ccm
    Jan 21 09:55:10 localhost: 647 PCSAFS130: Connect 533 Session 234 
    start on node
     172.18.4.152 user pcguest for service ccd
    Jan 21 09:55:54 localhost: 586 PCSAFS130: Connect 534 Session 209 
    start on node
     172.18.4.124 user pcguest for service win_excel
    Jan 21 09:55:56 localhost: 610 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 521
    Jan 21 09:55:56 localhost: 610 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 522
    Jan 21 09:55:56 localhost: 610 PCSAFS130: Client 172.18.4.5 user mikota
    stopped 
    connection tid 523
    Jan 21 09:55:56 localhost: 610 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 524
    Jan 21 09:55:56 localhost: 610 PCSAFS130: Node 172.18.4.5 connection
    closed
    Jan 21 09:55:59 localhost: 679 PCSAFS130: Starting server with
    172.18.4.132 and 
    netbios name PC823
    Jan 21 09:55:59 localhost: 679 PCSAFS130: Connect 535 Session 235 
    start on node
     172.18.4.132 user pcguest for service ccm
    Jan 21 09:55:59 localhost: 679 PCSAFS130: Connect 536 Session 235 
    start on node
     172.18.4.132 user pcguest for service ccd
    Jan 21 09:56:12 localhost: 264 PCSAFS130: Connect 537 Session 16  start
    on node 
    172.18.4.69 user pcguest for service win_word
    Jan 21 09:56:26 localhost: 689 PCSAFS130: Starting server with
    172.18.4.5 and ne
    tbios name MIKOTA
    Jan 21 09:56:26 localhost: 689 PCSAFS130: Connect 538 Session 236 
    start on node
     172.18.4.5 user pcguest for service ccm
    Jan 21 09:56:26 localhost: 689 PCSAFS130: Connect 539 Session 236 
    start on node
     172.18.4.5 user pcguest for service ccd
    Jan 21 09:56:26 localhost: 689 PCSAFS130: Connect 540 Session 236 
    start on node
     172.18.4.5 user mikota for service isw
    Jan 21 09:56:27 localhost: 689 PCSAFS130: Connect 541 Session 236 
    start on node
     172.18.4.5 user pcguest for service winbatch
    Jan 21 09:56:41 localhost: 576 PCSAFS130: Node 10.101 connection closed
    Jan 21 09:56:43 localhost: 490 PCSAFS130: Node 10.272 connection closed
    Jan 21 09:56:44 localhost: 634 PCSAFS130: Node 10.740 connection closed
    Jan 21 09:56:45 localhost: 712 PCSAFS130: Starting server with
    172.18.4.132 and 
    netbios name PC823
    Jan 21 09:56:47 localhost: 713 PCSAFS130: Starting server with
    172.18.4.108 and 
    netbios name HIGBEE
    Jan 21 09:56:47 localhost: 713 PCSAFS130: Connect 542 Session 238 
    start on node
     172.18.4.108 user pcguest for service ccd
    Jan 21 09:56:49 localhost: 714 PCSAFS130: Starting server with
    172.18.4.77 and n
    etbios name PC305
    Jan 21 09:56:49 localhost: 714 PCSAFS130: Connect 543 Session 239 
    start on node
     172.18.4.77 user pcguest for service ccd
    Jan 21 09:57:24 localhost: 609 PCSAFS130: Node 172.18.4.77 connection
    closed
    Jan 21 09:57:26 localhost: 679 PCSAFS130: Node 172.18.4.132 connection
    closed
    Jan 21 09:57:27 localhost: 603 PCSAFS130: Connect 544 Session 222 
    start on node
     10.747 user pcguest for service win_word
    Jan 21 09:57:32 localhost: 409 PCSAFS130: Client 172.18.4.86 user
    pcguest stoppe
    d connection tid 439
    Jan 21 09:57:46 localhost: 374 PCSAFS130: Client 172.18.4.75 user
    pcguest stoppe
    d connection tid 480
    Jan 21 09:57:53 localhost: 479 PCSAFS130: Node 172.18.4.108 connection
    closed
    Jan 21 09:58:00 localhost: 712 PCSAFS130: Node 172.18.4.132 connection
    closed
    Jan 21 09:58:18 localhost: 715 PCSAFS130: Starting server with 10.272
    and netbio
    s name PC812
    Jan 21 09:58:18 localhost: 715 PCSAFS130: Connect 545 Session 240 
    start on node
     10.272 user pcguest for service ccd
    Jan 21 09:58:40 localhost: 429 PCSAFS130: Connect 546 Session 156 
    start on node
     172.18.4.32 user pcguest for service win_word
    Jan 21 09:59:02 localhost: 689 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 538
    Jan 21 09:59:02 localhost: 689 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 539
    Jan 21 09:59:02 localhost: 689 PCSAFS130: Client 172.18.4.5 user mikota
    stopped 
    connection tid 540
    Jan 21 09:59:03 localhost: 689 PCSAFS130: Client 172.18.4.5 user
    pcguest stopped
     connection tid 541
    Jan 21 09:59:03 localhost: 689 PCSAFS130: Node 172.18.4.5 connection
    closed
    Jan 21 09:59:13 localhost: 317 PCSAFS130: Client 172.18.4.63 user
    pcguest stoppe
    d connection tid 515
    Jan 21 09:59:49 localhost: 495 PCSAFS130: Client 172.18.4.138 user
    pcguest stopp
    ed connection tid 498
    Jan 21 09:59:49 localhost: 429 PCSAFS130: Client 172.18.4.32 user
    pcguest stoppe
    d connection tid 546
    Jan 21 10:00:03 localhost: 721 PCSAFS130: Starting server with
    172.18.4.132 and 
    netbios name PC823
    Jan 21 10:00:03 localhost: 721 PCSAFS130: Connect 547 Session 241 
    start on node
     172.18.4.132 user pcguest for service ccm
    Jan 21 10:00:03 localhost: 721 PCSAFS130: Connect 548 Session 241 
    start on node
     172.18.4.132 user pcguest for service ccd
    Jan 21 10:00:41 localhost: 722 PCSAFS130: Starting server with 10.102
    and netbio
    s name PC102
    Jan 21 10:00:41 localhost: 722 PCSAFS130: Connect 549 Session 242 
    start on node
     10.102 user pcguest for service netc_data
    Jan 21 10:00:43 localhost: 722 PCSAFS130: Client 10.102 user pcguest
    stopped con
    nection tid 549
    Jan 21 10:00:43 localhost: 722 PCSAFS130: Node 10.102 connection closed
    Jan 21 10:00:47 localhost: 723 PCSAFS130: Starting server with
    pc8056.trimet.or 
    and netbios name PC8056
    Jan 21 10:00:47 localhost: 723 PCSAFS130: Connect 550 Session 243 
    start on node
     pc8056.trimet.or user thoren for service isw
    Jan 21 10:00:48 localhost: 724 PCSAFS130: Starting server with 10.102
    and netbio
    s name PC102
    Jan 21 10:00:48 localhost: 724 PCSAFS130: Connect 551 Session 244 
    start on node
     10.102 user pcguest for service ccd
    Jan 21 10:01:47 localhost: 725 PCSAFS130: Starting server with 10.101
    and netbio
    s name PC101
    Jan 21 10:01:47 localhost: 725 PCSAFS130: Connect 552 Session 245 
    start on node
     10.101 user pcguest for service ccd
    Jan 21 10:02:01 localhost: 726 PCSAFS130: Starting server with
    172.18.4.143 and 
    netbios name PC773
    Jan 21 10:02:01 localhost: 726 PCSAFS130: Connect 553 Session 246 
    start on node
     172.18.4.143 user pcguest for service ccm
    Jan 21 10:02:01 localhost: 726 PCSAFS130: Connect 554 Session 246 
    start on node
     172.18.4.143 user pcguest for service ccd
    Jan 21 10:02:20 localhost: 727 PCSAFS130: Starting server with
    172.18.4.5 and ne
    tbios name MIKOTA
    Jan 21 10:02:20 localhost: 727 PCSAFS130: Connect 555 Session 247 
    start on node
     172.18.4.5 user pcguest for service ccm
    Jan 21 10:02:20 localhost: 727 PCSAFS130: Connect 556 Session 247 
    start on node
     172.18.4.5 user pcguest for service ccd
    Jan 21 10:02:20 localhost: 727 PCSAFS130: Connect 557 Session 247 
    start on node
     172.18.4.5 user mikota for service isw
    Jan 21 10:02:20 localhost: 727 PCSAFS130: Connect 558 Session 247 
    start on node
     172.18.4.5 user pcguest for service winbatch
    Jan 21 10:03:33 localhost: 374 PCSAFS130: Connect 559 Session 108 
    start on node
     172.18.4.75 user pcguest for service wp51
    Jan 21 10:06:11 localhost: 603 PCSAFS130: Client 10.747 user pcguest
    stopped con
    nection tid 544
    Jan 21 10:06:45 localhost: 728 PCSAFS130: Starting server with
    172.18.4.83 and n
    etbios name PC326
    Jan 21 10:06:45 localhost: 728 PCSAFS130: Connect 560 Session 248 
    start on node
     172.18.4.83 user pcguest for service ccm
    Jan 21 10:06:45 localhost: 728 PCSAFS130: Connect 561 Session 248 
    start on node
     172.18.4.83 user pcguest for service ccd
    Jan 21 10:08:03 localhost: 318 PCSAFS130: Connect 562 Session 66  start
    on node 
    172.18.4.82 user pcguest for service win_word
    Jan 21 10:08:29 localhost: 729 PCSAFS130: Starting server with 10.729
    and netbio
    s name PC729
    Jan 21 10:08:29 localhost: 729 PCSAFS130: Connect 563 Session 249 
    start on node
     10.729 user pcguest for service ccm
    Jan 21 10:08:30 localhost: 729 PCSAFS130: Connect 564 Session 249 
    start on node
     10.729 user pcguest for service ccd
    Jan 21 10:09:07 localhost: 320 PCSAFS130: Connect 565 Session 68  start
    on node 
    172.18.4.39 user pcguest for service wp51
    Jan 21 10:11:37 localhost: 732 PCSAFS130: Starting server with 10.650
    and netbio
    s name PC650
    Jan 21 10:11:37 localhost: 732 PCSAFS130: Connect 566 Session 250 
    start on node
     10.650 user pcguest for service ccd
    Jan 21 10:12:39 localhost: 733 PCSAFS130: Starting server with 10.273
    and netbio
    s name PC273
    Jan 21 10:12:39 localhost: 733 PCSAFS130: Connect 567 Session 251 
    start on node
     10.273 user pcguest for service ccm
    Jan 21 10:12:39 localhost: 733 PCSAFS130: Connect 568 Session 251 
    start on node
     10.273 user pcguest for service ccd
    Jan 21 10:12:54 localhost: 735 PCSAFS130: Starting server with
    172.18.4.64 and n
    etbios name PC790
    Jan 21 10:12:54 localhost: 735 PCSAFS130: Connect 569 Session 252 
    start on node
     172.18.4.64 user pcguest for service ccm
    Jan 21 10:12:54 localhost: 735 PCSAFS130: Connect 570 Session 252 
    start on node
     172.18.4.64 user pcguest for service ccd
    Jan 21 10:13:01 localhost: 736 PCSAFS130: Starting server with 10.673
    and netbio
    s name PC673
    Jan 21 10:13:01 localhost: 736 PCSAFS130: Connect 571 Session 253 
    start on node
     10.673 user pcguest for service ccm
    Jan 21 10:13:02 localhost: 736 PCSAFS130: Connect 572 Session 253 
    start on node
     10.673 user pcguest for service ccd
    Jan 21 10:13:28 localhost: 352 PCSAFS130: Client 172.18.4.158 user
    pcguest stopp
    ed connection tid 188
    Jan 21 10:13:28 localhost: 352 PCSAFS130: Connect 573 Session 87  start
    on node 
    172.18.4.158 user pcguest for service wp51
    Jan 21 10:13:55 localhost: 240 PCSAFS130: Client 10.639 user pcguest
    stopped con
    nection tid 457
    Jan 21 10:14:05 localhost: 352 PCSAFS130: Client 172.18.4.158 user
    pcguest stopp
    ed connection tid 573
    Jan 21 10:14:40 localhost: 352 PCSAFS130: Connect 574 Session 87  start
    on node 
    172.18.4.158 user pcguest for service win_word
    Jan 21 10:15:58 localhost: 352 PCSAFS130: Connect 575 Session 87  start
    on node 
    172.18.4.158 user pcguest for service wp51
    Jan 21 10:16:16 localhost: 273 PCSAFS130: Connect 576 Session 25  start
    on node 
    172.18.4.41 user pcguest for service ccm
    Jan 21 10:16:41 localhost: 265 PCSAFS130: Connect 577 Session 17  start
    on node 
    172.18.4.10 user pcguest for service win_excel
    Jan 21 10:16:56 localhost: 585 PCSAFS130: Connect 578 Session 208 
    start on node
     172.18.4.65 user pcguest for service win_proj
    Jan 21 10:17:08 localhost: 733 PCSAFS130: Client 10.273 user pcguest
    stopped con
    nection tid 567
    Jan 21 10:17:09 localhost: 733 PCSAFS130: Client 10.273 user pcguest
    stopped con
    nection tid 568
    Jan 21 10:17:09 localhost: 733 PCSAFS130: Node 10.273 connection closed
    Jan 21 10:17:19 localhost: 715 PCSAFS130: Connect 579 Session 240 
    start on node
     10.272 user pcguest for service wp51
    Jan 21 10:17:25 localhost: 250 PCSAFS130: Connect 580 Session 13  start
    on node 
    172.18.4.79 user pcguest for service win_word
    Jan 21 10:17:38 localhost: 715 PCSAFS130: Connect 581 Session 240 
    start on node
     10.272 user pcguest for service ccm
    Jan 21 10:17:40 localhost: 715 PCSAFS130: Client 10.272 user pcguest
    stopped con
    nection tid 545
    Jan 21 10:18:34 localhost: 367 PCSAFS130: Node 10.732 connection closed
    Jan 21 10:18:42 localhost: 250 PCSAFS130: Client 172.18.4.79 user
    pcguest stoppe
    d connection tid 580
    Jan 21 10:18:52 localhost: 320 PCSAFS130: Client 172.18.4.39 user
    pcguest stoppe
    d connection tid 271
    Jan 21 10:19:35 localhost: 251 PCSAFS130: Node 10.676 connection closed
    Jan 21 10:19:48 localhost: 250 PCSAFS130: Connect 582 Session 13  start
    on node 
    172.18.4.79 user pcguest for service win_word
    Jan 21 10:20:05 localhost: 326 telnetd: Connection closed from host
    pc8056.trime
    t.org
    Jan 21 10:20:40 localhost: 740 PCSAFS130: Starting server with
    172.18.4.0 and ne
    tbios name PC793
    Jan 21 10:20:40 localhost: 740 PCSAFS130: Connect 583 Session 254 
    start on node
     172.18.4.0 user pcguest for service ccm
    Jan 21 10:20:40 localhost: 740 PCSAFS130: Connect 584 Session 254 
    start on node
     172.18.4.0 user pcguest for service ccd
    Jan 21 10:20:41 localhost: 611 PCSAFS130: Connect 585 Session 230 
    start on node
     10.684 user pcguest for service win_word
    Jan 21 10:20:48 localhost: 741 PCSAFS130: Starting server with 10.732
    and netbio
    s name PC732
    Jan 21 10:20:48 localhost: 741 PCSAFS130: Connect 586 Session 255 
    start on node
     10.732 user pcguest for service ccm
    Jan 21 10:20:49 localhost: 741 PCSAFS130: Connect 587 Session 255 
    start on node
     10.732 user pcguest for service ccd
    Jan 21 10:20:50 localhost: 534 PCSAFS130: Client 172.18.4.130 user
    pcguest stopp
    ed connection tid 450
    Jan 21 10:20:58 localhost: 534 PCSAFS130: Connect 588 Session 187 
    start on node
     172.18.4.130 user pcguest for service pdox40
    Jan 21 10:20:59 localhost: 534 PCSAFS130: Connect 589 Session 187 
    start on node
     172.18.4.130 user pcguest for service pact
    Jan 21 10:21:03 localhost: 742 PCSAFS130: Starting server with
    172.18.4.59 and n
    etbios name PC816
    Jan 21 10:21:03 localhost: 742 PCSAFS130: Connect 590 Session 256 
    start on node
     172.18.4.59 user pcguest for service ccm
    Jan 21 10:21:03 localhost: 742 PCSAFS130: Connect 591 Session 256 
    start on node
     172.18.4.59 user pcguest for service ccd
    Jan 21 10:21:39 localhost: 723 PCSAFS130: NETBIOS packet error,
    expecting SESSIO
    N_MESSAGE
    Jan 21 10:21:39 localhost: 723 PCSAFS130: Node pc8056.trimet.or
    connection close
    d
    Jan 21 10:21:49 localhost: 743 PCSAFS130: Starting server with 10.520
    and netbio
    s name PC520
    Jan 21 10:21:49 localhost: 743 PCSAFS130: Connect 592 Session 257 
    start on node
     10.520 user pcguest for service ccm
    Jan 21 10:21:50 localhost: 743 PCSAFS130: Connect 593 Session 257 
    start on node
     10.520 user pcguest for service ccd
    Jan 21 10:22:01 localhost: 474 PCSAFS130: Connect 594 Session 167 
    start on node
     172.18.4.50 user pcguest for service win_word
    Jan 21 10:22:02 localhost: 744 PCSAFS130: Starting server with
    172.18.4.61 and n
    etbios name PC815
    Jan 21 10:22:02 localhost: 744 PCSAFS130: Connect 595 Session 258 
    start on node
     172.18.4.61 user pcguest for service ccm
    Jan 21 10:22:02 localhost: 744 PCSAFS130: Connect 596 Session 258 
    start on node
     172.18.4.61 user pcguest for service ccd
    Jan 21 10:22:05 localhost: 264 PCSAFS130: Client 172.18.4.69 user
    pcguest stoppe
    d connection tid 537
    Jan 21 10:22:09 localhost: 409 PCSAFS130: Connect 597 Session 139 
    start on node
     172.18.4.86 user pcguest for service win_wp52
    Jan 21 10:22:26 localhost: 745 PCSAFS130: Starting server with
    172.18.4.97 and n
    etbios name PC681
    Jan 21 10:22:26 localhost: 745 PCSAFS130: Connect 598 Session 259 
    start on node
     172.18.4.97 user pcguest for service ccm
    Jan 21 10:22:26 localhost: 745 PCSAFS130: Connect 599 Session 259 
    start on node
     172.18.4.97 user pcguest for service ccd
    Jan 21 10:22:34 localhost: 373 PCSAFS130: Client 172.18.4.93 user
    pcguest stoppe
    d connection tid 409
    Jan 21 10:23:11 localhost: 611 PCSAFS130: Client 10.684 user pcguest
    stopped con
    nection tid 585
    Jan 21 10:23:54 localhost: 278 PCSAFS130: Connect 600 Session 30  start
    on node 
    172.18.4.112 user pcguest for service win_wp61
    Jan 21 10:23:54 localhost: 473 PCSAFS130: Client 172.18.4.1 user
    pcguest stopped
     connection tid 363
    Jan 21 10:23:54 localhost: 473 PCSAFS130: Client 172.18.4.1 user
    pcguest stopped
     connection tid 364
    Jan 21 10:23:54 localhost: 473 PCSAFS130: Node 172.18.4.1 connection
    closed
    Jan 21 10:24:34 localhost: 377 PCSAFS130: Connect 601 Session 111 
    start on node
     172.18.4.36 user pcguest for service win_excel
    Jan 21 10:24:40 localhost: 745 PCSAFS130: Connect 602 Session 259 
    start on node
     172.18.4.97 user pcguest for service win_wp52
    Jan 21 10:25:06 localhost: 744 PCSAFS130: Client 172.18.4.61 user
    pcguest stoppe
    d connection tid 595
    Jan 21 10:25:06 localhost: 744 PCSAFS130: Client 172.18.4.61 user
    pcguest stoppe
    d connection tid 596
    Jan 21 10:25:06 localhost: 744 PCSAFS130: Node 172.18.4.61 connection
    closed
    Jan 21 10:25:34 localhost: 350 PCSAFS130: Connect 603 Session 85  start
    on node 
    10.348 user pcguest for service wp51
    Jan 21 10:25:55 localhost: 352 PCSAFS130: Client 172.18.4.158 user
    pcguest stopp
    ed connection tid 574
    Jan 21 10:26:12 localhost: 746 PCSAFS130: Starting server with
    172.18.4.110 and 
    netbios name PC704
    Jan 21 10:26:12 localhost: 746 PCSAFS130: Connect 604 Session 260 
    start on node
     172.18.4.110 user pcguest for service ccm
    Jan 21 10:26:12 localhost: 746 PCSAFS130: Connect 605 Session 260 
    start on node
     172.18.4.110 user pcguest for service ccd
    Jan 21 10:28:02 localhost: 280 PCSAFS130: Connect 606 Session 32  start
    on node 
    172.18.4.53 user pcguest for service win_word
    Jan 21 10:28:28 localhost: 747 PCSAFS130: Starting server with 10.671
    and netbio
    s name PC671
    Jan 21 10:28:28 localhost: 747 PCSAFS130: Connect 607 Session 261 
    start on node
     10.671 user pcguest for service ccm
    Jan 21 10:28:41 localhost: 747 PCSAFS130: Connect 608 Session 261 
    start on node
     10.671 user pcguest for service ccd
    Jan 21 10:28:43 localhost: 594 PCSAFS130: Client 172.18.4.120 user
    pcguest stopp
    ed connection tid 489
    Jan 21 10:28:44 localhost: 474 PCSAFS130: Client 172.18.4.50 user
    pcguest stoppe
    d connection tid 594
    Jan 21 10:28:47 localhost: 474 PCSAFS130: Connect 609 Session 167 
    start on node
     172.18.4.50 user pcguest for service win_word
    Jan 21 10:29:10 localhost: 474 PCSAFS130: Client 172.18.4.50 user
    pcguest stoppe
    d connection tid 609
    Jan 21 10:29:17 localhost: 474 PCSAFS130: Connect 610 Session 167 
    start on node
     172.18.4.50 user pcguest for service win_word
    Jan 21 10:29:17 localhost: 373 PCSAFS130: Connect 611 Session 107 
    start on node
     172.18.4.93 user pcguest for service wp51
    Jan 21 10:29:52 localhost: 352 PCSAFS130: Client 172.18.4.158 user
    pcguest stopp
    ed connection tid 575
    Jan 21 10:30:10 localhost: 751 PCSAFS130: Starting server with 10.717
    and netbio
    s name PC717
    Jan 21 10:30:10 localhost: 751 PCSAFS130: Connect 612 Session 262 
    start on node
     10.717 user pcguest for service ccd
    Jan 21 10:30:21 localhost: 751 PCSAFS130: Connect 613 Session 262 
    start on node
     10.717 user pcguest for service ccm
    Jan 21 10:30:21 localhost: 751 PCSAFS130: Client 10.717 user pcguest
    stopped con
    nection tid 612
    
    
    Jan 21 10:30:21 localhost: 751 PCSAFS130: Connect 614 Session 262 
    start on node
     10.717 user pcguest for service ccd
    Jan 21 10:30:49 localhost: 752 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en pipe signal at pc 431548
    Jan 21 10:30:49 localhost: 752 PCSAFS130: Node 192.168.12.100
    connection closed
    Jan 21 10:30:59 localhost: 753 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en pipe signal at pc 431548
    Jan 21 10:30:59 localhost: 753 PCSAFS130: Node 192.168.12.100
    connection closed
    Jan 21 10:31:09 localhost: 755 PCSAFS130: Node 192.168.12.100
    terminated by Brok
    en pipe signal at pc 431548
    Jan 21 10:31:09 localhost: 755 PCSAFS130: Node 192.168.12.100
    connection closed
    Jan 21 10:31:59 localhost: 249 PCSAFS130: Connect 615 Session 12  start
    on node 
    172.18.4.54 user pcguest for service ccm
    Jan 21 10:32:13 localhost: 249 PCSAFS130: Connect 616 Session 12  start
    on node 
    172.18.4.54 user pcguest for service ccd
    Jan 21 10:32:57 localhost: 758 PCSAFS130: Starting server with 10.295
    and netbio
    s name PC295
    Jan 21 10:32:57 localhost: 758 PCSAFS130: Connect 617 Session 266 
    start on node
     10.295 user pcguest for service ccd
    Jan 21 10:32:59 localhost: 481 PCSAFS130: Client 172.18.4.117 user
    pcguest stopp
    ed connection tid 388
    Jan 21 10:33:57 localhost: 742 PCSAFS130: Connect 618 Session 256 
    start on node
     172.18.4.59 user pcguest for service win_word
    Jan 21 10:34:36 localhost: 758 PCSAFS130: Connect 619 Session 266 
    start on node
     10.295 user pcguest for service ccm
    Jan 21 10:34:36 localhost: 758 PCSAFS130: Connect 620 Session 266 
    start on node
     10.295 user pcguest for service ccd
    Jan 21 10:35:02 localhost: 647 PCSAFS130: Client 172.18.4.152 user
    pcguest stopp
    ed connection tid 532
    Jan 21 10:35:02 localhost: 647 PCSAFS130: Client 172.18.4.152 user
    pcguest stopp
    ed connection tid 533
    Jan 21 10:35:02 localhost: 647 PCSAFS130: Node 172.18.4.152 connection
    closed
    Jan 21 10:35:45 localhost: 341 PCSAFS130: Connect 621 Session 79  start
    on node 
    172.18.4.100 user pcguest for service wp51
    Jan 21 10:36:05 localhost: 759 PCSAFS130: Starting server with 10.818
    and netbio
    s name PC818
    Jan 21 10:36:05 localhost: 759 PCSAFS130: Connect 622 Session 267 
    start on node
     10.818 user pcguest for service ccm
    Jan 21 10:36:05 localhost: 759 PCSAFS130: Connect 623 Session 267 
    start on node
     10.818 user pcguest for service ccd
    Jan 21 10:36:50 localhost: 269 PCSAFS130: Client 172.18.4.45 user
    pcguest stoppe
    d connection tid 36
    Jan 21 10:37:19 localhost: 352 PCSAFS130: Connect 624 Session 87  start
    on node 
    172.18.4.158 user pcguest for service wp51
    Jan 21 10:38:20 localhost: 713 PCSAFS130: Connect 625 Session 238 
    start on node
     172.18.4.108 user pcguest for service ccm
    Jan 21 10:38:25 localhost: 760 PCSAFS130: Starting server with
    172.18.4.145 and 
    netbios name PC803
    Jan 21 10:38:25 localhost: 760 PCSAFS130: Connect 626 Session 268 
    start on node
     172.18.4.145 user pcguest for service ccm
    Jan 21 10:38:25 localhost: 760 PCSAFS130: Connect 627 Session 268 
    start on node
     172.18.4.145 user pcguest for service ccd
    Jan 21 10:38:58 localhost: 352 PCSAFS130: Client 172.18.4.158 user
    pcguest stopp
    ed connection tid 624
    
T.RTitleUserPersonal
Name
DateLines
1295.1Still looking for advice.VMSNET::G_OEHMSWill the wonders never seize the day?Mon Feb 10 1997 20:0612
    Hello:
    
    	Talked to the customer again, and he says things are working.  He's
    mainly concerned about whether he needs to worry about a recurrence of
    the broken pipe phenomenon that crashed his server.
    
    	We discussed that it may have been an odd "one-off" type of
    cascading error but he would like more reassurance than I can give. 
    Can anyone advise on this?
    
    	Thanks,
    	glenn