Appologies for newbie things but I have to start somewhere.
I’ve got a 4 module rack with an EB2 connected to a power supply (SNAP-PS5). Also the
latest PAC Manager interface code 9.2. I’m running on a Dell Inspiron 5520 with Windows 7
64 bit.
I’m attempting to determine what state the EB2 is in (don’t know if it has an IP established or not)
Here’s my questions:
-
Should I be trying to interface directly from my network interface card with the EB2 (ethernet 1 on the card)? I’m keeping the connection off my intranet due to DHCP which I understand is something the documentation says to avoid.
-
The documentation says that for an EB2 any ethernet cable should work. I take this to mean that a crossover cable isn’t needed. And that’s my next question is a crossover cable really not needed? With a statndard cable I’m seeing a flashing ACT light as well as a flashing NS (all other lights are green and steady). I did make a crossover cable but given that I got no flashing ACT I assume I screwed up one or both ends.
-
Lastly, I’m using a static IP address on the Windows machine. This seems ok when I’m connected to my intranet but as soon as I connect to the EB2 I can see that I’ve got an unidentifed network and no network access in IPv4 or IPv6. I wonder what this is telling me? Is there a relation between the static address on my Windows machine and the EB2?
There is definately a relation between the EB2 IP and the computer’s IP when I have a fully functioning system as both need to be able to communicate. But I wonder if this matters when your just trying to “see” the EB2 and maybe set its address.
Thanks for any help.
Dave