"Dreaded NAK", other than firewalls?

[radiodad]

Attempts to restore audio streaming after 6 months of webcasting 24/7 remain ineffective and currently stuck on what has been called “the dreaded NAK error”. The question that seems appropriate to remedy proposals like uninstalling routers and modems to get rid of all firewalls is how could firewalls have appeared if they were not blocking audio streaming before? The problem seemed to occur about the time an attempt was made to download the 5.111 Winamp, apparently while the old one was still running and linked to Shoutcast. The download crashed, as did the outgoing stream. It has been off-line ever since. A clean uninstall and reinstall also failed. With no Winamp player, one was copied from a companion computer and pasted into the server. It is now successfully playing and again linked to Shoutcast and heard on the companion computer, but the NAK block is apparently preventing anyone else from hearing it. The question again is how could a firewall problem exist now that wasn’t there before the ill fated update download event? Searching Winamp and Shoutcast Forums so far has failed to reveal anyone with similar problems, though there are many more “threads” to scan. In the meantime, if anyone has any clue what the problem may be, please give me a shout,. rick@musictampabay.com

[drewbar]

It is impossible for Winamp to cause the NAK error. It is caused by the outside world not being able to access the port the DNAS is running on. This can only becaused by some kind of firewalling, be it a software firewall, hardware firewall, NAT (done by routers), or the Windows firewall.