Forum Articles
  Welcome back Join CF
You are here You are here: Home | Forum | NTL to block port 135

You are currently viewing our boards as a guest which gives you limited access to view most of the discussions, articles and other free features. By joining our Virgin Media community you will have full access to all discussions, be able to view and post threads, communicate privately with other members (PM), respond to polls, upload your own images/photos, and access many other special features. Registration is fast, simple and absolutely free so please join our community today.


Welcome to Cable Forum
Go Back   Cable Forum > Virgin Media Services > Virgin Media Internet Service
Reload this Page NTL to block port 135
Register FAQ Community Calendar

NTL to block port 135
Reply
Page 2 of 5 1 2 345
 
Thread Tools
Old 16-10-2003, 12:26   #16
Chris
Trollsplatter
Cable Forum Team
 
Chris's Avatar
 
Join Date: Jun 2003
Location: North of Watford
Services: Humane elimination of all common Internet pests
Posts: 38,596
Chris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden aura
Chris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden aura
Re: NTL to block port 135
Quote:
Originally Posted by Tiptoes
So all those home wokers connecting to their works Exhange server for their email are buggered.
sounds like it. ntl strikes again.
Chris is offline   Reply With Quote
Advertisement
Old 16-10-2003, 12:29   #17
Nemesis
Inactive
 
Join Date: Jun 2003
Location: Surrey
Age: 59
Services: Virgin stuff
Posts: 6,407
Nemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny star
Nemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny starNemesis has a nice shiny star
Send a message via MSN to Nemesis
Re: NTL to block port 135
Quote:
Originally Posted by Tiptoes
So all those home wokers connecting to their works Exhange server for their email are buggered.
Can the Exchange servers be configured to use another port ?
Nemesis is offline   Reply With Quote
Old 16-10-2003, 12:35   #18
garyeuph
Inactive
 
garyeuph's Avatar
 
Join Date: Jun 2003
Posts: 31
garyeuph is an unknown quantity at this point
Re: NTL to block port 135
I presume the effect on exchange would not apply if you connect over a vpn tunnel??
garyeuph is offline   Reply With Quote
Old 16-10-2003, 12:57   #19
Shaun
Inactive
 
Join Date: Jun 2003
Posts: 6,064
Shaun has a nice shiny starShaun has a nice shiny star
Shaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny star
Re: NTL to block port 135
Quote:
Originally Posted by towny
For sure they will, for such is the way of virus writers ... and such is the way of M$, that it prolly won't take long to find the next exploit.
Check out the 4 hotfixes in windows update yesterday
Shaun is offline   Reply With Quote
Old 16-10-2003, 12:59   #20
Tiptoes
Inactive
 
Tiptoes's Avatar
 
Join Date: Sep 2003
Location: Ask not what your country can do for you but what a mess we could have made of your country
Posts: 250
Tiptoes is an unknown quantity at this point
Re: NTL to block port 135
Quote:
Originally Posted by garyeuph
I presume the effect on exchange would not apply if you connect over a vpn tunnel??
AS long as the VPN is set up to use TCP/IP and remember that
VPN isnt "allowed" on residential NTL Services.

Read their AUP.


Also Windows 2K servers on which Exchange server sits needs RPC (Port 135) to function properly so although it can be protected it can t be actually "Closed".

http://www.microsoft.com/technet/sec...n/MS00-066.asp

"Would it be possible to prevent the attack by disabling the RPC service?

It is not practical to disable the RPC service on a Windows 2000 server. RPC is an integral part of the Operating System and many services will not function with RPC disabled."
Tiptoes is offline   Reply With Quote
Old 16-10-2003, 13:00   #21
Shaun
Inactive
 
Join Date: Jun 2003
Posts: 6,064
Shaun has a nice shiny starShaun has a nice shiny star
Shaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny star
Re: NTL to block port 135
Quote:
Originally Posted by garyeuph
I presume the effect on exchange would not apply if you connect over a vpn tunnel??
Shouldn't think so, because your running the software there and not on your machine
Shaun is offline   Reply With Quote
Old 16-10-2003, 13:05   #22
Chris
Trollsplatter
Cable Forum Team
 
Chris's Avatar
 
Join Date: Jun 2003
Location: North of Watford
Services: Humane elimination of all common Internet pests
Posts: 38,596
Chris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden aura
Chris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden auraChris has a golden aura
Re: NTL to block port 135
Quote:
Originally Posted by dellwear
Check out the 4 hotfixes in windows update yesterday
Well, don't you know it ... I'm a prophet as well ...
Chris is offline   Reply With Quote
Old 16-10-2003, 13:20   #23
Tiptoes
Inactive
 
Tiptoes's Avatar
 
Join Date: Sep 2003
Location: Ask not what your country can do for you but what a mess we could have made of your country
Posts: 250
Tiptoes is an unknown quantity at this point
Re: NTL to block port 135
Quote:
Originally Posted by Nemesis
Can the Exchange servers be configured to use another port ?

yes Outlook Web Access (OWA ) on port 80


http://servername/exchange/mailboxname.


but its dodgy.....

(Port 80 connections into your server via a home user)

I would recommend any look at Exchange on W2K seriously consider these

http://www.securityfocus.com/infocus/1572

http://www.securityfocus.com/infocus/1578
Tiptoes is offline   Reply With Quote
Old 16-10-2003, 13:24   #24
Tiptoes
Inactive
 
Tiptoes's Avatar
 
Join Date: Sep 2003
Location: Ask not what your country can do for you but what a mess we could have made of your country
Posts: 250
Tiptoes is an unknown quantity at this point
Re: NTL to block port 135
Quote:
Originally Posted by dellwear
Shouldn't think so, because your running the software there and now on your machine
?
Tiptoes is offline   Reply With Quote
Old 16-10-2003, 13:31   #25
homealone
Guest
 
Posts: n/a
Re: NTL to block port 135
Quote:
Originally Posted by dellwear
Check out the 4 hotfixes in windows update yesterday

*cough* post #12 *cough*
  Reply With Quote
Old 16-10-2003, 13:36   #26
Shaun
Inactive
 
Join Date: Jun 2003
Posts: 6,064
Shaun has a nice shiny starShaun has a nice shiny star
Shaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny starShaun has a nice shiny star
Re: NTL to block port 135
Quote:
Originally Posted by homealone
*cough* post #12 *cough*

Sorry Gaz :o

Tiptoes, I've edited my post so it makes sense now


I'll get my coat!
Shaun is offline   Reply With Quote
Old 16-10-2003, 13:52   #27
homealone
Guest
 
Posts: n/a
Re: NTL to block port 135
Quote:
Originally Posted by dellwear
Sorry Gaz :o

<snip>
np - it's these laminate floors, they make everything echo

It'll be interesting to have a look at my router log when I get home to see how much difference this port blocking has made.
  Reply With Quote
Old 16-10-2003, 14:13   #28
altis
Inactive
 
altis's Avatar
 
Join Date: Jun 2003
Location: Warrington ntl:81304 Altitude: 12m (and falling)
Posts: 4,499
altis has a nice shiny staraltis has a nice shiny star
altis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny staraltis has a nice shiny star
Re: NTL to block port 135
Bugga all so far!
Quote:
Thu, 16 Oct 2003 13:57:50 GMT+0100 Unrecognized access from 81.97.150.191:4035 to TCP port 135
Thu, 16 Oct 2003 13:57:56 GMT+0100 Unrecognized access from 81.97.217.203:3622 to TCP port 135
Thu, 16 Oct 2003 13:58:02 GMT+0100 Unrecognized access from 81.100.109.208:3958 to TCP port 135
Thu, 16 Oct 2003 13:58:04 GMT+0100 Unrecognized access from 81.99.224.104:1681 to TCP port 135
Thu, 16 Oct 2003 13:58:05 GMT+0100 Unrecognized access from 81.100.109.208:3958 to TCP port 135
Thu, 16 Oct 2003 13:58:28 GMT+0100 Unrecognized access from 80.131.136.230:1025 to UDP port 137
Thu, 16 Oct 2003 14:00:19 GMT+0100 Unrecognized access from 81.96.103.92:3651 to TCP port 135
Thu, 16 Oct 2003 14:00:53 GMT+0100 Unrecognized access from 81.98.39.240:3118 to TCP port 135
Thu, 16 Oct 2003 14:00:56 GMT+0100 Unrecognized access from 81.98.39.240:3118 to TCP port 135
Thu, 16 Oct 2003 14:01:02 GMT+0100 Unrecognized access from 81.98.39.240:3118 to TCP port 135
Thu, 16 Oct 2003 14:01:12 GMT+0100 Unrecognized access from 81.97.83.164:3412 to TCP port 445
Thu, 16 Oct 2003 14:01:15 GMT+0100 Unrecognized access from 81.97.83.164:3412 to TCP port 445
Thu, 16 Oct 2003 14:01:39 GMT+0100 Unrecognized access from 81.97.107.242:3600 to TCP port 135
Thu, 16 Oct 2003 14:02:09 GMT+0100 Unrecognized access from 81.97.14.176:3735 to TCP port 135
Thu, 16 Oct 2003 14:02:12 GMT+0100 Unrecognized access from 81.97.14.176:3735 to TCP port 135
Thu, 16 Oct 2003 14:02:17 GMT+0100 Unrecognized access from 81.97.14.176:3735 to TCP port 135
Thu, 16 Oct 2003 14:03:09 GMT+0100 Unrecognized access from 200.154.72.12:1025 to UDP port 137
Thu, 16 Oct 2003 14:03:52 GMT+0100 Unrecognized access from 81.97.166.133:4032 to TCP port 135
Thu, 16 Oct 2003 14:03:54 GMT+0100 Unrecognized access from 81.97.166.133:4032 to TCP port 135
Thu, 16 Oct 2003 14:03:55 GMT+0100 Unrecognized access from 81.99.222.41:3736 to TCP port 135
Thu, 16 Oct 2003 14:03:58 GMT+0100 Unrecognized access from 81.99.222.41:3736 to TCP port 135
Thu, 16 Oct 2003 14:04:00 GMT+0100 Unrecognized access from 81.97.166.133:4032 to TCP port 135
Thu, 16 Oct 2003 14:04:04 GMT+0100 Unrecognized access from 81.99.222.41:3736 to TCP port 135
Thu, 16 Oct 2003 14:04:43 GMT+0100 Unrecognized access from 200.182.64.181:1033 to UDP port 137
Thu, 16 Oct 2003 14:05:03 GMT+0100 Unrecognized access from 81.97.127.244:4056 to TCP port 135
Thu, 16 Oct 2003 14:05:06 GMT+0100 Unrecognized access from 81.97.127.244:4056 to TCP port 135
Thu, 16 Oct 2003 14:05:12 GMT+0100 Unrecognized access from 81.97.127.244:4056 to TCP port 135
Thu, 16 Oct 2003 14:05:38 GMT+0100 Unrecognized access from 81.97.62.18:3779 to TCP port 135
Thu, 16 Oct 2003 14:05:41 GMT+0100 Unrecognized access from 81.97.62.18:3779 to TCP port 135
Thu, 16 Oct 2003 14:05:46 GMT+0100 Unrecognized access from 81.97.62.18:3779 to TCP port 135
Thu, 16 Oct 2003 14:06:39 GMT+0100 Unrecognized access from 81.99.24.179:3121 to TCP port 135
Thu, 16 Oct 2003 14:06:42 GMT+0100 Unrecognized access from 81.99.24.179:3121 to TCP port 135
Thu, 16 Oct 2003 14:06:48 GMT+0100 Unrecognized access from 81.99.24.179:3121 to TCP port 135
Thu, 16 Oct 2003 14:07:06 GMT+0100 Unrecognized access from 81.99.5.121:1265 to TCP port 135
Thu, 16 Oct 2003 14:07:09 GMT+0100 Unrecognized access from 81.99.5.121:1265 to TCP port 135
Thu, 16 Oct 2003 14:07:15 GMT+0100 Unrecognized access from 81.99.5.121:1265 to TCP port 135
Thu, 16 Oct 2003 14:07:53 GMT+0100 Unrecognized access from 81.97.103.221:3415 to TCP port 135
Thu, 16 Oct 2003 14:07:55 GMT+0100 Unrecognized access from 81.97.103.221:3415 to TCP port 135
Thu, 16 Oct 2003 14:08:01 GMT+0100 Unrecognized access from 81.97.103.221:3415 to TCP port 135
Thu, 16 Oct 2003 14:08:50 GMT+0100 Unrecognized access from 81.100.153.1:20051 to TCP port 135
Thu, 16 Oct 2003 14:08:54 GMT+0100 Unrecognized access from 81.100.153.1:20051 to TCP port 135
Thu, 16 Oct 2003 14:09:00 GMT+0100 Unrecognized access from 81.100.153.1:20051 to TCP port 135
Thu, 16 Oct 2003 14:10:05 GMT+0100 Unrecognized access from 81.97.189.91:4123 to TCP port 135
Thu, 16 Oct 2003 14:10:08 GMT+0100 Unrecognized access from 81.97.189.91:4123 to TCP port 135
Thu, 16 Oct 2003 14:10:14 GMT+0100 Unrecognized access from 81.97.189.91:4123 to TCP port 135
Thu, 16 Oct 2003 14:12:13 GMT+0100 Unrecognized access from 81.98.100.108:4905 to TCP port 135
altis is offline   Reply With Quote
Old 16-10-2003, 15:02   #29
garyeuph
Inactive
 
garyeuph's Avatar
 
Join Date: Jun 2003
Posts: 31
garyeuph is an unknown quantity at this point
Re: NTL to block port 135
Quote:
Originally Posted by Tiptoes
AS long as the VPN is set up to use TCP/IP and remember that
VPN isnt "allowed" on residential NTL Services.

Read their AUP.


Also Windows 2K servers on which Exchange server sits needs RPC (Port 135) to function properly so although it can be protected it can t be actually "Closed".

http://www.microsoft.com/technet/sec...n/MS00-066.asp

"Would it be possible to prevent the attack by disabling the RPC service?

It is not practical to disable the RPC service on a Windows 2000 server. RPC is an integral part of the Operating System and many services will not function with RPC disabled."
THE AUP does allow VPN, they just do not support it!
garyeuph is offline   Reply With Quote
Old 16-10-2003, 18:45   #30
Alan Waddington
Inactive
 
Alan Waddington's Avatar
 
Join Date: Jun 2003
Location: Farnham
Posts: 503
Alan Waddington has a spectacular aura about themAlan Waddington has a spectacular aura about themAlan Waddington has a spectacular aura about themAlan Waddington has a spectacular aura about them
Re: NTL to block port 135
I can't access my pipex dialup mailbox no more...

But it turns out that pipex's mailservers are borked, so it's not due to NTL blocking 135. I didn't think it would be, but it gave me a bad moment.
Alan Waddington is offline   Reply With Quote
Reply
Page 2 of 5 1 2 345

« Previous Thread | Next Thread »

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 19:06.

Contact Us - Service Status - Cable Forum - Archive - Privacy Statement - Terms of Service - Top

Server: lithium.zmnt.uk
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum
Copyright © 2026 Cable Forum Hosted On Hetzner Cloud