The nice thing about TCP/IP is that the backup speed from Hard Drive to MAT is really fast this way. At 4800 baud direct connect, figure 3-4 hours. With TCP/IP, figure 20-30 minutes.

Installation Checklist:

1. Use Windows 95 ONLY. Must have a new version of Win 95. Wasted two days with an old version with 13 disks. New CD version looks for 19 disks. Also wasted two days trying Windows 98. With Windows 98 you get an error when you try to ping saying "ICMP.DLL has a problem." Once that driver gets fixed, Windows 98 may be an alternative. I used IMX MAT software Ver. RV Date 10/07/98.

2. Machine should be at least 32 meg of memory, NEC suggests 64 meg, probably a good idea due to Windows 95. Must have Ethernet Card installed to run on their LAN as well as a CD and a floppy disk. Use the floppy that comes with the Ethernet card to have the right driver for the Ethernet adapter. Assuming you have a working Ethernet card with the correct driver, you can proceed!

3. Windows commands (Do this first!). If you have to reinstall Windows, keep the latest versions of the files.
a. Go to Settings, Control Panel, click on Network, view Configuration
b. Look for TCP-IP. If not there you MUST add the Microsoft Protocol. You will need Windows 95 disks or CD.
c. To add, click Protocol, then Add, then Microsoft, then TCP/IP. You must reboot the PC as per instructions.
d. Next, you MUST assign that computer a IP address. It CANNOT be the same as the 2400IMX.
e. Go back to Control Panel, Network, Configuration.
f. Scroll down to your TCP/IP Ethernet Card. Click on it, then click Properties. You may have to delete other setups such as IPX or NetBEUI to get this to work.
g. Click on IP Address. Click on Specify an IP Address.
h. Suggest making up a number close to the IMX number assigned in ADYDL.

I used 172.172.253.3 for the PC and 172.172.253.16 for the PBX. For this example in the IMX, launch ASYDL. Set SYS 1, Index 515 to AC, 516 to AC, 517 to FD, 518 to 10. Also used 172.16.2.200 for the PBX and that worked OK. 172.30.10.200 did not work. Don’t know why.
During the initial IP setup and if you change IP numbers, you MUST back up memory to the hard drive, then reset the switch. That should tell you that you need to get this working long before cutover. Make the sub-net mask 255,255,255,0.

Note that the job spec has a typo on the suggested numbering plan. Note that decimal 10 is really hex 0A, not IC as the Job Spec says. Use at least 3 digits for first two numbers. Call the customer's MIS department if this is going on their LAN and not a direct wiring connection all by itself as they may assign you the two numbers you need. If the customer is running Ethernet, you should be able to plug into an outlet that feeds into one of their 10 or 10/100 hubs. Note that the IMX is running 10 megabits.

Use the Windows Calculator (Accessories) (View Scientific) to double check your hex. Enter a number in decimal and click hex to convert and vice versa. NEAT TOOL!

4. Cabling Issues. a. If you have a hub card in the IMX, use standard Cat V patch cables with straight through connectors.
b. If you are going into the customers external hub, you may have to use a reversal. Our office hub had a port vacant with a switch to reverse so we didn't have to redo a cable. You may need to two Ethernet adaptors in a PC if you want to work on an office LAN plus do TCP/IP to the IMX MAT
c. The port light on the hub will come on green if the cabling is correct.
d. You can connect a cable direct from the IMX to a PC, but then you need to reverse one end. The problem here is that if you shut off the PC, you create alarms on the IMX. Note that if the green light doesn't come on at both ends, you've got cable problems.
e. An expensive NEC hub card in the IMX is not a bad idea so you can plug and unplug PC's without cauing alarms. f. I ran the TCP/IP MAT through our office LAN with our cheap (but very reliable Acton Hub), Novell, running 10BaseT. Did not cause a problem on the office LAN running the TCP/IP at the same time. BUT, our office LAN is 10 Base T. If the customer has 100 Base T, you may need a switch as the IMX is only running 10 megabits. If the customer is running Ethernet, you should be able to plug into an outlet that feeds into one of their 10 or 10/100 hubs. Note that the IMX is running 10 megabits. If they are an IBM shop running token ring, you can’t plug straight in - you need a router that has an Ethernet port or a special switch to route the Ethernet/TCP-IP.

5. Once you think this is working, you need to test the TCP/IP connection:
a. Click on Start, Program, MS-DOS
b. This will give you an MS-DOS prompt
c. Type PING (followed by the IP address of the IMX switch (programmed via MAT direct already) after the cabling is in place. Make sure the lights on the PC's Ethernet card are on, as well as the hub port the card is using. If not, cabling problem. Use CPU port 1 (on the right) for MAT. Port 0 is for Fusion. If two CPU's, then two connections with two different TCP/IP addresses!
d. PING will tell you if it can talk to the 2400 IMX. If it does, you're close to conclusion. If you get any errors, go back to square one and say Bill Gates name along with appropriate four letter words.

5. Install MAT software via CD. Follow NEC directions that comes with the software.

6. Next configure a TCP/IP connection in the MAT software PBX Configure and a different address in the switch in ASYDL as per the manual. Insert the IP address of the PBX.

7. Cross your fingers and try to connect via TCP/IP

If this saved you more than one hour of time, have your company send $25 to Steve Autor, Digital Communications, 244 Eastgate Dr., Danville, IL 61834-9358. Or, if that's too much to ask, send comments to: sautor@digcom.com.

Any corrections or improvements to this page would be welcome. Email to the above address or fax to 217-442-0974.