You can do a packet capture on the interface the DHCP server is listening on and after that analyze it with wireshark or any other tool.

thank you very much. you assumption was correct. Is was regarding maxing out my upload. What limitation would be recommended on a 1024 upload speed. shall i set the limit to 50Kib/s

Hi, yes, some tunnels are configured to use a FQDN with a domain 'hosted' by dns (with a very low TTL, making the cache useless). And the problem get worse when the internet line is down so you must be right. Thanks a lot !

i fixed it guys. tried the new snapshot and its working now with the rule activated on lan however i had to insert the ip via //ip/share etc because it doesnt seems to auto discovery when click network which is no problem

the other thing i cant decide about, is why if i boot the pfsense cold with no cables, and then plug it in does it work (obivously the openNTP hang is there, because there is no internet). why does it work after a complete boot and cable change, whereas if i leave it all plugged in and boot it that way, it refuses to find the internet and route traffic? unfortunately ive not tried it with 1.2.3, as i need the features in 2.0 in order to accomplish multiple cisco vpn clients to the same VPN concentrator (a customer's requirement… and this part works fine in 2.0-RC3).

All you should have to do is port forward 25, 80 and 443 to you exchange server. That is all I am doing and it works just fine. Did you change something on exchange? Looking at your NAT, it does not look like you are forwarding port 80. Yes, I would start over as well and have only this rule in the LAN Tab LAN net * * * *   Default LAN -> any Just go to Firewall > NAT > Port forward for you Exchange services WAN TCP * * WAN address 80 (HTTP) Exchange 80 (HTTP) WAN TCP * * WAN address 443 (HTTPS) Exchange         443 (HTTPS) WAN TCP * * WAN address 25 (SMTP) Exchange 25 (SMTP) etc. The Port Forwarding will auto-create some rules in your WAN leave them there.

You shouldn't be using 1.2.2, its VERY old.  2.0 is practically released, the RCs are extremely stable.

It would help others if you could tell people how it was solved and what the problem was.

@chpalmer: Otherwise give it an hour or two after you reboot the router. It takes time before the client will trust your server… This - openntpd needs some time before it considers itself accurate enough for syncing clients (why it doesn't log that…another story). If you get a pcap of the NTP traffic you'll see in the response it has the code set indicating that. You have to wait an hour or two after enabling it.

What Joel described, though you'll also need to enable the serial console under System>Advanced.

Professional = paid for your work… Amateur = volunteer... One is not necessarily any better at their job than the other.  :P But that said- If you were to buy services from me Id say the exact opposite-    ;D

Just tested sticky connections with 2.0-RC3 (i386) built on Wed Jul 13 18:38:42 EDT 2011 No improvement.

Thanks. And safe reboot is?

Thank you for your help I will check it out.

Thank you, that helped. So I need to think which interface the traffic is hitting first.