Conference jamin::pathworks32

335.0. "WNT V4 Alpha and PWV5 Integration" by GRANPA::BARABIA () Fri Jun 06 1997 09:10

              <<< NOTED::NOTES$9:[NOTES$LIBRARY]PWV50IFT.NOTE;1 >>>
        -< Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server >-
================================================================================
Note 4319.0             WNT V4 Alpha and PWV5 Integration             No replies
GRANPA::BARABIA                                      44 lines   6-JUN-1997 09:03
--------------------------------------------------------------------------------
    We recently have brought 2 Windows NT V4.0 Alpha 2100's into our
    existing PATHWORKS V5.0E ECO1 Domain as te PDC and BDC for our Domain
    FDACDER.
    
    The Windows NT Servers have also been updated with Service Pak 3.
    PATHWORKS32 V7.0 (DECnet) only is all we are using PATHWORKS wise.
    
    As best we can tell, both Alpha's are up to rev firmware wise. We have
    an Alpha 2100 4/275 with a DEC435 PCI Ethernet controller and JBOD SCSI
    disk configuration. Our other 2100 is a 5/250. That one has a raid disk
    configuration as well as a PCI FDDI adapter (DEFPA). The 4/275 has
    512Meg of meomory and is configured as the PDC. The 4/275 has 128Meg
    and is a BDC.
    
    The integration of the NT Servers to our PATHWORKS Domain has gone
    well. We have a cluster of 3 Alpha systems running PATHWORKS V5.0E ECO1
    as well as 4 other V5.0E systems acting as BDC's as well. Our Domain
    seems fine, the NT serves as well as PATHWORKS servers are validating
    users logons and the SAM/UAS is replicating to the BDC's. There are no
    shared resources on the NT servers at this time. Their only function is
    users logon validation. We have over 2000 users accounts though. Most
    of our clients are Windows 95 clients, though we still have about
    300-400 DOS/Windows PW V5 clients. DECnet is still the primary protocol
    for all clients though the Win95 clients have NetBeui and TCP/IP
    enabled along with DECnet.
    
    We have been running this configuration for about a week now. We have
    been experiencing regular hands of the NT servers for no apparent
    reason. No dump file is created, though we are set up to write one and
    no events show up in the event log to give us a clue. We've called
    Microsoft and they've been of little help. I've also logged calls with
    our CSC and they are stumped as well, only suggestion I keep getting is
    to remove PATHWORKS from the NT servers which is not an option since we
    need that for our PW V5 clients to get validated since DECnet is the
    only protocol they run.
    
    Does anyone have Windows NT Alpha Server running with PATHWORKS32
    integrated with PATHWORKS? Or has anyone experienced something like
    this? We really are clueless at this point so any input would be
    greatly appreciated.
    
    Thanks,
    
    Barry A

Yes we have... the issue is probably the same one that has been fixed for
some time, and is in V7.0a.  There was a problem with random system hangs
directly releated to idle links and such.

V7.0a will be submitted to SSB on Jun 11th, so... if they can wait, and
they are on automatic update... the customer will receive v7.0a.

If not, file an IPMT case... also, have a harsh word or two with the
Digital folks suggesting REMOVING PATHWORKS 32 as a "workaround"....

Jeff

    Jeff,
    
    Thanks for the response, and we've already had the harsh words for the
    support folks. I think we will submit the IPMT. We just brought our NT
    servers online this week so we need to stablize our environment as soon
    as possible.
    
    We don't have a problem turning PATHWORKS32 off on our NT servers
    temporarily if it stablizes the servers. Most of our clients are Win95
    clients and have NetBeui and TCP/IP enabled as well as DECnet anbd we
    have those protocols enabled on the NT servers as well. Our issues is
    that we still have about 300 PWV5 clients that run DECnet only. Is it
    not possible that the NT servers could answer their requests for Logons
    and not be able to return a successful validation to the client if
    DECnet is not running on the Server or will the NT Server not respond
    at all to a DECnet only clients request for a NETLOGON?
    
    Thanks for any input.
    
    Barry A