I am attempting to do netmeeting securely with an outside party. I will not be using an ILS, just direct address connections for some private business-to-business applications. My netmeeting host computer “Host” has dual NICs – one on our inside house LAN, and one on a DMZ segment. When the machine was initially configured with dual NICs, both NICs were interpreted as gateways causing delayed response time for basic logins and the like (the DMZ route was actually shorter than the regular route). I modified routes in the following ways:
route DELETE 0.0.0.0 MASK 0.0.0.0 {DMZ interface}
route -p ADD {DMZ network} MASK {DMZ mask} {DMZ gateway address}
The routes seemed to be right.
Then, I started up NetMeeting in “Host a meeting” mode. A client NetMeeting from the inside house LAN was successful in calling the netmeeting using direct TCP/IP address of “Host” on the
inside house LAN. However, a client NetMeeting from the DMZ was unsuccessful in calling the netmeeting using the direct TCP/IP address of “Host” on the DMZ.
As a test, I removed the inside house LAN connection, and rebooted “Host”. With only one NIC active, the client NetMeeting from the DMZ
was successful, proving that there was no firewall issue of any kind.
I concluded that in my dual NIC configuration, NetMeeting was listening only on the NIC associated with the inside house LAN.
Does anyone know how to make it listen on both NICs in this situation?