Werbung: SecurityConsole.de verwaltet Ihre Computer mit Security Essentails aus der Cloud!
30 Tage kostenfrei testen und 20% Rabatt für Ihre Bestellung mit Promocode: WBF2685582
(Promocode gültig bis 31.12.2011)

Group:  English: Windows Server » microsoft.public.windows.server.networking
Thread: identify file copy during the network

HTVi
TV Discussion Newsgroups

identify file copy during the network
"NT" <nt29[ at ]community.nospam> 12/17/2008 5:29:21 PM
hello
is it possible to identify/specify a port TCP/UDP for a file transfert
between workstations and servers

because i must give a list of ports using in my network to my provider to
organize a qos
He could only filter on udp/tpc ports

thanks,
nicolas

RE: identify file copy during the network
v-dashen[ at ]online.microsoft.com (David Shen [MSFT]) 12/18/2008 2:51:30 AM
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

Re: identify file copy during the network
"NT" <nt29[ at ]community.nospam> 12/18/2008 1:06:01 PM
thanks, your link is very important

i conitnue my researchs


"David Shen [MSFT]" <v-dashen[ at ]online.microsoft.com> a écrit dans le message
de news:TWEyHuLYJHA.2052[ at ]TK2MSFTNGHUB02.phx.gbl...
[Quoted Text]
> 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
>

Re: identify file copy during the network
"Phillip Windell" <philwindell[ at ]hotmail.com> 12/18/2008 3:15:10 PM
There is no logical reason that your provider should have any relevance to
file transfers between machines on your LAN.

With TCP/UDP, the only relevant port is the destination port,...the client
source port is always [or usually] random and there is no way to make any
QoS decisions based on it.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------



"NT" <nt29[ at ]community.nospam> wrote in message
news:E5771837-08C0-495E-866F-B110522709E2[ at ]microsoft.com...
[Quoted Text]
> hello
> is it possible to identify/specify a port TCP/UDP for a file transfert
> between workstations and servers
>
> because i must give a list of ports using in my network to my provider to
> organize a qos
> He could only filter on udp/tpc ports
>
> thanks,
> nicolas


RE: identify file copy during the network
v-dashen[ at ]online.microsoft.com (David Shen [MSFT]) 12/19/2008 6:53:57 AM
Hi Nicolas,

I am glad that the information is helpful for you. If you have any other
question, please welcome to our newsgroup again.

David Shen
Microsoft Online Technical Support

Re: identify file copy during the network
"Juergen Kluth" <jkluth-newskonto[ at ]dokom.net> 12/19/2008 3:28:42 PM
Hi,
are there any differences with usage of "direct hosting", so if NO NetBT is
involved.

regards jk


Re: identify file copy during the network
v-dashen[ at ]online.microsoft.com (David Shen [MSFT]) 12/25/2008 9:47:59 AM
Hi,

According to the research, Direct hosted "NetBIOS-less" SMB traffic also
uses port 445 (TCP and UDP).

For more information, please refer to:

Direct hosting of SMB over TCP/IP
http://support.microsoft.com/kb/204279

Hope it helps.

David Shen
Microsoft Online Technical Support

Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net
Suche nach Orten, Städten, Postleitzahlen, Vorwahlen, Kfz-Kennzeichen