> With 1:1 NAT and the policy above, I should essentially be 
> wide open through my public IP, no? Everything else works 
> fine; RDP, PCAnywhere, VNC, you name it... just NO NETMEETING!

From what little I remember about Netmeeting - it uses a subset of h.323 for
audio/video. h.323 is even more a pain in the backside to get running
through NAT than SIP. Generally with SIP, you've got 2 options - 1) rewrite
the outgoing SIP headers with the true external IP, or 2) use an outbound
SIP proxy that'll rewrite the headers for you before sending them on to the
remote party.

Remember, you are *technically* still behind nat, even if it's a
fully-mapped symmetric NAT. If you want to give each client a true public
IP, you'll need to use the filtered bridge rather than 1:1 NAT.

Sorry, I know I haven't really come up with a solution, but hopefully it's
at least an explanation of the (likely) problem.

Regards,

Chris
-- 
C.M. Bagnall, Director, Minotaur I.T. Limited
Tel: (07010) 710715   Mobile: (07811) 332969   Skype: minotaur-uk
ICQ: 13350579   AIM: MinotaurUK   MSN: msn at minotaur dot cc   Y!: Minotaur_Chris
This email is made from 100% recycled electrons