This is the message I get in the logs for why it is being blocked: "The rule that triggered this action is: @12 block drop in log quick proto tcp from <webConfiguratorlockout:1> to any port = https label webConfiguratorlockout"
[image: Inline image 1] * * * * On Mon, Jul 16, 2012 at 5:57 PM, Brad Otto <brad.o...@p3ctech.com> wrote: > Hi PFSense community - > > I've got an odd one for you! One of the admin users with access to the > firewall says she was adding a user to our VPN, and after that point, she > was unable to use HTTPS on her office computer. She could not get to https > websites - period. This was the only computer exhibiting this behavior. > Other computers on the same network did fine. > > I've run through every troubleshooting guide imaginable for Windows, and > when that failed, I even rebuilt her computer. But nothing did the trick > until I switched her reserved IP address to another address on the same > network. > > I checked firewall rules, aliases, etc. but did not see anything in > pfsense that the user might have touched which would bring this type of > behavior. Any tips? > > Thanks! > > -Brad >
<<image.png>>
_______________________________________________ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
