(2) pfSense-2.0.1-RELEASE  (i386)

I wanted to post to this thread ,although our webconfigurator(s) does not exhibit behaviour exactly as indicated in the the OP's initial post.
The two installs are on identical 1U p4 3.2 ghz 2GB ram sata drive machines,,,for completeness to this post.
Over a period of any where from 5 days to 2 weeks the webconfigurator becomes inaccessible. By merely doing a telnet <ipaddress>80 no response is returned.
Doing an ssh <ipaddress>and getting into the pfSense machine console and doing an 11-restart Webconfigurator the webGui is immediately accessible.
We have never experienced the 'hard lock' state as mentioned in some previous posts.

Also worth noting I never had this trouble at all until I issued another admin login for my helper. She is very savy and methodical in everything she does,but the point I am making it seems to me to possibly have something to do with the 'locking' pieces into the web interface built into pfSense.
Now that we know the quick fix it is not a big deal. When this happened the first few times,,I thought it was going to really be a pain to keep this setup working as we need it to.

Also, both setups were clean installs of pfSense-2.0.1-RELEASE but a config from pfSense-1.2.3-RELEASE was imported to each machine,,,just for completeness to this post. I somewhat wonder if this may be causing some config snafoo behind the scene. Just a thought?

Take Care,
Barry</ipaddress></ipaddress>