Firewall Blocking

rosco · 17th January 2001, 00:53

Hello:
I think my ISP is providing me with a IP address that is behind a firewall, I current am getting the "nak" error
s when I use the shoutcast DNAS. Is there a quick way to find out? My ISP is sometimes hard to get in touch with.

Thanks

BIGDADDY · 17th January 2001, 02:11

which nak error is it? the online documentation will explain which codes mean what.

RuphBear · 17th January 2001, 12:15

If you're running behind a firewall, you need to make sure that the ports used by Shoutcast are open, or forwarded to the PC running Shoutcast. I never did get this to quite work behind my firewall, but I'm not a network expert.

Ruph

rosco · 18th January 2001, 00:48

Hello Again ..
This is the error I am recieving, I have tried different ports. Still get the same results

<01/17/01@17:56:54> [yp_add] yp.shoutcast.com gave error (nak)
<01/17/01@17:56:54> [yp_add] yp.shoutcast.com gave extended
error (Connection timed out 200.55.127.143:8000 check
shoutcast.com troubleshooting)

CompuTurk · 18th January 2001, 06:18

You either need to forward all port 8000 requests to your internal IP behind the Firewall that starts with 192.168..
or..
probably the best thing to do would be to move your internal IP to DMZ...let all the ports be open. This might slack the security for that specific computer, but move your computer to DMZ...

Good luck,
-CompuTurk

CompuTurk · 18th January 2001, 06:20

Also check the following link out, it might be helpful.

http://www.shoutcast.com/support/doc...vlayout=normal

Radio CMU San Pablo · 18th January 2001, 14:52

I'm not sure about what does it mean, it doesn't look like the common port error...
Anyway, be sure that, as computurk said the port 8000 isn't being used by other server, like a web page or sth like that, this port is usually open, so if it doesnt work, the most probably reason is that sth is using it (sth like a page being hosted, for example).
Anyway, as it doesn lokk like the common port error, u can try to shoutcast using another port (read the ini file in order to know hoe to change the port number)
Good luck

rosco · 18th January 2001, 23:28

Is there a possibility that the IP address that is shown in the error, isn't really the correct IP address.
Is there a way to find out what "exactly" what my IP address
is
Thanks

wedgemusic · 19th January 2001, 00:00

If you are using Windows, run winipcfg to find out your real IP.

Radio CMU San Pablo · 19th January 2001, 00:31

Rosco, it depends on whether your LAN uses statics IPs or dinamics IPs, the best is static IPs, but based on my experience I would say, ti doesn't matter, because if u r using dinamic IPs, your server will probabily assign usually the same IPs to each computer.
In order to check this, and to now your server and your source IP, u can open the DOS window in windows and type
ping name_of_computer
where name_of_computer is the name of the machine u want to know IP, the name as appear on your network. Once you type it, it will show u machine's IP.
Good luck

kbi · 19th January 2001, 05:30

hey guys! i've had the same problem with shoutcast. it doesn't depend on firewall settings. the problem is, that
shoutcast is unable to connect to the main shoutcast.com
server, and it shows something like that. just wait some
time, until server will connect. it will believe me

rosco · 19th January 2001, 21:09

I have had the server running well over 5 hours and got the error about every 5 minutes.

rosco · 20th January 2001, 18:03

I finally got it to work correctly, (I think) I turned off internet sharing on the computer, and was able to connect without the errors listed above, How can I correct this and still be able to activate internet sharing..

djderricke · 22nd January 2001, 03:38

The problem is that the Shoutcast directory tries to verify that the IP address it is given is actually running a shoutcast server. This is to avoid people from creating bogus redirects to other websites. What I had to do with my internal network was open up port 8002 (I'm using 8002-8003 not 8000-8001) and map it the internal IP address that is running my server. So when you go to my Shoucast server @ 64.7.13.90:8002 (which is actually my router) it is really going to an internal IP address. But since that address is mapped within the router, the shoutcast directory can communicate back and forth. So in your case, your Shoutcast server has to be running on the same machine your Cable/DSL connection is running on.

17th January 2001, 02:11	#2
BIGDADDY Senior Member Join Date: Jul 2000 Location: Florida Posts: 497	which nak error is it? the online documentation will explain which codes mean what. IBIG - Relax.

18th January 2001, 06:18	#5
CompuTurk Junior Member Join Date: Jan 2001 Posts: 2	Firewall You either need to forward all port 8000 requests to your internal IP behind the Firewall that starts with 192.168.. or.. probably the best thing to do would be to move your internal IP to DMZ...let all the ports be open. This might slack the security for that specific computer, but move your computer to DMZ... Good luck, -CompuTurk

22nd January 2001, 03:38	#14
djderricke Senior Member Join Date: May 2000 Location: Schaumburg,IL,USA Posts: 194	The problem is that the Shoutcast directory tries to verify that the IP address it is given is actually running a shoutcast server. This is to avoid people from creating bogus redirects to other websites. What I had to do with my internal network was open up port 8002 (I'm using 8002-8003 not 8000-8001) and map it the internal IP address that is running my server. So when you go to my Shoucast server @ 64.7.13.90:8002 (which is actually my router) it is really going to an internal IP address. But since that address is mapped within the router, the shoutcast directory can communicate back and forth. So in your case, your Shoutcast server has to be running on the same machine your Cable/DSL connection is running on. DJ Derrick E. djderricke@djderricke.com www.djderricke.com listen.to/djderricke

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

17th January 2001, 00:53	#1
rosco Junior Member Join Date: Jan 2001 Posts: 10	Hello: I think my ISP is providing me with a IP address that is behind a firewall, I current am getting the "nak" error s when I use the shoutcast DNAS. Is there a quick way to find out? My ISP is sometimes hard to get in touch with. Thanks

17th January 2001, 12:15	#3
RuphBear Member Join Date: Jan 2001 Posts: 68	If you're running behind a firewall, you need to make sure that the ports used by Shoutcast are open, or forwarded to the PC running Shoutcast. I never did get this to quite work behind my firewall, but I'm not a network expert. Ruph

18th January 2001, 00:48	#4
rosco Junior Member Join Date: Jan 2001 Posts: 10	Hello Again .. This is the error I am recieving, I have tried different ports. Still get the same results <01/17/01@17:56:54> [yp_add] yp.shoutcast.com gave error (nak) <01/17/01@17:56:54> [yp_add] yp.shoutcast.com gave extended error (Connection timed out 200.55.127.143:8000 check shoutcast.com troubleshooting)

18th January 2001, 06:20	#6
CompuTurk Junior Member Join Date: Jan 2001 Posts: 2	Also check the following link out, it might be helpful. http://www.shoutcast.com/support/doc...vlayout=normal

18th January 2001, 14:52	#7
Radio CMU San Pablo Junior Member Join Date: Nov 2000 Location: Spain Posts: 40	I'm not sure about what does it mean, it doesn't look like the common port error... Anyway, be sure that, as computurk said the port 8000 isn't being used by other server, like a web page or sth like that, this port is usually open, so if it doesnt work, the most probably reason is that sth is using it (sth like a page being hosted, for example). Anyway, as it doesn lokk like the common port error, u can try to shoutcast using another port (read the ini file in order to know hoe to change the port number) Good luck

18th January 2001, 23:28	#8
rosco Junior Member Join Date: Jan 2001 Posts: 10	Is there a possibility that the IP address that is shown in the error, isn't really the correct IP address. Is there a way to find out what "exactly" what my IP address is Thanks

19th January 2001, 00:00	#9
wedgemusic Senior Member Join Date: Nov 2000 Posts: 176	If you are using Windows, run winipcfg to find out your real IP.

19th January 2001, 00:31	#10
Radio CMU San Pablo Junior Member Join Date: Nov 2000 Location: Spain Posts: 40	Rosco, it depends on whether your LAN uses statics IPs or dinamics IPs, the best is static IPs, but based on my experience I would say, ti doesn't matter, because if u r using dinamic IPs, your server will probabily assign usually the same IPs to each computer. In order to check this, and to now your server and your source IP, u can open the DOS window in windows and type ping name_of_computer where name_of_computer is the name of the machine u want to know IP, the name as appear on your network. Once you type it, it will show u machine's IP. Good luck

19th January 2001, 05:30	#11
kbi Member Join Date: Jan 2001 Location: Poland Posts: 81	hey guys! i've had the same problem with shoutcast. it doesn't depend on firewall settings. the problem is, that shoutcast is unable to connect to the main shoutcast.com server, and it shows something like that. just wait some time, until server will connect. it will believe me

19th January 2001, 21:09	#12
rosco Junior Member Join Date: Jan 2001 Posts: 10	I have had the server running well over 5 hours and got the error about every 5 minutes.

20th January 2001, 18:03	#13
rosco Junior Member Join Date: Jan 2001 Posts: 10	I finally got it to work correctly, (I think) I turned off internet sharing on the computer, and was able to connect without the errors listed above, How can I correct this and still be able to activate internet sharing..