First, you really should restart by reinstalling Worx. A corrupted filesystem may cause a lot of grief down the stream -- I'm speaking from long experience here --, so the sooner you do the reinstall, the easier and better it is in the long run.
Second, like OdinnBurkni said, if you use a single cable between Worx and MIC, it has to be a
patch or
crossover ethernet cable (as opposed to a normal one). You can check by looking at the wires in the connectors side-by-side: a patch cable is
ABCD-CBAD, where normal is just
ABCD-ABCD. (
Here are some nice images.)
Third, again like OdinnBurkni said, you need to set up a static IP on the same subnet as MIC on the the second interface on Worx. The details differ a bit between Linux distributions, but you did not state which one you use. The one thing that bites people is the routing table. When setup correctly, the networking scripts will automatically set up correct routes for the interface. Since distributions differ, some people tend to just "hack it" to work rather than learn what the preferred configuration method is for that distribution -- and the routes don't get set properly. As you probably know very well,
route -n will show the routing configuration.
It is very common in University labs to have a "black box" instrumentation machines connected this way. You should be able to get it working very well.
Hope this helps,
Nominal Animal
