Cable Forum
Page 2 of 5 1 2 345
Show 100 post(s) from this thread on one page

Cable Forum (https://www.cableforum.uk/board/index.php)
-   Virgin Media Internet Service (https://www.cableforum.uk/board/forumdisplay.php?f=12)
-   -   NTL to block port 135 (https://www.cableforum.uk/board/showthread.php?t=3427)

Chris 16-10-2003 11:26
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.

Nemesis 16-10-2003 11:29
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 ?

garyeuph 16-10-2003 11:35
Re: NTL to block port 135
 
I presume the effect on exchange would not apply if you connect over a vpn tunnel??

Shaun 16-10-2003 11:57
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. :rolleyes:
Check out the 4 hotfixes in windows update yesterday :rolleyes:

Tiptoes 16-10-2003 11:59
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."

Shaun 16-10-2003 12:00
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 ;)

Chris 16-10-2003 12:05
Re: NTL to block port 135
 
Quote:
Originally Posted by dellwear
Check out the 4 hotfixes in windows update yesterday :rolleyes:
Well, don't you know it ... I'm a prophet as well ... ;)

Tiptoes 16-10-2003 12:20
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 16-10-2003 12:24
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 ;)
?

homealone 16-10-2003 12:31
Re: NTL to block port 135
 
Quote:
Originally Posted by dellwear
Check out the 4 hotfixes in windows update yesterday :rolleyes:

*cough* post #12 *cough* :D

Shaun 16-10-2003 12:36
Re: NTL to block port 135
 
Quote:
Originally Posted by homealone
*cough* post #12 *cough* :D

Sorry Gaz :o

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


I'll get my coat! :dmonk:

homealone 16-10-2003 12:52
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.

altis 16-10-2003 13:13
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

garyeuph 16-10-2003 14:02
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!

Alan Waddington 16-10-2003 17:45
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.


All times are GMT. The time now is 14:43.
Page 2 of 5 1 2 345
Show 100 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum