Or, get a NAT which *does* connection-track H.323. They do exist, open-source and not, and work just fine. Better, get a proper H.323 gateway (which will work behind an H.323 aware NAT if done properly) so people can call in as well as out. However, NAT is still brokenness. (and so is H.323) Andrew --On Tuesday, March 12, 2002 15:17:35 -0800 Joe Touch <touch@ISI.EDU> wrote: > NAT doesn't support Netmeeting. It uses H.323 encoding, which uses IP > addresses and dynamically assigned ports in-band (inside the connection). > The NAT is translating the outer IP addresses, but because your NAT > doesn't understand H.323, it doesn't know it would have to also translate > the inner addresses and ports. Netmeeting expects that it can dynamically > select a port to use to connect back to your machine, but that defeats > what a NAT "thinks" the Internet looks like (notably because it's > incorrect). > > The best solution: get real IP addresses. It's cheaper than wasting your > time figuring out why things don't work. > > Joe > >