#Scott McHugh

1 messages ยท Page 1 of 1 (latest)

smoky dewBOT
light terrace
#

A screenshot of the network calls I see

atomic crane
#

You mentioned this started happening recently. Has anything network-wise changed in this timeframe? Also, is this connectivity issue intermittent? Have you seen any successes recently?

light terrace
#

I reached out to the customers IT support, they indicated no network changes have occurred. I'd also asked about firewalls etc, but they indicated it was fully open. The issue is persistent, no successes since the problem started occuring

#

(their network IT person* - I work for the software company that provides their point of sale)

atomic crane
#

Ok gotcha. Thanks for all the details. Let me reach out to a colleague so I can get a second pair of eyes on this

light terrace
#

thank you- really appreciated!

old citrus
#

Hello ๐Ÿ‘‹
I am a bit confused by the error message in the console as it says unable to connect to Verifone terminal but WisePOS E isn't really a verifone terminal.

light terrace
#

yeah, that seemed odd to me as well

#

I know the same setup does work when I test from my home network (that call resolves)

old citrus
light terrace
#

good call, I'll try that

old citrus
#

Yeah, that would help us confirm if the issue is with their network

light terrace
#

ok, yeah when I hit the device off my hot spot it does make that request alright- and I can get to the point where it finds the reader, then when I go to process a sale it shows the 'waiting for payment' on the reader as expected. The jackrabbit requests come back with a status of

#

status 200 ok, no payload, which seems clean

old citrus
#

Right, so looks like something in their network configuration is preventing Reader DNS from resolving..

light terrace
#

thank you for your help! Been testing variations of the set up. I appreciate your time.

old citrus
#

NP! ๐Ÿ™‚ Happy to help