Whoa..! Yikes...!  Argghh...!!  All suddenly becomes clear!

In article ,
Dennis Lee Bieber   wrote:
>
> I would suspect you have a firewall/proxy problem on your network
>end...

Not exactly that... (:-/)

>
>md_admin@microdiversity:~$ wget -O BBC2.mp3
>http://bbcmedia.ic.llnwd.net/stream/bbcmedia_radio2_mf_p
>--2019-05-26 19:29:20--
>http://bbcmedia.ic.llnwd.net/stream/bbcmedia_radio2_mf_p
>Resolving bbcmedia.ic.llnwd.net (bbcmedia.ic.llnwd.net)... 208.111.170.251,
>208.111.170.250
>Connecting to bbcmedia.ic.llnwd.net
>(bbcmedia.ic.llnwd.net)|208.111.170.251|:80... connected.
     This is what *you* get ^^^^^^

But if I do, say, "dig bbcmedia.ic.llnwd.net", *I* see "69.164.29.xx"!!

It's a CDN, and I'm connected to a different server! ("..llnw.." is
"Limelight Networks")

I replaced the hostname with the IP you connect to, and I'm back listening
to R2!  (Dunno if I should try to complain to Limelight, or just live with
the working hack...)

>
> What does traceroute do for you?
As one would expect it traces through to the same IP as dig shows.
I'm curious, though:
> [....]
> 1  dsldevice.attlocal.net (192.168.1.254)  0.832 ms  0.911 ms  1.014 ms
               ^^^^^^^^^^^^
... sounds like AT&T.  Are you in the US, too?  Where?  Why are you being
served, and I'm not?

Thanks for providing the clue!

 -- Pete --

--- SoupGate-Win32 v1.05