A year or so ago after signing up for the local telco ADSL service I discovered I couldn't get any server to operate. After some tests and investigation, I concluded that inbound was blocked on many if not all ports. The telco's response to an email that related my findings confirmed this to be the case. I've since dropped the telco service and am now with one of the smaller ISP's who's interest is much more service oriented than with just collecting the money.
At 09:36 AM 2/25/2002 -0700, Wes Stewart wrote: >I have the feeling that these "new" ISP's are going to be more active in >port blocking. I've already experienced a odd form of this. Where I live >in Mesa I had no problem checking my email on the company's Exchange server. >Exchange uses three ports: 135 and two random numbers in the 1000 range. My >boss in Scottsdale after the switch to Cox could no longer connect to the >server. I hard coded the two random number in Exchange to the 2000 range >and he was once again able to connect to the server. I've heard of inbound >port blocking such as port 80 for webservers, but never outbound port >blocking. That is how they could possibly control the VPN issue. > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >To subscribe to the digest version first unsubscribe, then > e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] To subscribe to the digest version first unsubscribe, then e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
