#sumishi_val-terminal

1 messages ยท Page 1 of 1 (latest)

royal mangoBOT
thorny depot
#

Is this a new integration?

#

Or existing one that began failing?

maiden pike
#

Existing one that is now failing after a change in our network layout, I can't see anything in the firewall showing a blocker. I have a video of the link process as to what happens in the inspect

thorny depot
#

Hm what exactly changed in the network?

maiden pike
#

We added a new firewall and to separate our corporate network from guest network so we recreated the exact VLan from the old firewall on the new but for some reason we are getting these connection issues, some are using TLS 1.2 some using HTTPS/SSL

#

All I could find in logs for an exact unit was the following

#

date=2023-10-17 time=15:04:11 eventtime=1697555051279963979 tz="+0000" logid="0000000020" type="traffic" subtype="forward" level="notice" vd="root" srcip=192.168.3.32 srcname="WSC513101001797" srcport=37876 srcintf="BUY-WIFI-VLAN" srcintfrole="lan" dstip=198.137.150.131 dstport=443 dstintf="wan1" dstintfrole="wan" srccountry="Reserved" dstcountry="United States" sessionid=2056278 proto=6 action="accept" policyid=1 policytype="policy" poluuid="81e8da40-6476-51ee-ca46-c2cbc47588ad" policyname="LAN to WEB" service="HTTPS" trandisp="snat" transip=192.168.100.100 transport=37876 appid=40568 app="HTTPS.BROWSER" appcat="Web.Client" apprisk="medium" applist="block-high-risk" duration=137 sentbyte=580 rcvdbyte=14873 sentpkt=11 rcvdpkt=13 sentdelta=580 rcvddelta=14873 osname="Android" srcswversion="9" mastersrcmac="20:59:a0:1c:eb:16" srcmac="20:59:a0:1c:eb:16" srcserver=0

thorny depot
#

Hm not sure. Let me ask a colleague

maiden pike
#

No worries thankyou ๐Ÿ™‚

thorny depot
#

Can you run a ping command from the machine your POS software is running on to the terminal reader's ip?

#

And share the result in here

maiden pike
#

Of course

Pinging 192.168.6.105 with 32 bytes of data:
Reply from 192.168.6.105: bytes=32 time=60ms TTL=64
Reply from 192.168.6.105: bytes=32 time=69ms TTL=64
Reply from 192.168.6.105: bytes=32 time=5ms TTL=64
Reply from 192.168.6.105: bytes=32 time=95ms TTL=64

Ping statistics for 192.168.6.105:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 95ms, Average = 57ms

thorny depot
#

Ok so you can reach your reader

#

Issue is reader can't connect to Stripe then?

maiden pike
#

Apologies I was connected to the wrong network, when I ping from the new corporate I receive the following

Pinging 192.168.3.23 with 32 bytes of data:
Reply from 192.168.3.51: Destination host unreachable.
Reply from 192.168.3.51: Destination host unreachable.
Reply from 192.168.3.51: Destination host unreachable.
Reply from 192.168.3.51: Destination host unreachable.

Ping statistics for 192.168.3.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

But no indicator on the stripe that it has no connection

#

I suppose I will need to find why i'm receiving no connection on the terminal, I'm just resetting and rebooting so it will get a new IP reping and if no luck I know where to fix

thorny depot
#

Yeah and you're certain the reader and pos are connected to the same network?

safe goblet
#

sumishi_val-terminal

maiden pike
#

Yes definitely the same network

safe goblet
#

๐Ÿ‘‹ hopping in here since codename_duchess has to head out

maiden pike
#

No problem at all

#

Unfortunately i'm getting the same results when a new ip has been assigned so I'm guessing it will be something related to our new vlan?

safe goblet
#

Yeah... it seems like something must be different after moving to your new vlan, but I'm not sure what it could be

maiden pike
#

Looks like it will have to be a tomorrow fix network team gone home for the day. Thank you for the help anyways ๐Ÿคž i'll get this done in the morning

safe goblet
#

๐Ÿ‘ good luck!

maiden pike
#

Thankyou!