What happened was this, There is no pre-defined OWA Policy, so when I created it, I must have hit 'proxy' instead of 'filter'. I deleted the OWA Policy and created it correctly and wouldn't you know it...it now works. I have both the MUVPN and OWA now working. In regards to the SSL Certificate, I assume this is the http vs https thing. This was already set up prior to me coming into this company and to be honest, I just had too much going on and have not ever looked at it. the whole reason for our 'quick-switch' was that we got blacklisted due to our 'helo' not showing our domain. You can not re-write the banner in a Firebox III so we had to overnight a new one in order to get up and going quickly over the holiday week that we are actually shut down. As soon as we got the box in, we got the re-write done, but did not have VPN or OWA access, not good since we are closed but doing Inventory or the Executives wanted to dial in and look around at the numbers. All is good now but has been pretty stressful. I agree that it was annoying to have to use 2 incidents when you pay so much money to buy the thing you would think they would help get it set up right without using incidents. We will see how it goes. I hope my experience has helped others. Thanks for everyone's help.
Kelly
glad everything is working for you. Sounds like you were in the same situation I was in. I thought no big deal, I'll just upgrade while everyone was off. Soon as that happened and stuff started not to work I got orders to order laptops and desktops and load them up with the MUVPN client over the holidays and have them ready by the first. All this and turn online a new file server and move everything over to that. Not much of a holiday for us, huh?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.