It's just that H.323 (or Netmeeting's implementation?) uses dynamic ports for connection. So, you can only get it to work by putting your PC on the DMZ. Of course, I can't do that since I don't want to put a machine on the net unprotected (yes, there is personal firewall... but....) and I'm running a web server which is behind the firewall happily using port forwarding. To make it more complicated, my new housemate Martin might want to use Netmeeting as well.
I would think standard like H.323 have take into account for working in different enviroment, but did it? Maybe I shoudl take a look into it.

Did I say it's suck not able to get it to work?
Update: So, I saw some posts on the Internet regarding who's to blame. here...
It basically said H.323 is developed standard before NAT is widely used and it is working for many routers.... right! But NAT is deployed in millions of home around the world now and what to blame here? I just hope they fix this in the future.
NetMeeting h.323 and a NAT router
Comments
Leave comment
Trackback