New devices not discoverable from Jace.
I have church customer location that is just a pain in the butt. I installed a bacnet capable thermostat last month. I used my host with workbench to discover it, and program it. If I signed onto the building It would not discover from the Jace. Met with IT guy a week later. He did something to his firewall which allowed the device to be discovered. At this time I had him allot me 20 IP addresses for future work. He gave them too me with IP's, subnet, gateway, dns, etc.
Well, today I replaced a controller and a TC500 thermostat. Assigned the proper credentials for each device. Once again not discoverable from the Jace IP. I cannot get them on the building network. I once again had to use my host computer to pull them in and set them up. They work, but it's very frustrating because the end customer expects them on his front end and does not understand the unit is working, but he can't see it. It also leaves my job unfinished. It means I have to meet the IT guy and argue it again.
Called IT again and he's telling me those IP's are open and should work. I told him that If I can be on your building wifi that can access the Jace, but I have to use my Host as a station it's your problem. I'm meeting him again next week. This is a church! It's not the damn Pentagon!
Question: Can wireshark isolate traffic from the ip address of the jace? If I am on their network, and use wireshark to detect bacnet packets can I isolate 10.1.1.205 and capture only what it's sending and receiving?
I am not gonna lie, I am no IT guy, but I want too be after learning BAS work.