Unable to connect to Kulp K8-B

[algerdes]

Please tell me what I am missing.  The Good Lord knows I've been doing this for a long time, but for some reason I'm not able to do a simple thing ...

Kulp K8-B, 12vdc, using all 8 onboard outputs and one of the differential sender outputs (channels 9-12) with Falcon Smart Receivers (x2).  

While I had it in the shop, I setup a playlist, schedule, and uploaded a sequence (short).  Also, while in the shop it received its IP address via our lighting router's DHCP function.  (I did not set a static IP while in the shop - forgot.)

In the field (quite literally in a field) there is no Internet, no DHCP provider, etc.  Just 110 VAC power. I had to set the IP manually using the buttons on the K8-B.  I set its IP to 192.168.2 111.  I changed the IP on my laptop to 192.168.2.1.  Both have subnet masks set to 255.255.255.0.  The Kulp has its Gateway set to 192.168.2.1.  A physical Ethernet cable is present between the laptop and Kulp.

Nothing I tried out in the field allowed me to communicate with the Kulp.  

I do this every day with a couple of stand-a-lone falcons (FPP on an RPi, physically located in the same box and connected to a Falcon controller.)

I also tried to connect via wifi, but did not find any wifi signals from the Kulp as is mentioned in many threads.  (Side question - is there a built in wifi module on the K8-B?)

Anyone have any ideas as to what to try now?  

[algerdes]

One thing to note is that it ran just fine on schedule.  The small sequence started on-time, ran all night, then shut-down on time.  All outputs worked.

Just can't connect to it to make adjustments or update the sequence.

Did I have to power boot it after making the IP adjustment?  Anything else I need to do with it?

[K-State Fan]

There is not any built in wifi on the K8

I have always had trouble hooking something directly to the computer.  I would try using a switch.

[Sawdust]

This is where i would think to use Tethering Mode - or turn off so it doesn't block other connections

[breese]

Seeing you setup the computer and the Kulp on the same sub-net, with a network cable between them, I would reboot the kulp and then try to ping it.
If you cannot ping it, then its either the network cable is bad or you missed something in configuring the IP on the computer or the kulp.

There is no other reasons why you would not be able to communicate between the 2.

[algerdes]

Thanks for the information folks.

I agree Breese.  It should work, but doesn't. 

I've verified the cable as being 100% good via test devices.  Also plugged it into a known good connection without any problems, so will consider it not the culprit.

I'll give it a reboot, now that the "show" is idle, and see what comes up.

Thanks again, if for nothing else but to clear my mind as to what I've done is accurate.

[algerdes]

OK.  What a difference a day (and a good night's sleep) makes.
Was able to power cycle the K8.  Once that happened I was able to connect via Ethernet and make all the adjustments I needed.

Don't know why it doesn't set the IP when input on the OLED.  Apparently it did set it in the boot file.  A reboot did it.  Oh well.

Thanks for all the advice both here on the forum and offline.