Specific ShoutCast Server vs. NAT question

[Rigel]

I have some slightly more specific questions concerning workarounds for a NAT with my ISP in order to run a ShoutCast Server than I have seen in the forums so far.

My wireless ISP sends their signal to a Linksys Wireless Ethernet Bridge antenna (http://www.linksys.com/Products/prod...id=22&prid=432) in my home which then goes to a 4-port minihub, and then to three computers.

I know that NATing is going on somewhere within this setup. Can anyone advise on which are the most likely solutions?

- Is the NATing being done at the wireless ethernet bridge? I don't think it is because I couldn't find any mention of NATing in the entirety of its documentation. If it is, tho, I could use the web interface to fix it myself.
- If, in the more likely instance, my ISP is doing the NAT, would asking them to forward all traffic coming into them at port 8000 to my PC on their network be the correct request to make? In this case, would I enter my PC's IP address or my ISP's IP address into the WinAMP DSP tool?
- If both of these fail, would a static IP address be a viable workaround for the problem? Can a static IP address still exist behind a NAT? Or is the solution to a static IP address on a NAT just freezing my IP address and setting up a forwarding schedule?

I may have more questions as this thread goes along (if I get responses . Thanks for any advice!

[Jay]

most likely your isp is doing the routing and providing you with a LAN address like 192.x.x.x or 10.x.x.x in which case you would have to talk to your ISP about getting it forwarded.

[Rigel]

That's my most likely solution. Would I then enter my ISP's IP or my own IP (198.xxx.xxx.xxx) in the DSP plugin?

[Rigel]

[edit]
Oops, double-post, and I can't delete this entry for some reason.

[Jay]

well if your DSP/Winamp combo is sitting on the same machine as your server then just use localhost or 127.0.0.1

however if you have a firewall, NAT, gateway/router between your server and the internet then folks outside your network won't be able to connect to it to listen to your stream.

[Rigel]

I had it set to localhost and I turned off my firewall, but still had the same problem.

There is the wireless ethernet bridge and a NAT between myself and the Internet. Consensus in the forums has been that port-forwarding on the NAT/Router/proxy will solve the issue. If that's not the problem, then disabling potential IP caching could fix it.

Let me know if you disagree.

[Jay]

yes this is for listeners

but for the source usually if your server and your winamp/dsp combo are located on the same machine these nat/router issues are not the problem. If you have a software firewall then that may be what is causing the problem, some software firewalls block up all ports when they are deactivated so make sure that's not the case here, also try 127.0.0.1 instead of localhost as that won't require a HOSTS file lookup.

[Rigel]

As I mentioned, my firewall (ZoneAlarm) was shutdown when I ran my tests, so I don't believe that's the problem. I've never heard of a program blocking all ports even when it's not running.

As for the NAT port-forwarding issue being only for listeners, one of the group's moderators, among many others in the forums, have recommended that solution specifically for people broadcasting, such as in this thread:

http://forums.winamp.com/showthread....ghlight=yp+nat

Nevertheless, I'll try the 127.0.0.1 and doublecheck my ICS and XP firewall to make sure they're all shutdown or letting the right port through once more. I've also changed the YPort to 666. You were right in the other thread, I may just be stubborn...

[Rigel]

I've now tried running it under Yport 666 and 80. I've tried an Output Configuration Address of 127.0.0.1, localhost, and my ISP's IP. I verified ICS, XP Firewall, and ZoneAlarm are not running. And I tried various combinations of all those.

I just keep getting
<12/16/02@19:52:05> [yp_add] yp.shoutcast.com gave error (nak)
<12/16/02@19:52:05> [yp_add] yp.shoutcast.com gave extended error (Cannot see your station/computer (IP: 66.xx.xx.xx:8000) from the Internet, disable Internet Sharing/NAT/firewall/ISP cache (Connection refused))

Where 66.xx.xx.xx:8000 is not my IP (my IP is 192.168.xxx.xxx).

The only option I can see left is getting a static, internal private IP address and port-map.

If you have a better suggestion, I'd like to know, thanks!

[Jay]

your ip is 192.168.x.x?

that's a lan address the problem is your ISP is running a router/gateway, unless you are? the only way it will ever work outside the lan is if you forward port 8000 to your lan IP from the router. The router is located at 66.xx.xx.xx.

[Rigel]

Yup, although I'll need a static IP address, too, because otherwise as soon as my IP changes (dynamic/DHCP), the whole port-forwarding setup will have to be redone again to point to the new IP.

I'm already working with my ISP to solve the issue. I'll post if it works.

[DJ AmPs]

ISP priovides 192.x.x.x IP? Is you're neigbor the "ISP" ? =)

-amps

[Rigel]

Yes, actually. The ISP I'm a customer of is a small wi-fi business run in our neighborhood. The coverage is a tiny bubble with a connection provided by NAS. The 66.xx.xx.xx address resolves to NAS, so the port-forwarding will have to be done there.

[Rigel]

For anyone who was following this thread, my ISP provided me a static IP address and routed port 8000 through the NAT. I have tested and successfully broadcasted and appeared listed on Shoutcast.com. So, this solution works.

Thanks for all the help, folks!

[V³K†röñ]

i seem to get the same error message as rigel ,... and i'm pretty sure i have no firewall setup on my computer can someone let me know where this NAT is located on my computer (i'm running windows ME on the computer i have this DNAS server on ) so i can disable it and finally be able to use this shoutcast stuff

[FesterHead]

V³K†röñ, please reply with these new details in your thread rather than digging up the dead.