Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
So they do! Live and learn. The two go hand-in-hand, of course. The
novice setting up a webserver is likely to be infected via code red rather
quickly, although that scenario differs from their stated intent of blocking
"high volume web servers.
"Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message
news:%23GAaEkUpEHA.3252@TK2MSFTNGP14.phx.gbl...
> Cox HSI, my provider, gives the reason for blocking TCP Port 80 as both,
> ie. no personal web servers are allowed and worm protection...This is for
> purely residential service...
>
>
http://usercenter.cox.net/rsuite/sdcuser/default.jsp
>
> --
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual
> benefit of all of us...
> The MS-MVP Program -
http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no
> rights...
>
> "Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
> news:%23QUpRwOpEHA.2340@TK2MSFTNGP11.phx.gbl...
>> FWIW, the block of port 80 isn't to prevent running servers, it is
>> because of the Code Red worm which is still alive and well out there,
>> more than three years after its first appearance.
>>
>> I shouldn't make a blanket statement for all ISP's, but this is Verizon's
>> stated reason, and I believe them.
>>
>>
>> "Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message
>> news:%23jiceAKpEHA.2588@TK2MSFTNGP12.phx.gbl...
>>> If you connect using the regular RD client, ie. not the web based
>>> method, from a remote site does that work? If so, its possible your ISP
>>> is blocking TCP Port 80 (IIS). Many ISP block that because running
>>> personal web servers is a violation of the terms of agreement. You might
>>> contact your ISP to find out for sure...
>>>
>>> If the connection, from a remote site, using the regular RD client does
>>> not work, then run this telnet test to see if you can pinpoint the
>>> problem.
>>>
>>>
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628
>>>
>>> Note that if your trying to do this from work its also possible they
>>> block TCP Port 3389 outbound...
>>>
>>> --
>>> Al Jarvi (MS-MVP Windows Networking)
>>>
>>> Please post *ALL* questions and replies to the news group for the mutual
>>> benefit of all of us...
>>> The MS-MVP Program -
http://mvp.support.microsoft.com
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights...
>>>
>>> "NJTucker" <jose_ocampo@email.com> wrote in message
>>> news:b51f3d16.0409270633.66dc7f69@posting.google.com...
>>>> Okay this is what i've done so far. I followed the many numerous
>>>> posts and guides and installed the web connection software. I've
>>>> opened up the appropriate ports and forwarded them, ie ports 80 and
>>>> 3389. My local remote deskop connection works fine, but i can't get
>>>> web connection to work. When i type in
http://ipaddress
ort/tsweb I
>>>> get page cannot be displayed. I've gone to whatismyip.com to find my
>>>> ip and made sure my router is forwarding it to the appropriate lan ip
>>>> address.
>>>>
>>>> What am i missing?
>>>
>>
>>
>
Facebook
Twitter
Instagram