Sounds like you need put on your network management hat or get your network support folks involved. Have them look at netstat and maybe use the procexp.exe utility from <a href=”http://live.sysinternals.com”>Sysinternals/Microsoft</a> to see if it can track down the open connections and narrow it down to a workstation. If they are unable to track it to a workstation, then you may need to open a support case with Microsoft.
For more ideas check out a couple of my blog entries:
<a href=”http://itknowledgeexchange.techtarget.com/it-trenches/nifty-tools-for-tracking-down-that-interesting-network-traffic/”>Nifty tools for tracking down that “interesting” network traffic</a> – You can ignore the first half of this as it talks about Cisco routers. It’s the last half that might be of interest in tracking down IP connections and processes talking to those connections.
<a href=”http://itknowledgeexchange.techtarget.com/it-trenches/did-you-see-this-process-monitor-now-does-tcpudp-monitoring/”>Did you see this? – Process monitor now does TCP/UDP monitoring</a>
In the IT trenches? So am I – read my <a href=”http://itknowledgeexchange.techtarget.com/it-trenches”>IT-Trenches blog</a>