That must be a change from when I used it. SQL Express 2005 used to listen on that port - I haven't worked with anything newer.
Interesting. Kurt On Sun, Mar 28, 2010 at 12:05, Phil Brutsche <[email protected]> wrote: > Not necessarily. > > Does the Windows Internal Database listen for TCP/IP connections? I know > for a fact that a default install of SQL Express doesn't. > > IMO portscanning for TCP ports 8530 and 80, then subtracting the known > web servers, is one of the better ways of finding a rogue WSUS server. > > On 3/28/2010 1:00 PM, Kurt Buff wrote: >> Uh, I thought you said you didn't have access to the network. >> >> A portscan for port 1433 would probably have been equally as good, or >> perhaps better. > > -- > > Phil Brutsche > [email protected] > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
