yp.shoutcast.com gave extended error (404 Cannot see your station/computer from the I

[mondobeats]

Hello all,

I've heard read all of the posting on this error message that I am also getting after 2 years of having no problems with shoutcast:

yp.shoutcast.com gave extended error (404 Cannot see your station/computer from the Internet, disable NAT/firewall/ISP cache)

I have 2 machines at home on over DSL.
One is a web server running everything and the other is my workstation running 2 Shoutcast servers.
As of last night, I couldnt get any shoutcast servers running without getting the --- yp.shoutcast.com gave extended error (404 Cannot see your station/computer from the Internet, disable NAT/firewall/ISP cache) error message --

Today, I installed a shoutcast server on my web server machine instead and it runs great. I cant and dont want to run my shoutcast servers on this machine because of resource needs.

Both my machines have their own IP addresses.
Web server - 142.59.196.48
Workstation (shoutcast servers) - 142.59.195.146

My setup is simple, both machines go through a 10MB hub so no problems there. I also disabled both software firewalls on them. Since I was able to successfully run an instance on shoutcast server on my server machine (142.59.196.48), that tells me that perhaps there is a routing or caching problem with my workstation (142.59.195.146). When I initialize shoutcast on the workstation, I can tell it tries to connect to shoutcast yp directories at these addresses - 205.188.234.73,74,and 42. but gives me the -- yp.shoutcast.com gave extended error (404 Cannot see your station/computer from the Internet, disable NAT/firewall/ISP cache) error message. Nonetheless, I tried to connect to it from my server as a client repeatedly and was able once to stream from it even thought I got this error message. I would like this to work eventually.

Here's my take... think that if shoutcast looks at the problem of its client software not being able to touch/list in their directories everyone will be happy. My connection is refused on your end. Since both my machine are on the same DSL link, and that the server can connect as per my test, this proves that it is perhaps a routing/os/directory problem at the shoutcast end.

I am a senior cisco network engineer and network architect and I think that we need to put our heads together to solve the problem.
In lots of the similar posting, it is not a firewall,security,internet,ISP problem but rather a shoutcast or OS problem. please dont bother to tell me if i have my firewall disabled or yp port set to 666 etc... tried it all. Everybody can see my machine from the internet and i can see everything from my machine.... i have not discounted a setting perhaps in windows XP (i am not using ICS/firewall or certificates etc..).

This problem seems to be rampant with lots of user with no proper solution provided yet. i know shoutcast is free but i believe that this is an infrastructure problem on the shoutcast side..maybe im wrong. any suggestions?

regards,

michael

[Tom]

Looks like all incoming requests are being sent to .48. Take a look at whatever you have that allows you to share the connection and make sure port 8000 (TCP) is routed to .146 (assuming you are using a PortBase of 8000).

Tom

[mondobeats]

No shoutcast server instances are running on my webserver machine x.x.x.48.

I have no firewalls, proxy, digital certificates, routers, switches or software security programs at this time for testing purposes. I can access my .146 machine via ftp,sftp,web - port80, and telnet from my office network. only using 10mb hub.

I have an instance of shoutcast with the above mentioned error still running in the hope that it will clear out by perhaps finding a route to the shoutcast directories.

oh well...still working on it...I'll find it.

cheers!

Michael

[mondobeats]

by the way... using the netstat command on .146, I can see that port 8001 is mapped to my IP.

[mkochsch]

Where do you live. I'm in Winnipeg and just started having the same problem beginning last Tuesday.

~m

[mondobeats]

Calgary AB .. just moved here from vancouver. not bad.

www.mondobeats.com

[Tom]

Just reread your post and realized you have two IPs from your ISP so the routing I mentioned above is worthless (in case you haven't noticed yet (usually we get people that are using a NAT and haven't properly forwarded the correct ports)). I know you will probably hate me for this but I just want to verify that you have disabled the firewall that comes standard with WinXP. It is also possible that a slow network could cause this behavior as well, in which case it should clear itself up (but seems odd it would only occur on one of the IPs).

Tom

[mondobeats]

That's right Tom, it is odd. Like I said, 've has no problems in over 2 years and suddenly it misbehaves.

I do not have Microsoft Firewall enabled in Windows XP(nor would I want to do that). I discussed my situation with some friends and members of this forum. Some like myself, were running Shoutcast perfectly until very recently and now they do not have connectivity anymore.

Anyhow, I am looking at hacking the registry in Win XP when I have the chance. Meanwhile if you have any suggestions let me know along with everybody else.

Cheers,

Michael

[mondobeats]

..my DSL connection is soooo fast..great service. not a problem there.

[mkochsch]

What's your subnet mask? I notice the third Octet is different. ie. 196 (server) and 195 (workstation).

~m

Web server - 142.59.196.48
Workstation (shoutcast servers) - 142.59.195.146

[mondobeats]

Web server - 142.59.196.48 - Mask: 255.255.248.0
Workstation (shoutcast servers) - 142.59.195.146 Mask:255.255.248.0

These are not supernetted...

I stopped every conceivable Services in XP also.

Note: I do not have Shoutcast running today since I am working.

[mkochsch]

That's fine then you should be on a network between xxx.xxx.192.xxx and xxx.xxx.199.xxx I believe. What does a trace route back to shoutcast do on each machine? Have you tried flipping the IP addresses between machines? These are Static IP's through Telus right?

~m

Originally posted by mondobeats
Web server - 142.59.196.48 - Mask: 255.255.248.0
Workstation (shoutcast servers) - 142.59.195.146 Mask:255.255.248.0

These are not supernetted...

I stopped every conceivable Services in XP also.

Note: I do not have Shoutcast running today since I am working.

[mkochsch]

And your gateway is the same address right?

~m

[mondobeats]

I'm on a .192 network and gateway is the same on both.

Yes, did that yesterday, tracert to www.shoutcast.com on both machines - same result but (shoutcast does work on Windows 2000 server as per test).

1 27 ms 27 ms 27 ms CLGRAB31AR02.ab.tac.net [209.115.152.21]
2 27 ms 27 ms 27 ms clgrabezdr00.bb.telus.com [209.115.223.167]
3 27 ms 27 ms 27 ms clgrab31br01.bb.telus.com [205.233.111.84]
4 60 ms 61 ms 60 ms chcnil23gr00.bb.telus.com [154.11.10.130]
5 61 ms 61 ms 61 ms chcnil23gr01.bb.telus.com [154.11.11.94]
6 61 ms 61 ms 61 ms chcgildtgr00.bb.telus.com [154.11.11.2]
7 61 ms 62 ms 61 ms pop2-chi-P4-3.atdn.net [66.185.148.73]
8 62 ms 61 ms 61 ms bb2-chi-P0-2.atdn.net [66.185.148.68]
9 81 ms 81 ms 81 ms bb2-vie-P10-0.atdn.net [66.185.153.150]
10 82 ms 81 ms 82 ms bb2-dtc-P8-0.atdn.net [66.185.152.237]
11 82 ms 82 ms 83 ms pop1-dtc-P15-0.atdn.net [66.185.140.10]
12 82 ms 82 ms 82 ms ptne1-dc3-P0-0.atdn.net [66.185.145.190]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.

They have 3 main directory listing for broadcaster (ping -a):
205.188.234.74
205.188.234.73
205.188.234.42

www.shoutcast.com - 205.188.234.88 (cant ping on either one..but thats ok)

My IP addresses are dynamic from Telus. I can statically test them by switching (did that in the past) but my web server is running on x.x.x.48 -- maybe I'll try that later to confirm.

___________________________________________________

"doubt is the enemy of the artist"
--- me

[mondobeats]

One of the thing I was thinking to do yesterday is to acquire a new network card...but perhaps I should disable my web server and flip the IP's statically... and update the MACs in the telus database.
I have DNS hosted but should be ok for a short while.

I still tend to think that the shoutcast directories need to be flushed perhaps... hmmm.. gotta work on this later..right now I have to complete this software due diligence report document for a client.

What do you think?

------------------------------
Linda Emery: A philosophy major? Now, what can
you do with a philosophy major?
Bruce Lee: You can think deep thoughts about
being unemployed.

-Dragon, the Bruce Lee Story

[mondobeats]

..another thing Im thinking it could be related to is HTTP.
thats what shoutcast uses to ad you to their directories.
perhaps i need to reinstall explorer??? ..had no problems with browsing net... its been a while since i troubleshooted microsoft OS.

[mondobeats]

Well well!!!

1- get this... i switched the IPs around and guess what?
my server (win2K)was able to properly connect to the shoutcast directory with the IP that couldnt from my workstation(winXP).

2- gotta be exact.. I installed a new NIC card in the workstation (the one that shoutcast cant read) got a new IP for it and -- DOES NOT WORK.

3- got a new IP (same subnet,mask,network than workstation)assigned to my server and shoutcast still worked.

Conclusion:

Shoutcast is not compatible with Windows XP and/or they have directory policies and network setings that are inadequate to properly served anyone. Cant complain so right? its free...
BUT - its not a firewall/NAT/ISP problem for most.

next? i dont know... I think im gonna go the microsoft/real server way.

Being free and all, Shoutcast is not for serious business or users that require stability. THe ride has been fun but its time to move platform.

cheers.

[mkochsch]

Get a copy of Ethereal and put it on your XP machine and do a capture of the raw packets. You might be able to see where the link is failing. I'd say the evidence is strongly pointing to something on the XP machine (some "security" issue is my guess). Anyway, don't go to Microsoft or Real unless your music stream is a "business" (read: generating money for you) and you need to buy support, this is my advice. As for Using XP, why? You could easily run this on 9x/NT/2000. The key here is not to obsess about the latest and greatest OS from Microsoft, but to have a running system. My W2K Pro setup runs 24X7 for the most part. Once I got is going I didn't touch it (if it ain't broke,,,right?!) Anyhoo. Good luck.

~m

[mkochsch]

How are you connecting to the network. What I'm after here is: you've got a server. Are you authenticating on your local network first? Are you running AD? Is your workstation running in a workgroup? Domain model? Are you logged on as the administrator when you're doing all this? Did you install the SC server while you were the administrator. In my last post I said "security" problem. I mean to clarifiy. NTFS version 2 security. What does your Event Viewer say on your workstation? Any strange error messages popping up? There are three different policy sets (one local and two domain) in W2K and XP. There are as many people in the forum having success and failure with XP. This is leading me to wonder if it's some inherited permission propagating from the initial OS or network install. You're not running any of the CISCO VPN software are you? Just a shot in the dark. I had some of the Cisco VPN software on my machine and screwed up connectivity until I sorted it out. Also, can people who know your IP address connect directly to your XP ShoutCast server?

~m