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

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

1552.0. "FDDI - NT and SUN can't communicate..." by DECLNE::PEACOCK () Wed Jan 11 1995 17:08

    A customer in South America is having the following problem.  The
    support person is asking if there are any know problems with this
    configuration.  This is quite possibly a software issue with NT or SUN, 
    but I thought I would post his situation here to see if anyone has any 
    ideas or suggestions on where to begin.
    
    Thanks for any help or suggestions.
    
    Here is his situation:
    
    ---------------------------------------------------------------------------
    
    Some time ago our customer Clarin(the most important newspaper in our
    country)  requested us for a sollution to connect the following
    environment :
    
            - 4  Workstation SUN Sparc 10 with FDDI (1.0.SunLink
                 FDDI/S) controllers.
            - FDDI single ring network interconnects all systems.
            - SOLARIS 4.1.3_U1 operating system for Sparc 10.
            - TCP/IP transport.
    
    with a couple of PC AXP/150 with Ethernet controller running Windows NT
    V3.1. Our suggestion was the FDDI (DEFEA-AA) controllers for the PC AXP/150
    We sold the cards and now (during the instalation of the cards).  We
    are experiencing problems with the FDDI options DEFEA-AA installed in PC
    AXP/150 and using WINDOWS NT with TCP/IP as transport.
    
    Problem: SUN workstations can't communicate with DEC PC's through FDDI
    ring and DEC PC's can't communicate with SUN equipment. Customer
    uses PING command for looping among different nodes.
    
    Symptoms: 1) Communication via Ethernet works properly.
              2) Communication via FDDI works properly among SUN equipment.
              3) Communication via FDDI works properly among DEC equipment.
              4) Communication fails when Customer want to access DEC from
                 SUN or SUN from DEC. For example using PING.
              5) LED indicators in FDDI concentrator report that network is
                 OK at physical level.
    
    
    Could you check with Product Mgmt. if there is a known problem with
    this configuration ?
    ---------------------------------------------------------------------------
T.RTitleUserPersonal
Name		DateLines
1552.1NETCAD::STEFANILook Ma, I'm drinking my oatmeal!Wed Jan 11 1995 18:5511
    >>          3) Communication via FDDI works properly among DEC equipment.
    
    How are you determining that the DECpc AXP/150 is communicating
    properly amongst other DEC equipment?  Can you PING from the NT station
    to another NT station, but not to the Sun?  There could be something at
    the protocol level that is causing the incompatibility.  Is it possible
    to get an FDDI Sniffer trace of the ping going to/from the NT station?
    
    Larry Stefani
    FDDI Driver Development
1552.2Response from Argentina....DECLNE::PEACOCKFri Jan 13 1995 14:4635
    Larry, 
    
    Unfortunately, I am acting as the go-between here because the people in
    Argentina can't get to this notes conference.  If you have any more
    specific questions I can ask him, let me know and I will pass it on.
    
    Here is his response to your questions:
    
    
    -------------------------------------------------------------------------
    Hi Rick,
    As it's not easy for us to include answers in Notes, I hope you can
    do this for us. These are the answers requested by Larry.
    
    Thank you very much.
    Alex
    ****************************************************
    
    
    1) We determine that DECpc AXP/150 is communicating properly to/from
    other DEC stations, using PING and establishing a connection from one node
    to another.
    
    2) Unfortunately we haven't access to any Sniffer System to get a FDDI 
    trace.  We don't know whether we can use an auxiliary method to obtain
    the same information. For example a command or procedure available from
    TCP/IP or WINDOWS NT, such as TRACE is for DECNET.
    
    
      We thank in advance, all the information you can supply about it.
    
    
    ---------------- Labor Activity Information for this Work Unit
    ----------------
1552.3WagKEIKI::WHITEMIN(2�,FWIW)Fri Jan 13 1995 15:435
    
    	Is this an ARP problem?
      What are the broadcast addresses for the subnet both Digital and Sun?
    
       					Bill
1552.4Please list the "IP's" of all machinesCIVPR1::MARKISDepends on Your Perspective, Ofcourse ...Tue Feb 13 1996 11:4413
>      What are the broadcast addresses for the subnet both Digital and Sun?
Bill has a very important question in .3...

What are the IP addresses of the SUN's and of the DEC's ???  Also what are 
each System's Subnet Mask ????

It behaves as if you have 2 different AREA's defined and no Router, causing 
your Masks to filter each other out.

Please list the above IP information for all to analyse.


Chris					:)
1552.5NETCAD::STEFANII *CAN* drive 65!Tue Feb 13 1996 12:1612
    re: .4
    
    Chris,
    
    You may not have noticed that the original posting is a year old.  I
    assume that this problem is closed, or at the very least, the original
    customer has since upgraded to Windows NT 3.5 or 3.51.
    
    Thanks for your interest in helping.
    
       - Larry