Thanks for your reply Jfer,
We have port 445 'stealth' at the perimiter, would blocking it internally stop some applications / printing from working?
I've checked through the firewall logs and identified a machine internally that was sending across port 445 and also 8-10 Port 139 connections. I've taken that machine off the network and the replication of the worm has stopped according to Sophos.
We're still getting some of the failed login attempts for the non-existant username "bjeiVlak[]Y_bUUbY" on the DC so I guess we're still being attacked by something.
Am I right in assuming the "Root:1" part of the netlogon.log signifies a local attempt at logging on via a share as opposed to attempts on web-facing servers such as OWA?
Most of the alerts we were getting for the executable have been found in system restore partitions so we're globally disabing and then enabling System Restore overnight via GP.
Thanks
Main Topics
Browse All Topics





by: jfer0x01Posted on 2009-10-03 at 08:23:04ID: 25485672
Hi,
ts_port_44 5_in_w2k_x p_2003.htm
Set\ Services\NetBT\Parameters
it's definetly an attack attempt, there are many exploits that attack 445, you need to make sure that the port if actually being blocked, or even better, not used
close 445
http://www.petri.co.il/wha
"
How to disable port 445?
You can easily disable port 445 on your computer. To do so follow these instructions:
Start Registry Editor (Regedit.exe).
Locate the following key in the registry:
HKLM\System\CurrentControl
In the right-hand side of the window find an option called TransportBindName.
Double click that value, and then delete the default value, thus giving it a blank value.
Close the registry editor.
Reboot your computer.
After rebooting open a command prompt and in it type
netstat -an
See that your computer no longer listens to port 445.
"
try viewing logs from network device that feeds workstation internet access for access logs
Only way you are going to find out attacker source
Jfer