Pinging one way...frustrating sauga

[mrmicros]

Pinging one way...frustrating sauga continues.

On kds no matter the ip entered we get Conflict error.

OK let it obtain an ip and see what comes up.
192.168.2.120
Set kds to that and it takes it.

From server can ping.2.120 with reply. Ok

From kds cannot ping server 192.168.100.100??

Running cal previous could not find server??

Front of house all fine.

So WTF?? Please and thanks.

 

[Wildbar]

You appear to be on different ip ranges. Ping 192.168.100.120 and if its not in use set the kds to that and try Do you have a second router or something assigning the wrong ips?

 

[mrmicros]

Lets try this again. These two kds started popping up with ip conflict error and takes them off line.

In the kds network setting assign any address and save you get ip conflict error.

Set kds network to auto to see what ip it would assign.

Ipcomfig listed 192.168.2.120

Manually entered that ip and save it with no ip conflict popping up.

Seems try any in the 192.168.100.??? And it's a conflict.

Cannot ping server 192.168.100.100

Internet seperate nic set to auto. Unplugged same results

 

[Wildbar]

What are you using for controllers for the kds?

 

[POSKitchen]

Check the routing from 192.168.2.xxx to 192.168.100.xxx and back.
Perhaps the Firewall of the Server is active, if you can not send a ping from the kds to the server.
Also check that the dhcp range is not in the static range of the POS.

I know that I had issues if the server has two NIC. In some versions, the KDS controller service on the server is crashing all the time. Worked only with 1 NIC.