> Hi Nicolas,
>
> According to the research, there is a way to identify a port TCP/UDP for a
> file transfer between workstations and servers. We can use network monitor
> 3.2 to capture the network traffic between the two computers during the
> copy operation.
>
> Download: Microsoft Network Monitor 3.2
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=f4db40af-1e08-4a21-> a26b-ec2f4dc4190d&DisplayLang=en
>
> 1. Enable the Capture Filter "IPv4.Address == <IP of the client>" and
> start
> capture.
> 2. Restart one of clients to reproduce the issue.
> 3. Stop capture and save to *.cap file.
> 4. In the area of Frame Summary, you may find the SrcPort (Source port)
> and
> DstPort (Destination port) in column of "Description" to identify the port
> number that is used by copy operation.
>
> For more detailed steps, please refer to:
>
> How to use Network Monitor to capture network traffic
>
http://support.microsoft.com/kb/812953>
> Generally speaking, the file copy operation between Windows uses SMB
> protocol. For about the ports information about SMB, please refer to the
> following the KB article.
>
> Service overview and network port requirements for the Windows Server
> system
>
http://support.microsoft.com/default.aspx?scid=kb;EN-US;832017>
> Hope it helps.
>
> David Shen
> Microsoft Online Technical Support
>