Hello all,
I'm using PD within an intranet (I've got 3 computers networked using a D-Link 704 Ethernet gateway/router) and I'm having trouble using netsend and netreceive in this environment.
It looks like I need to configure the D-Link manually to allow communication on specific ports - it has a built-in firewall. For example: I've manually configured the D-Link to allow incoming messages to Port 21 for FTP services on my server and port 80 for WWW messages, etc.
I can configure the D-Link to 'listen' on any port I want, but only if there's an outgoing message that corresponds to the incoming port. For example, if a message goes out of PD on port 3000, then the firewall allows a response from an external computer on the same port.
The D-Link interface calls this a 'trigger'. Hence, if PD's netsend (for TCP) uses port 200 for all outgoing message, then I can tell the D-Link to open ports 2999-49999 for incoming messages.
So the question is: Which port does [netsend] use for outgoing messages?
many thanks.. Dave Sabine
David Sabine schrieb:
So the question is: Which port does [netsend] use for outgoing messages?
Hi David,
what problem do you run into? Does netsend refuse to connect? - I encountered a similar problem yesterday using a OS X machine behind a firewall / proxy. A call to gethostbyname() returned an error and made netsend, shoutcast~ ans others unusable. This gethostbyname() is used to translate the hostname you can type into the connect-messagebox into an IP address. In case Pd can not reach a DNS Server or resolve the hostname because of other problems this function will fail. netsend then says: "bad host?"
In my setup it seems that Pd does not use the proxy settings given in the system preferences. (Or the terminal does not use them; I coulnd't even ping the other machine.)
Olaf
-
David Sabine -
Olaf Matthes