Firewall, Port Forwarding, Still Invisible

mweiss · 29th October 2002, 07:58

I have spent many hours reading all the threads pertaining to the

<10/29/02@03:32:12> [yp_add] yp.shoutcast.com gave extended error (Cannot see your station/computer (IP: 24.151.85.138:8000) from the Internet, disable NAT/firewall/ISP cache (Connection timed out))
<10/29/02@03:37:22> [yp_add] yp.shoutcast.com gave error (nak)

message in Shoutcast server monitor.

I have determined that my Linksys BEFW11S4 router is the problem, because I connected my PC directly to the WAN port of the cable modem and started up WinAMP's connection and got a status message that I was added to the Shoutcast web page, followed by a series of messages that my server had been 'touched' several times in 1 minute, followed by several connection messages. I don't get those messages when I run via the router.

For some reason, forwarding ports 8000-8001 to my computer's internal IP address does not work, although every bit of documentation I could find indicates that this is the correct procedure.

My next step was to try setting up a DMZ for just the Shoutcast computer. That did not work either.

I'm not convinced that port forwarding is working properly on the Linksys router. Has anyone successfully gotten Shoutcast to work on this model and make of router?

baytime88 · 29th October 2002, 11:41

Are you sure you're forwarding the ports to the correct internal IP? if you're using DHCP, maybe the router is assigning your computer a new IP that the ports aren't forwarded to. Also, if you are running a server on your internal LAN, you only need to forward port 8000.

mweiss · 29th October 2002, 18:40

My router is set up for DHCP, but even when I use IPCONFIG/ALL to view my current IP address and configure the router to forward all port 8000 calls to that address, Shoutcast still cannot find my computer on the net.

It works nicely if I plug the computer directly into the cable modem.

I forwarded 8000-8001 to the IP address of the shoutcast server. I figure that should cover it.

But, I also tried setting up a DMZ for the shoutcast PC and STILL it is invisible to the internet.

I am beginning to wonder if this is even possible to do from behind a router.

[see attached screen shot]

mweiss · 30th October 2002, 04:07

Okay, I just read the thread:

http://forums.winamp.com/showthread.php?threadid=77606
"SHOUTCasting through a Linksys Cable/DSL Router for Dummies "

And I realized I was still using DHCP. So I revamped things and I disabled DHCP, enabled the port forwarding for 8000 and 8001 ports, added the specific DNS information from the Status menu of router, and so on. Everything by the book.

This did not correct the problem.

I also tried setting up DMZ for the shoutcast PC again, this time to its specific assigned IP address, as shown in IPCONFIG. No change.

The only thing that I managed to accomplish was to kill all PC's on the network ability to access newsgroup servers.

Just for a reality check, I bypassed the router again, physically, and ran the computer directly into the SB4200 cable modem. I restarted the DNAS and started the encoder and got right into the yp within seconds.

My Linksys router firmware is 1.42.7 --did anyone get this version to work with shoutcast? It looks like something is wrong with this router--it's not REALLY creating a DMZ. No matter what the setting is, the computers are still all invisible.

Given that the modem has a USB port, I wonder if I can use the Ethernet port to connect it to the router and the rest of the LAN, but use the USB port to connect to one dedicated Shoutcast server? Since the router won't let any PC directly access the outside world, perhaps if I can set up a parallel connection to the modem. Has anyone done this with success?

Jay · 30th October 2002, 04:22

Can you open a connection to the server using your outside IP address?

mweiss · 31st October 2002, 02:10

I have done that testing using the outside IP address, but it only works one a PC from INSIDE the LAN. If I try it from a dialup account the address times out or is not found.

Jay · 31st October 2002, 02:16

your ISP could be blocking ports

if by going to your outside IP address in your lan gets you to the server and going to your outside IP address through another connection does not then something outside of your lan is blocking.

mweiss · 31st October 2002, 23:14

I am not under the impression that my ISP is blocking ports because I am able to get listed in the yellow pages when I run the server without the router. I get the appropriate response back from the server when I connect the PC directly to the cable modem . The problems begin when I put the router back into the system . If I didn't need a LAN , then I could webcast without the router. unfortunately this is not the case.

GR1F73R · 8th November 2002, 00:39

I am using a linsys 4 port router (befsr41 model) and I also cannot get shoutcast to work correctly with it. I must have read every forums that has to do with this topic, but nothing seems to work. What really pisses me off is that IT USED TO WORK. Now that I have installed shoutcast server again, it doesnt and I am upset!

mweiss · 8th November 2002, 01:01

I have the exact same router as you do and I never got it to work with Shoutcast. I have tried disabling DHCP and assigning a gateway and IP addresses to the PCs involved, in conjuction with setting up the Shoutcast PC in the DMZ of the router, but not even that drastic measure allowed the Shoutcast PC to be visible to the internet.
For now, I've just given up on it. Not much point when you've only got 128K uplink speeds which can serve decent audio to just one listener, so I've taken to prerecording my shows and placing them on my station's server.

GR1F73R · 8th November 2002, 17:08

Well, I got mine working

I didn't really do anything different expect I disabled DHCP server BEFORE putting on the filters.. Last time it was the other way around, and it didn't work. I don't know if this is the reason it's working now... but it is!

mweiss · 9th November 2002, 07:30

Okay that is a good clue...

What else did you need to do to make this work? Did you have to assign static IP addresses to the server where Shoutcast is located? If one disables DHCP, then it is quite involved as far as setting up each PC to access the internet. What else needs to be done to make it all work?

kardi412 · 16th February 2003, 16:09

that was all it took; disabling it that order is what it took I am now on the yellow pages

mweiss · 18th February 2003, 22:33

I solved this some months ago by updating the firmware on the router. Port forwarding works properly now.

30th October 2002, 04:22	#5
Jay Moderator Alumni Join Date: May 2000 Location: Next Door Posts: 8,942	Can you open a connection to the server using your outside IP address? -Jay \| Radio Toolbox.com

31st October 2002, 02:16	#7
Jay Moderator Alumni Join Date: May 2000 Location: Next Door Posts: 8,942	your ISP could be blocking ports if by going to your outside IP address in your lan gets you to the server and going to your outside IP address through another connection does not then something outside of your lan is blocking. -Jay \| Radio Toolbox.com

8th November 2002, 00:39	#9
GR1F73R Junior Member Join Date: Jun 2002 Location: Waynesboro, PA Posts: 2	same problem I am using a linsys 4 port router (befsr41 model) and I also cannot get shoutcast to work correctly with it. I must have read every forums that has to do with this topic, but nothing seems to work. What really pisses me off is that IT USED TO WORK. Now that I have installed shoutcast server again, it doesnt and I am upset!

8th November 2002, 17:08	#11
GR1F73R Junior Member Join Date: Jun 2002 Location: Waynesboro, PA Posts: 2	Success! Well, I got mine working I didn't really do anything different expect I disabled DHCP server BEFORE putting on the filters.. Last time it was the other way around, and it didn't work. I don't know if this is the reason it's working now... but it is!

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

29th October 2002, 11:41	#2
baytime88 Junior Member Join Date: Jun 2002 Location: Tampa, FL, USA Posts: 4	Are you sure you're forwarding the ports to the correct internal IP? if you're using DHCP, maybe the router is assigning your computer a new IP that the ports aren't forwarded to. Also, if you are running a server on your internal LAN, you only need to forward port 8000.

30th October 2002, 04:07	#4
mweiss Member Join Date: Oct 2002 Location: Connecticut Posts: 55	Okay, I just read the thread: http://forums.winamp.com/showthread.php?threadid=77606 "SHOUTCasting through a Linksys Cable/DSL Router for Dummies " And I realized I was still using DHCP. So I revamped things and I disabled DHCP, enabled the port forwarding for 8000 and 8001 ports, added the specific DNS information from the Status menu of router, and so on. Everything by the book. This did not correct the problem. I also tried setting up DMZ for the shoutcast PC again, this time to its specific assigned IP address, as shown in IPCONFIG. No change. The only thing that I managed to accomplish was to kill all PC's on the network ability to access newsgroup servers. Just for a reality check, I bypassed the router again, physically, and ran the computer directly into the SB4200 cable modem. I restarted the DNAS and started the encoder and got right into the yp within seconds. My Linksys router firmware is 1.42.7 --did anyone get this version to work with shoutcast? It looks like something is wrong with this router--it's not REALLY creating a DMZ. No matter what the setting is, the computers are still all invisible. Given that the modem has a USB port, I wonder if I can use the Ethernet port to connect it to the router and the rest of the LAN, but use the USB port to connect to one dedicated Shoutcast server? Since the router won't let any PC directly access the outside world, perhaps if I can set up a parallel connection to the modem. Has anyone done this with success?

31st October 2002, 02:10	#6
mweiss Member Join Date: Oct 2002 Location: Connecticut Posts: 55	I have done that testing using the outside IP address, but it only works one a PC from INSIDE the LAN. If I try it from a dialup account the address times out or is not found.

31st October 2002, 23:14	#8
mweiss Member Join Date: Oct 2002 Location: Connecticut Posts: 55	I am not under the impression that my ISP is blocking ports because I am able to get listed in the yellow pages when I run the server without the router. I get the appropriate response back from the server when I connect the PC directly to the cable modem . The problems begin when I put the router back into the system . If I didn't need a LAN , then I could webcast without the router. unfortunately this is not the case.

8th November 2002, 01:01	#10
mweiss Member Join Date: Oct 2002 Location: Connecticut Posts: 55	I have the exact same router as you do and I never got it to work with Shoutcast. I have tried disabling DHCP and assigning a gateway and IP addresses to the PCs involved, in conjuction with setting up the Shoutcast PC in the DMZ of the router, but not even that drastic measure allowed the Shoutcast PC to be visible to the internet. For now, I've just given up on it. Not much point when you've only got 128K uplink speeds which can serve decent audio to just one listener, so I've taken to prerecording my shows and placing them on my station's server.

9th November 2002, 07:30	#12
mweiss Member Join Date: Oct 2002 Location: Connecticut Posts: 55	Okay that is a good clue... What else did you need to do to make this work? Did you have to assign static IP addresses to the server where Shoutcast is located? If one disables DHCP, then it is quite involved as far as setting up each PC to access the internet. What else needs to be done to make it all work?

16th February 2003, 16:09	#13
kardi412 Junior Member Join Date: Feb 2003 Posts: 6	that was all it took; disabling it that order is what it took I am now on the yellow pages

18th February 2003, 22:33	#14
mweiss Member Join Date: Oct 2002 Location: Connecticut Posts: 55	I solved this some months ago by updating the firmware on the router. Port forwarding works properly now.