# Question about going through firewall **URL:** \ **Category:** Ignition\ **Created:** [March 23, 2010, 9:18pm UTC](https://forum.inductiveautomation.com/t/question-about-going-through-firewall/1684 "2010-03-23T21:18:31Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![SonicClang](https://avatars.discourse-cdn.com/v4/letter/s/eada6e/32.png) [@SonicClang](https://forum.inductiveautomation.com/u/SonicClang)\ **Post date:** [March 23, 2010, 9:18pm UTC](https://forum.inductiveautomation.com/t/question-about-going-through-firewall/1684/1 "2010-03-23T21:18:31Z")
As mentioned in Wednesday’s webinar by Dave at the brewery, we too separate our business network from our production network through a firewall. I’m really excited about the possibilities afforded by Ignition, but I’d like if someone could elaborate a bit more on how one would configure it to go through a firewall before I make any decisions. Like Dave, I too am using Access for supervisors/manager to keep an eye on the production floor. This means I’m maintaining two systems; RsView for our operators, and Access for supervisors. The way I’m pulling the data into Access is, the firewall is set up to allow traffic on port 443. I set up the ODBC connections to go to the IP address of the firewall, and Windows sees the production SQL server. I’d love to be able to maintain one system, all launched from the server. But it won’t work if I can’t get through that firewall. ---
**Author:** ![Kyle\_Chase](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@Kyle\_Chase](https://forum.inductiveautomation.com/u/Kyle_Chase)\ **Post date:** [March 23, 2010, 9:40pm UTC](https://forum.inductiveautomation.com/t/question-about-going-through-firewall/1684/2 "2010-03-23T21:40:49Z")
Ignition uses standard TCP. Just allow port 8088 through the firewall, and 8043 if you force SSL encryption. These are the default ports, but you can change them if you need to.