For many developers, iBursts dumb policy of blocking port 1433 is a complete showstopper and makes it completely pointless for me to use iBurst. I've just gone down to Cape Town with only an iBurst modem for connectivity to my client's systems. Imagine my horror to discover that I couldn't access any of their SQL servers because iBurst's nanny mentality has decided that since hackers sometimes use port 1433 for hacking, therefore they'll just block it. Well, hackers also use port 80 - why don't they block that as well, morons??
I don't want a service provider that decides for me which ports to allow. If I am dumb enough to put an unsecured sql server onto the internet then it is my responsibility, not iBurst's. And, no, I'm not prepared to reconfigure 48 SQL servers just to accomodate a hostile port blocking policy from one service provider. So, bye bye iBurst - and good riddance.
I don't want a service provider that decides for me which ports to allow. If I am dumb enough to put an unsecured sql server onto the internet then it is my responsibility, not iBurst's. And, no, I'm not prepared to reconfigure 48 SQL servers just to accomodate a hostile port blocking policy from one service provider. So, bye bye iBurst - and good riddance.