> > If I recall correctly, when I was on AT&T@HOME (as opposed to > AT&T Broadband), the VPN was against the AUP. I ignored them, > and they ignored me. > > It was also against the AUP to run any kind of server, but I > knew of 2-3 people that were running webservers. > > I think the AUP is more a thing that they can fall back on > if they think you are really abusing the service than something > that they actively enforce. > > Mike Burden > Lynk Systems > http://www.lynk.com > (616)532-4985 > [EMAIL PROTECTED]
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]
