ATMbook gets disconnected

[AlexTovar]

Hi all:

I have a ATMbook, when link between it and a Laptop is established, on the Sniffer's top bar I get a message of "Pod Connection Lost", after few seconds, connection is re-established, but normally it is lost, and I have to reboot my PC and ATMbook.

Firmware was updated to the Portable Sniffer I'm using ( 4.7 ), any suggestion will be appreciated.

Thanks to all !

 

[AlfSutherland]

Hi Alex, Check the following;
1. ATM book is assigned a static IP addess in the same subnet range as your LTMLT2 driver
2. Make sure the ATM book is set to 100 Mbps
3. Make sure your Ethernet card is set to 100 Mbps Half Duplex
4. Make sure the LTMLT2 driver is set to use the Ethernet card
Some other thing to be aware of;
Do not enter a value into the Gateway field of the ATMLT2 intermediate driver. The ATM Book and Host PC are directly connected and do not need the gateway address.
The Ethernet Adapter, the ATMLT2.sys and the ATM Book must use a unique IP address. The firmware GUI will not work unless the Ethernet adapter, ATMLT2 intermediate driver, and ATM Book all reside in the same IP Address range and use unique values.
When starting the Sniffer Pro and the ATM Book, insure the ATM Book is powered on for at least one minute before launching the Sniffer application. This insures the ATM Book completes an initialization process that occurs upon power-up.
When rebooting the Sniffer PC, as the application closes it issues a reset command to the ATM Book. Be aware of this condition if the ATM Book is "in line" with the monitored ATM network and not attached via a splitter. The reset will momentarily interrupt the communications line.
During start up, Sniffer Pro momentarily declares the connection to the ATM Book as down. Usually this message clears after completion of initialization sequence. Occasionally this message will remain in the title bar after the initialization sequence despite normal communications with the ATM Book. Although Sniffer will operate normally, it's recommended to close the application, wait for the ATM Book to complete its reboot process and launch Sniffer Pro again.
When switching from Emulation Mode (Traffic Generator) to Monitor mode, it is necessary to close the Sniffer Pro Application and allow the ATM Book to reboot to restore the monitor and capture functions

P.S. If you also use the SnifferBook Ultra, you can't use the SnifferBook Ultra if the ATMLT2 virtual adapter is installed, as this affects the BootP request.

I hope this helps. Alf (sniffer@axial.co.uk)

 

[AlexTovar]

Alf.

Thanx for your answer, I tried those settings and ATMbook looks fine, I haven't had the opportunity to test it in a live network, but it used to lose connection even without the ATM link !

Last month I test it on a live network and lost connection several times, but another technician put his Laptop infrared port "in line" with mine, and my laptop show "the damn blue screen" showing that "atmlt2 driver" had memory conflict !!! after that, my intermediate driver gone away and nothing was able to set up it again. Do you know how can I avoid this ? I have win2000.

Many thanks.

 

[svorick]

AlexTovar,

I have the same problem of the ATMbook getting disconnected while using OC12 modules. I had Sniffer ATM lab guys at my site to troubleshoot the problem, they discovered an orphanned process in the ATM code getting killed. This was in May and I still am waiting for a fix.