Hi, i wonder does anybody knows why exchange use a tcp 1349 when communicating with clients (outlook 2003, 2007 and 2010). When i run netstat I get: TCP exc1-production:1349 192.168.54.18:1140 ESTABLISHED TCP exc1-production:1349 LSTTA-LU:49178 ESTABLISHED TCP exc1-production:1349 LETT6:1133 ESTABLISHED TCP exc1-production:1349 LETT1:1050 ESTABLISHED TCP exc1-production:1349 LETT5:1074 ESTABLISHED TCP exc1-production:1349 LETT3:1142 ESTABLISHED I looked in exchange well known ports and it is not listed in exchange 2003 documentations. We use a Symantec endpoint protection 12.1 and there is no virus and malware on the server or clients so i can exclude that option. Regards

On Tue, 6 Sep 2011 06:25:34 +0000, Dofa wrote: > > >Hi, i wonder does anybody knows why exchange use a tcp 1349 when communicating with clients (outlook 2003, 2007 and 2010). When i run netstat I get: > >TCP exc1-production:1349 192.168.54.18:1140 ESTABLISHED TCP exc1-production:1349 LSTTA-LU:49178 ESTABLISHED TCP exc1-production:1349 LETT6:1133 ESTABLISHED TCP exc1-production:1349 LETT1:1050 ESTABLISHED TCP exc1-production:1349 LETT5:1074 ESTABLISHED TCP exc1-production:1349 LETT3:1142 ESTABLISHED > > > > I looked in exchange well known ports and it is not listed in exchange 2003 documentations. We use a Symantec endpoint protection 12.1 and there is no virus and malware on the server or clients so i can exclude that option. Use "portquery" to see what ports are used by which services: http://support.microsoft.com/kb/310298 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

TCPView is another very usful tool. Just start ít and check which process/programm is using the port http://technet.microsoft.com/en-us/sysinternals/bb897437?ppud=4 Right-click the process in the left column, choose properties and see the full path to the .exe file Regards Eduard