<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>
My server gets this error: "[yp_add] yp.shoutcast.com gave error (nak)" -- What's wrong with my server?
Answer: The SHOUTcast directory has refused to publish your directory entry for one of a number of reasons. Your server should have an extended error message as well which might correspond with one of the following:
* NOTE: If the extended-error message is accompanied by an IP address, check to make sure it's the same IP address and port you're running the SHOUTcast server from. If it's different, then something is changing your IP address before it gets to us. This is usually because of internet sharing devices or software. DSL routers and cable modems typically are the culprit, as are corporate firewalls, NAT devices, or web caches.
We are working on a solution for the web caches, but if any of the other devices are changing your IP, you will *have* to follow the instructions under Connection refused: below to solve your problem. Listeners on the internet will not be able to listen to your server until you fix the problem.
* Connection refused: This typically means your server is not visible from the Internet. The usual cause is that you're located behind a firewall or NAT device (this includes internet sharing programs like Sygate, Wingate, etc.). These devices block incoming connections to your network. You need to configure these devices to map port 8000 on the device to port 8000 on the computer running the SHOUTcast server. If you have changed the SHOUTcast DNAS configuration to have different values for the ports, you should map that port instead. The important detail is that the SAME PORT YOU BROADCAST ON MUST BE THE PORT MAPPED FROM THE OUTSIDE. That is, you can't map port 99 to port 8000 and expect it to work. It won't.
* Connection timed out: This means the SHOUTcast directory attempted to contact your server, but never reached it. This is usually due to ISPs or corporate networks blocking incoming traffic. Occasionally this is because the Internet is tweaked and the directory can't find a route to your server. Reasons for this can be as various as ISPs around the world disagreeing on route tables, overburdened connections between your ISP and the backbone, or just general net flakiness. If it doesn't clear up after a day or so, ask your network provider if they block incoming traffic.
My problem was that my ISP blocks traffic on port 80 for a web cache, shoutcast also touches servers to see if they're alive on port 80, so the server would return NAK error when yp.shoutcast.com tries to list. The remedy was to change the YP port in shoutcast configuration to use port 666 instead of port 80.
Drink or Die! Barstool Blues