Thanks Eugene! :) It was a Nat Rules that i forgot to add.. ;D If        Proto     Ext. port range   NAT IP          Int. port range **WAN       TCP            2222          192.168.1.30 2222  ** Please close this..SOLVED Happy to be with my pfSense Family!!!!

You can try the Snort package.

@tommyboy180: @cruzades: @tommyboy180: You can block port 80 traffic from going outbound from that particular box. This will force the client to configure the proxy. yup, but this will affect the whole network instead of just only one client. You can setup the outbound rules so that only one box will have port 80 blocked. It won't affect your entire network, just that one box. Example, deny port 80 from 192.168.1.199; all others pass. oh I missed the 'box' thing, anyway I want to make it automatic without further configuration at the user's end, is it possible?

Or access the internal server via a name? You could then do split DNS for the internal server. (And thus access it with it's internal IP directly)

This should help explain http://forum.pfsense.org/index.php/topic,5144.0.html

yeah i kinda figured it wasnt working properly before nice to know its in the pipeline though thanks

Why not use VLAN???

Thanks GruensFroeschli! I appreciate your help  :)

Thank you for your reply. This was a big help. I was able implement all firewall rules on the fly. After you pointed me in correct direction, first I used pfctl -F state            this did the trick and all new rules implemented immediately. Than I looked around under WEB GUI and found the following link that made the job really easy. DIAGNOSTICS –-> STATES ---- RESET STATES THANKS :)

LMAO!

IF you're looking for control, you may want to consider using Packetfence in conjunction with PFsense.

DISABLE  FTP Helper on ALL interfaces Interfaces -> Lan/Wan - > FTP Helper [CHECK]  Disable the userland FTP-Proxy application

I have done.. but I didn't find the answer to my problems.  :-\ I will continue.

http://forum.pfsense.org/index.php/topic,17782.0.html