Hi,Irecently noticed tcpsvcs.exe listening on different TCP ports on my Server 2003Domain Controllers. For example: tasklist | findstr tcpsvcs.exe tcpsvcs.exe 1668 Console 0 6.224 K netstat -ano | findstr 1668 TCP 0.0.0.0:1097 0.0.0.0:0 LISTENING 1668 TCP 192.168.5.10:1096 192.168.5.10:389 CLOSE_WAIT 1668 TCP 192.168.5.10:2476 192.168.5.10:389 CLOSE_WAIT 1668 UDP 127.0.0.1:1095 *:* 1668 UDP 192.168.5.10:67 *:* 1668 UDP 192.168.5.10:68 *:* 1668 UDP 192.168.5.10:2535 *:* 1668 portqry -n 192.168.5.10 -e 1097 -p tcp Querying target system called: 192.168.5.10 Attempting to resolve IP address to a name... IP address resolved to SERVERNAME TCP port 1097 (unknown service): LISTENING TCPSVCS.EXE is DHCP Server service and usesUDP ports 67, 68, 2535 (read that somewhere on microsoft.com).However, as you can see above it is also listening on TCP port 1097. I checked about 5 of my servers, all running DHCP service and everyone has a tcpsvcs.exe listening on a TCP port between 1089 and 1211. During my reasearch I couldn't anything that mentions tcpsvcs.exe is supposed tolistening on dynamic TCP ports between 1000 and 1300.I'm a bit concerned about thissince the networks I am responsible for have a history (usually I should have takem them all down instantly when I started this job :D ) Does anyone know if it is normal that tcpsvcs.exe is listening on dynamic TCP ports?thank youOSJF

Hi, It seems that the port is used for DHCP remote management. On my Windows Server 2003 DHCP server, the tcpsvcs.exe process is listening on dynamic TCP ports as well. You may initial a new thread in the Network Infrastructure Servers forum, which is special for DHCP, DNS, NPS, and RRAS. Network Infrastructure Servers forum http://social.technet.microsoft.com/Forums/en-US/winserverNIS/threads Thanks.