Ok I am not sure if I asked the question correctly so have mercy. My network is growing at work and I am finding it hard to manage my firewall rules. The problem I am having is 2 fold:
- I have 4 servers at work and with progress more services are being added, in the past I have managed to route traffic ok since either a. two services requireing the same port were on the same server and I could let IIS work it out or b. if they were on different machines they used different ports i.e. http, https, ftp, etc.
- The users are stubborn and refuse to have to remember non-standard port numbers to get to internal servers from the outside. (one idea I had was if I had two services needing the same protocol (http) I would change the port on one to be able to route that traffic to the correct server)
I will admit, this is a smaller company and I am the only admin here and while I feel that I am competent, all of my previous experience was with large companies and I basically did 1 task all day long. Now that I do everything I am realizing how detrimental that was to my knowledge level. So if there is something stupid simple that I have overlooked I appologise for wasting your time. Either way thanks for looking and for any help you may offer.
One note though the environment is all windows so linux cant be a solution, and I have been told to figure it out and not spend money, if I could I have already found other firewalls that claim to do what I need. but I am sure that either the sonicwall or somehow using the onsite dns server to route requests to internal ips. (FYI I was a AD admin for 5 years before this job and my weakest skill-sets are dns and firewall routing).
Thanks again for any and all help.