How exactly does ISP port scanning work?
Posted: Fri Apr 01, 2005 10:38 am
Years ago I ran a shoutcast station for myself with some CDs I ripped. It was easy to do that in synchronization with VNC which I use a lot when I'm out and about than to copy all of the mp3 files over to a CD.
My ISP found out and was like, "HARRR!!! WE DON'T ALLOW ANY SUCH HOSTING!!!" Even though I've for years been on the @Work (Business Services, or BS now.) professional system which allows hosting from your location.
Long story short, I had it on port 8888 then 9999. I also ran an HTTP and FTP for myself on that same server, and they shut those down as well because they're retarded.
They never said anything about Q3 ports like 27960. I ran servers for friends and whatnot for a while, and nothing was ever done.
My question is, do they check what's happening or do they just look for the ports in question? If I make my HTTP or Shoutcast run on 27960, should I be fine?
My ISP found out and was like, "HARRR!!! WE DON'T ALLOW ANY SUCH HOSTING!!!" Even though I've for years been on the @Work (Business Services, or BS now.) professional system which allows hosting from your location.
Long story short, I had it on port 8888 then 9999. I also ran an HTTP and FTP for myself on that same server, and they shut those down as well because they're retarded.
They never said anything about Q3 ports like 27960. I ran servers for friends and whatnot for a while, and nothing was ever done.
My question is, do they check what's happening or do they just look for the ports in question? If I make my HTTP or Shoutcast run on 27960, should I be fine?