UDP instead of TCP
How do you implement UDP transport protocol, instead of TCP, on a windows 2000 network?
I know what the difference is between TCP and UDP, but I have never seen UDP implemented. I am just curious how you install or implement UDP.
Windows Forum
How do you implement UDP transport protocol, instead of TCP, on a windows 2000 network?
I know what the difference is between TCP and UDP, but I have never seen UDP implemented. I am just curious how you install or implement UDP.
by joseph moore
You don't implement UDP in the way you are suggesting. Applications/services hold open ports, and if the port is a TCP port or UDP port just depends on how the application is written.
For example, Windows does a lot of its talking over NerBIOS (even in Win2K NetBIOS is used). File and Print Sharing is over NetBIOS on a default setup. Now, TCP port 139 is the file and printer sharing port that the default NetBIOS uses, but it is not the ONLY port that is used.
UDP port 137 is the NetBIOS Nameserver port. This port is used when your Windows box does a name lookup of a remote Windows box when you try and connect to a remote machine to access a shared folder or printer.
You can also type in 'NBTSTAT -A IP_ADDRESS' to use UDP to get the NetBIOS name cache of a remote system (replace IP_ADDRESS with the IP of a remote system to see what I mean).
Also, do 'NETSTAT -AN' on your Windows box to see what UDP ports your system currently is listening on.
Also, I believe that anytime you talk to a remote time server (using Network Time Protocol) that it is talking UDP.
There are many other examples.
The whole point of this is that you ALREADY have UDP enabled. If you are talking IP, then TCP & UDP are both 2 different connection methods at your disposal.
hope this helps
by northwood
by food537
by northwood
by northwood
This discussion is closed to new replies.
Sort by Trending