View Full Version : internet radio


spuriousmonkey
01-14-06, 02:18 PM
Every time I try to play internet radio it fails to do so (asx url).

Now I downloaded windows media player 10 and behold, it played internet radio immediately after installing. I then close WMP and open it again. And guess what. Same old problem. Can't play internet radio, although I am quite sure that it can since I saw it with my own eyes once.

Does anyone have a solution. I did the obvious that the help file suggested with is check network settings and set it to autodetect proxy.

Fafnir665
01-14-06, 02:44 PM
What version of windows? Try using a port 80 stream. That worked for me when i was having a similar problem..

spuriousmonkey
01-14-06, 02:49 PM
where would I find this option?

windows xp sp2, mediaplayer 10

Mr Anonymous
01-14-06, 07:32 PM
When you open up in full mode, next to close, minimise, etc, there's a tiny down arrow - select Tools>Options and choose the Network Tab. Tick the Use Port box and it enables you to maually set the port you want to use.

spuriousmonkey
01-15-06, 04:25 PM
Well, I was hoping there was another port option somewhere because I tried changing that one.
:(

I don't understand why it worked when i just downloaded and installed it. And after closing and opening the application it didn't anymore as before. I didn't even restart.

Something must be wrong on some kind of level.

Could it be a problem with the cable internet provider? For some strange reason.

spuriousmonkey
01-15-06, 04:44 PM
My freedom loving american provider is blocking half the ports known in existence i think

25 TCP SMTP Both* SMTP Relays
80 TCP HTTP Inbound Web servers, worms
135 UDP NetBios Both Net Send Spam/Pop-ups, Worms
136-139 UDP, TCP NetBios Both Worms, Network Neighborhood
445 TCP MS-DS/ NetBios Both Worms, Network Neighhood
1433 TCP MS-SQL Inbound Worms, Trojans
1434 UDP MS-SQL Inbound Worms, SQLslammer
1900 UDP MS-DS/ NetBios Both Worms, Network Neighborhood
27374 TCP Subseven Both SubSeven Trojan

Any alternatives? I guess 80 won't work.

Mr Anonymous
01-15-06, 06:23 PM
Mmmmm.... Firewall settings, perhaps?

In either event, uninstall the bugger and then reinstall, pay scrupulous attention to what transpires. Y'know the thing works so something else along the way is just being puckish with you're privates. See if you can spot what.

Blue_UK
01-15-06, 06:48 PM
Have you tried another cilent, such as Winamp?

spuriousmonkey
01-15-06, 06:53 PM
Winamp gives the same results, so I think it is the cable company. I had similar problems when I first tried to send a spuriousmonkey email NOT with webemail. Took me forever to realize that the bastards had just blocked the email port to prevent spam (that is what they say).

I'm reading now the fineprint and apparently unlimited internet access is defined by them as having access to the internet at all hours, not use the internet as much as you like. So I wouldn't think it is strange they would block internet radio. And apparently they do block port 80 as can be seen from the table in previous post.

So anyone know an alternative port? The support of the cable company is american. That means that an answer is usually given a week after a question. And then it usually is the automatic reply.

I'm still waiting for a username and pass to use their mail server, which they promised me more than a week ago. I send them an email reminding them of that fact and indeed after 2 days I received an automatic reply email that my email had been received.

Bloody fast service they have.

Kunax
01-16-06, 01:30 AM
winamp + www.shoutcast.com, for music anyway

edit.: althou there are some talk channels between the 10000+ servers listed

Blue_UK
01-16-06, 06:10 AM
So anyone know an alternative port?You can use any port number greater than 1024 and less than something like 50,000 so long as it's no already in use. Less than 1024 are reserved. I very much doubt something like 20,000 is in use.

I expect your provider is only blocking incoming port 80 requests - i.e. proventing you from hosting your own web server. Whereas you are clearly able to send requests to port 80.