kcarpenter
01-02-2008, 08:11 AM
This is basically a server NAT'd behind our cable modem in the SE Lab and the scope of this setup was to connect to it from our home machines and use WAVE.. From Shaun Botha:
1) Added an entry in the machine's \Windows\System32\Drivers\etc\hosts file to be "127.0.0.1 wavedev01.twistpair.com". This way the Management Server software can speak to the same machine without having to go to the external IP to reach the Media Server on the same box.
2) Changed the host name of the Media Server used by the Management Server to be "wavedev01.twistpair.com". I didn't change the machine's actual name - just the name the Management Server software uses to call it by.
3) Changed configuration URL in the Media Server INI file to be:
http://127.0.0.1/wave/_interface/get_media_server_config.asp?name=wavedev01.twistpa ir.com
This way we don't have to change the machine's actual host name (from "pod2client" which it actually is) and still have a nice name show up in the Media Server list.
4) Set the Supernode NAT address for the Media Server (in the Management Server's "Media Servers" page) to be the NAT'ted public IP of the box. This allows the Supernode to hand out its public IP to connecting clients instead of the internal 192.168.x.x address. Doing so allows for (at least) one-way UDP audio streaming instead of two-way TCP.
1) Added an entry in the machine's \Windows\System32\Drivers\etc\hosts file to be "127.0.0.1 wavedev01.twistpair.com". This way the Management Server software can speak to the same machine without having to go to the external IP to reach the Media Server on the same box.
2) Changed the host name of the Media Server used by the Management Server to be "wavedev01.twistpair.com". I didn't change the machine's actual name - just the name the Management Server software uses to call it by.
3) Changed configuration URL in the Media Server INI file to be:
http://127.0.0.1/wave/_interface/get_media_server_config.asp?name=wavedev01.twistpa ir.com
This way we don't have to change the machine's actual host name (from "pod2client" which it actually is) and still have a nice name show up in the Media Server list.
4) Set the Supernode NAT address for the Media Server (in the Management Server's "Media Servers" page) to be the NAT'ted public IP of the box. This allows the Supernode to hand out its public IP to connecting clients instead of the internal 192.168.x.x address. Doing so allows for (at least) one-way UDP audio streaming instead of two-way TCP.