If Sonicwall isn't supporting H.323 over NAT as advertised, that's actually more usual than unusual re: Vendor's claims... The only firewall I've been able to configure this successfully are the Microsoft firewalls.
You may want to try opening the required ports <manually> instead of relying on automatic configurations in case that might be an issue... But in general H.323 over NAT will fail because of Vendor implementation. Recommend at least trying the "non-multimedia" parts of NetMeeting to see if they work, they don't use H.323... Ie. The Whiteboard, chat. I've found they work well, in general you should have problems only with anything related to voice or video. Tony -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jason Hobbs Sent: Thursday, March 21, 2002 8:14 PM To: [EMAIL PROTECTED] Cc: 'Jeff Vogt' Subject: RE: [SonicWALL]- netmeeting setup Good luck :) Try using one of the other connection methods and NOT H.323 (not even sure if NetMeeting has other protocols as an option)... Basically the problem is that Net meeting figures out what IP your machine is at by essentially querying the NIC, and it encapsulates that information into the request that it sends to the remote machine. i.e.: Net meeting sends out a "ring" to the answering machine that says "Yoo-hoo! Here I am on 192.168.1.2! Come get me!" ....the remote machine can't get back to your 192.x.x.x NATted machine, and it's very frustrating. The H323 protocol is not very NAT-friendly (unless you have some hardware with some "application aware" NAT). I managed to "trick" CUSeeMe into working with H323 at one point by adding a second IP to a Windows 98 machine, specifically my WAN IP. I had to tweak it a few times and change the orders the IPs were added in the network configuration so that it showed up as the "#0 Ethernet adapter" address when doing an ipconfig on the command line, but it did eventually work... Not the best solution though... Prolly not good to have yer WAN IP being spoofed on the LAN. :) ...The other solution is to get some more IP addresses and use the Sonicwall in standard mode. Then it works like a charm :) ...It's been a while since I played with this so Sonicwall may have changed some of the H323 support, so y'all let me know if this is possible now... As far as I know though, H323 and NAT go together like.... like... like stuff that doesn't go together very well. Jase -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jeff Vogt Sent: Thursday, March 21, 2002 6:14 PM To: 'Sonicwall (E-mail) Subject: [SonicWALL]- netmeeting setup Hi all, I went to the sonicwall site to get instructions for setting up the sonicwall to allow for netmeeting. the instructions said just to add the 2 known services for whiteboard and videoconference services. Then I added them in on a public lan server. I set the client up with a dhcp reserved ip address, and rebooted the sonicwall. I am unable to establish the netmeeting session. i know that the problem is on my end because we have been able to establish the netmeeting session from the remote end (that I was working with today) and my users home (no firewall there) Additionally, I attempted to establish the netmeeting session using IP adresses only. Anyone out there have any experience setting this up and if so, any documentation that is more thorough than what is on the sonicwall site? thanks for the help Jeff --- [This E-mail scanned for viruses by Declude/F-Prot Virus] =================================================================================================== To unsubscribe, send email to [EMAIL PROTECTED] In the body of the email put the following: unsubscribe sonicwall your_name The archive of this list is at http://www.mail-archive.com/sonicwall%40peake.com/
