As with any timeout sort of error, the problem may be caused by a hardware or software misconfiguration on the end user's computer, or by a line related problem ie. router build, excess capacity occupation, etc. Basic troubleshooting will include:
1) Make sure that the modem driver is properly installed in device manager. The alcatel usb should appear directly under computer at the top, and under network adapters as an rfc 1483 device. Alcatel usb drivers should be located in the \installs\setup\alcatel\usb folder on the sbc express version 1.0.5 cd. Drivers are located in the x:\Drivers\Alcatel\usb folder on the 2.0 software. The 4060 should also appear in device manager as an rfc 1483 device. 4060 drivers must be downloaded from efficient.com. Make sure that the modem is using the rfc 1483 driver. Update driver should give you this option if an inappropriate driver has been loaded.
2)Make sure that the device appears in the network connections window as a local area connection, and that tcp/ip is bound to the device. Of course excess protocols such as ipx/spx, netbeui, internet connection sharing (ics), and virtual private networking (vpn). can cause connection problems. You may also try right clicking on the appropriate local area connection and selecting "repair".
3)Make sure that there is a modem diagnostic icon in the system tray showing proper status (should be green for alcatel usb).
4)Make sure that the end user has an appropriate router build, and attempt an end to end atm ping. In the case of an Ameritech customer that has not been converted, contact Ameritech provisioning for these tests.
5)Make sure that the modem has sync. If the customer is not an RT order, do a circuit manager port check. Make sure that there is not excessive downstream capacity occupation. (anything above 90% can cause connection problems, and inconsistant sync) Also, as with any timeout error, it is important to power cycle the modem for a full minute.
6)In the case of an alcatel usb, you may also try an alternate alcatel installation. In the case of an efficient networks 4060, you may try a clean install.
7) You may try forcing windows to use the correct network adapter for its connection by running the Network Setup Wizard.
8)After you are sure that everything is connected and configured properly, and there are no line/network issues you may try using the NETSH command to reset the tcp paramaters. Open an Ms-DOS window and type the following including spaces: netsh interface ip reset log.txt