Conference 7.286::fddi

1296.0. "any ideas welcome: lat,fddi,decbridge,ethernet??" by TOHOPE::WSA003::CHURCHE_J (Nothing endures but change) Tue Mar 29 1994 09:22

    
        <<< NOTED::DISK$NOTES9:[NOTES$LIBRARY_9OF4]PWDOSWINV5.NOTE;2 >>>
                 -< PATHWORKS for DOS and Windows Version 5.x >-
================================================================================
Note 567.0       LAT, FDDI, DECbridge 650, PW V4.1 client...NOT       No replies
TOHOPE::WSA003::CHURCHE_J "Nothing endures but chan" 21 lines  28-MAR-1994 16:40
--------------------------------------------------------------------------------
                                                                 
    This fellow that I am talking to has LAT V4.1.17x with a DE200 card
    doing a remote boot from a V4.x server.  It is trying to talk to a
    server on an FDDI network through a DECbridge 650.  The specific 
    problem that he is seeing is this:  he can't do a LAT connect from the
    PC client to the FDDI server (a VAX 7xxx), unless he defines the server
    node with its hardware address.  If we define the server using the
    usual LATCP add area.node name name, it won't work and comes back with
    service not known.  DECnet is started on the FDDI controller.
    
    Does anyone know why this isn't working like we would expect?  Why
    can't the PW V4.1 pc client see the FDDI server via the AA... address?
    
    (Other VMS based system on the same ethernet segment are able to set
    host/lat to this FDDI node just fine.)
    
    Thanks,
    
    jc
    pw/alf
    
    

    
    Found the answer in NOTED::LAT, #4605.
    
    jc