are you using a wireless AP that your hosts are connecting through? i had this same exact problem and it turned out to be my wireless access point. once i connected my hosts directly to the switch i could access all my pages as normal…

Well, I'm afraid this is not an option as the network contains web servers with "unknown" SMTP senders, so we would not know who to block and not to block.  This is why we are looking at the "SPAMBLOCKER" route for outgoing traffic.

You should not be running pfSense 2.0 in production.  It is labeled an "alpha alpha alpha" release and is not suitable for any sort of production use.

oh really? Ok, I will have to give it a try then.

Thanks!

I simply make firewall rules to allow the sip server access and no port forwarding involved…

oh yeah, duh. i forgot that it they are connected with cat 6 but to a 10/100 switch. thanks for pointing that out!

Well the new fix was tested for more than 700 users and it behaved really well.
Even the status->CP was fixed to be usable under load.

It is better to get a snapshot rather than the 1.2.3-RC1 that is in the mirrors cause they might not have updated the new image with the fixes.

Not saying this is always the case, but typically random weirdness of that nature is indicative of hardware issues.

If you can get to a shell, running top -S might help figure out what is taking so long. Pay particular attention to RAM usage.

I'm not sure if it works during the boot process, but pressing Ctrl-T should print on the console what the current active process is when you're waiting on it.

I don't know if this does what you want, but if you serve DHCP addresses to other computers you can have the names of the other computers registered in the DNS forwarder automatically. (Web GUI: Services -> DNS forwarder, tick the appropriate boxes in one or more of Register DHCP leases in DNS forwarder and Register DHCP static mappings in DNS forwarder).

I guess I was hoping to use port number in combination with IP address since apps like messenger and a few others now try to sneak out on port 80.

The problem for me on the port rule is that occassionally apps like the ftp server will try to use these 'banned' ports.

So far I have settled for tracert'ing all the well known ones and building their IP address into an alias for blocking.

As for the p2p I have gone into traffic shaping and set the upload / download allowance to zero.

Not supported and not possible without rolling your own pfSense so also not recommended.

I just did a reboot about 4 hours ago and the problem was solved without any aparent reason.
I did not change anything i just rebooted .

hi-cpu.JPG
hi-cpu.JPG_thumb

Thanks, i'll tried that and if i run into trouble i'll give you guys a shout.  Thanks again.

Everybody from this forum clicked the link trying to help and the server was brought down ;)