Network Problems
Most problems with Commander-IS are likely to be due to network access of Imagestores.
A simple check is to confirm that the Imagestore can be contacted via Ethernet using the ‘ping’ command from the DOS prompt. If this works, you should see something like this.
If ‘ping’ fails for any reason, see the checklist below.
Ping Problems
If the ‘ping’ command to an Imagestore fails, then consider the following possible problems:
- Imagestore does not have Ethernetlicense – All Imagestores have the RJ45 connector, but the license must be ordered from Miranda.
- PC IP Address is not on same ‘subnet’ as Imagestores. If PC is on 123.12.1.100, with submask = 255.255.0.0, then the Imagestore must have an IP address of 123.12.x.x (NOT 123.12.1.100!) and a submask of 255.255.0.0
- PC IP Address is same as an Imagestores. (See above)
- Failure to use 10/100 auto-switching hub between Imagestore and PC. (Imagestore must run at 10Mbits, while modern PCs typically run at 100 Mbits per second.
- Cabling problems
If you are unsure of the Ethernet setup or cabling, or have systems supporting gateways, multiple networks, multiple IP addresses on a single PC, or other sophisticated networking techniques, then you should first consult your local PC administrator for advice.
DNS Problems
If Commander-IS runs very slowly, taking several seconds before it connects to the Imagestore, then a likely cause is an incorrect DNS or setup of the PC.