Conference noted::atm

What version of the driver are you using?

doug

    The version of the atm driver is 1.10 for intel
    
    
    thanks murat
    

Use a newer version of the driver.  www.networks.digital.com
The newer ones are "field test" but are much better versions.

doug

    I installed ATM driver 2.10 (field test) on NT by means of ADD ADAPTER
    three times in order to connect three different LANE.
    I gave three LECS names and IP addresses.
    I can ping itself. (three adapters' IP), but I can ping nowhere in the
    network.
    Is there a hint in installation of NT ATM driver for multiple LANE's
    

Do each of the LANE clients belong to a different emulated LAN?
Are each in different a different subnet?

doug

    Each lane clients belong to a different emulated lan.Each lane clients
    have different IP's but they have same subnet masks
    
    
    In gigaswitch there are three emulated lans.
    Lan 1  (10.0.1.0 Network)
    Lan 2  (10.0.2.0 Network)
    Lan 3  (10.0.3.0 Network)
    
    
     NT sever has a card ATMworks 350. I configured this card by means of
    ADD ADAPTER three times. I have one ATMWORKS 350 but I installed three
    drivers with different IP's .
    1st driver has 10.0.1.25 address
    2nd driver has 10.0.2.25 address
    3rd driver has 10.0.3.25 address
    I can only ping 10.0.1.25,10.0.2.25 and 10.0.3.25
    
    
    (Note: I installed only one driver. Then I can connect first LANE)   
    
               

I guess I'm a little confused; are you trying to ping from any of the  
ELANs on the ATMworks 350 in the NT machine to some other ELAN in the 
same machine?  If so, you have to configure it as a router.  In fact, 
to ping off of any subnet to a different subnet, you need to 
configure a router somewhere in the network (the NT machine is a 
possibility).  Are you saying that you can ping between two machines 
in a subnet?

doug

Run the Registry Editor: (from MS-DOS prompt, type regedt32)

Go to HKEY_LOCAL_MACHINE

Click on SYSTEM, then CurrentControlSet, then Service, then TCPIP, 
then parameters.

If there is an entry for IPEnableRouter, double click on it, then
change the value 0 to 1, and then exit and reboot.

If there is no entry, select EDIT, and select ADD VALUE.  IN the
'value name' field, type IPEnableRouter, and then select data type
to be REG_DWORD.  CLick OK, and type 1 into the string editor dialog
box.

This turns on internal IP routing, so that any IP enabled card
connected to this NT machine can route traffic to any other IP 
enabled
card in this machine.

To setup other static routes (to other endstations), you have to use
ROUTE.EXE command line utility.

For example, if you have a configuration with 
        
                                   10.1.1.4           16.207.241.55
                GIGAswitch/ATM  -------- (ATM) NT Box (Ethernet)---
                    |       |
       Unix EndStation      |
       10.1.1.5             |
                          10.1.1.3
                          (ATM)
                          DS 400
                          (Ethernet) --------
                          10.2.1.1

Using the Registry Editor, and setting IP routing enabled, allows
connectivity from the Ethernet side of the NT box to the ATM 
Interface
to the Unix Endstation, i.e. routing from 16.207.241 to 10.1.1 
domain.

To get from Ethernet on the NT box, to Ethernet on the DS 400, you 
need
to set a route on both the NT box, and the DS 400.

Setting Route on the NT box:
----------------------------

route add 16.207.241.0 10.1.1.3

Setting Route on the DS 400:
----------------------------

Refer to the DS 400 user guide.

    Re .6: it is assumed that your subnet masks are set to 255.255.255.0 Is
    that correct?
    
    Pedro