SQL Server with port 1027 open but no IIS

Does anyone know know why a SQL Server would open the IIS port? I don't even have IIS installed.

TIA

80 is the IIS port. SQL Server can be set to listen on any port. After a connection has been made it may instruct the client to move to another open port to free up its main port for other incoming requests. This last bit is speculation.

80 is the port that serves up content, but it isn't the only port IIS uses. AD probably uses 4 or five ports all by iteself.

If you have an M$ web server on your network, and perhaps even a SQL server, do a port scan on it, and the scanner will identify 1027 as being open, and that it belongs to IIS. It will determine that based on a simple lookup of a table the port scanner has internal to itself, so basically that means you can trust the open closed portion of the test, but as to what owns the port is best guess... hence why I am wondering.

Ok, you're right. Sorry. I just ran netstat from MS-DOS. My IIS is listening on 1027. You don't think SQL does the same thing? I've got a few instances MSDE installed on this machine... I might shut down IIS and see what they listen on... or, I might just go to bed.

By the way, the only way I have found to map a port to the process using it is to use the free Sygate Personal Firewall. That's all I ever use that thing for, never liked it as a firewall. Just fire it up once in a while to see what DLL is using a mystery port. Let me know if you have another method.

Hey, cool idea. Actually, I have no idea how to do this in Windows. It's a breeze in linux, but I've been tearing my hair out on the win side.

Do me a favor... shutdown your IIS and see if it's still there. Meanwhile, I'll go find that package and see what I come up with.

I shutdown IIS and no more port 1027... I shutdown taskscheduler and no more port 1025. All that's left is TCP ports 135,139,445,1026,3002,3003,3004 on a networked W2k desktop with minimal services.

Powered up MSDE and some other incarnation of SQL Server and now I got 1433 and 2272 open.

Not sure what we learned here, but I do have something cool to add. Evidently there is newer, cooler freeware out now.

These guys offer a command line tool that lists open udp and tcp ports by process in a netstat format.

http://www.diamondcs.com.au/openpor...p?page=download

They also have some other usefull stuff that I have seen elsewhere like a utility that lists auto starts and a utility that monitors your registry for changes.

openports is EXACTLY what I was looking for!

Thanks much!

On my machine, the msdtc has that port open, and I suspect it's because my dba has his sql boxes talking back and forth.

I did find documentation that says both IIS and SQL use msdtc.