[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

1817.0. "Help needed: NT3.5 + SNA 2.1 + FDDI NIC" by VAXRIO::SERGIO () Mon Oct 02 1995 10:53

	Hi,

	I have a customer who has a problem with NT 3.5 Build 807, SNA SERVER
	2.1 and DEC FDDI PCI NIC (DEFPA-UA). When he uses DEC NIC, the client
        machines loses sessions with server. But if he uses 3COM NIC (Ethernet)
	everything runs ok!
	The machine is a DECPC XL 560.
	What to do?
	Anybody knows anything about that?

	Thanks in advance.

	Sergio Valente

        VMSMAIL::SERGIO
	A1::SERGIO.VALENTE@DJO
T.RTitleUserPersonal
Name		DateLines
1817.1NETCAD::STEFANIMachines to humanizeMon Oct 02 1995 12:5528
    >>	I have a customer who has a problem with NT 3.5 Build 807, SNA SERVER
    >>	2.1 and DEC FDDI PCI NIC (DEFPA-UA). When he uses DEC NIC, the client
    >>    machines loses sessions with server. But if he uses 3COM NIC (Ethernet)
    >>	everything runs ok!
    
    Sergio,
    
    We'll need a little more information than this.
    
    If the customer has both FDDI and Ethernet drivers loaded and
    installed, there may be protocol binding issues.  I'd simplify the
    configuration by removing all network device drivers except for the
    DEFPA.  Also, see if the clients can connect over any protocol stack
    (NetBEUI, TCP/IP, or IPX/SPX).
    
    As for SNA, I don't know if Microsoft supports that protocol over FDDI
    under NT, maybe they do, I just don't know.
    
    You may also want to do the following:
    
    	1. Install the latest DEFPA driver (v1.57) off the latest DEFPA
    	   kit (KALI::PCDRIVERS:[DEFPA.INTERIM]FPKIT242.ZIP).
    	2. Install Service Pack 2 for Windows NT 3.5.
    
    If possible, you may want to upgrade to Windows NT 3.51 since that has
    a lot of fixes.
    
       - Larry
1817.2More InformationVAXRIO::63043::sergioCSC - PC Hardware SupportThu Oct 05 1995 16:2315
   Larry

   He's using both NICs FDDI and Ethernet. He's using TCP/IP and NETBEUI. 
   protocols.

   The Service Pack 2 was installed a few days ago after a lot of tries, 
   and I copied the new drivers for both FDDI (SERVER) and ETHERNET 
   controllers (client machines) and gived it to him. I'm waiting for 
   response.

   Any more idea?

Tks

 - Sergio
1817.3NETCAD::STEFANIMachines to humanizeThu Oct 05 1995 17:4018
   >>He's using both NICs FDDI and Ethernet. He's using TCP/IP and NETBEUI. 
   >>protocols.
 
    Ask the customer to make sure the following is setup properly:
    
    	1. Windows NT 3.5 with Service Pack 2 installed.
    	2. DEFPA v1.57 driver off latest DEFPA kit.
    	3. Only one (1) adapter (DEC FDDIcontroller/PCI) appears under
           "Installed Adapter Cards" in the Control Panel\Network Settings
           dialog box. 
        4. All bindings are correct for TCP/IP and NetBEUI (use Bindings
           option).
    	5. Once driver is loaded, verify that DEFPA has a solid green
           LED.  If it's blinking green, then either the FDDI cable
           is bad, no cable is connected, or the connection on the
           other end is bad.
    
    - Larry