Just in case someone has to deal with Telus using Windows Server (I believe samba may also uses these ports but in perhaps a sane way, but clients refuse at this moment for me to move them to such a thing), I have some notes.
I am dealing with an oil company app that sends it's data over port 445 (Yes. yes. I asked why...They're going to re-write it...It was originally for LAN use only...) and I was experiencing some problems like time-outs, etc. After dealing with app's tech guy, he informs me "oh yeah, and telus started blocking those ports too." Luckily, they're on a static business line, which doesn't get affected by such things. So the problem actually was elsewhere...But it took me a couple hours of dealing with 'that infernal voice menu system' and line techs to isolate if WE had messed up somewhere (the company and the app's company) or if it was Telus' block doing something wonky. Bad telus. You forgot to fill out your TPS report -AND- send me a memo! So if your heart is set on using Telus and you feel like running some stuff that might be blocked, their static business line doesn't appear to be blocking anything at all. Personally, I am very glad to give my money to Shaw instead. --Scott _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
