Introduction
We have created a command line tool, UDPChecker, which you can run to check specified UDP ports between 2 clients (Sender and Receiver).
A link to the UDPChecker, the communications flow diagram and a document detailing the ports used can be found at the bottom on this page.
How to use the UDPChecker tool
- Identify 2 clients, one to be the Receiver and one the Sender. If you are checking our broadcast ports, ensure both clients are on the same subnet. To check a WAN connection, you want to select a machine at each location. Ensure you can remote control / command prompt on both of these clients.
- The tool requires .NET 3.5 be installed.
- Download the UDPCheckerLibrary.zip file, and unpack the tool locally on each client (e.g. C:\Temp\UDPChecker)
- On the Receiver, you first need to stop the Adaptiva Client service. Run a Command Prompt with admin rights, and run the following command;
net stop adaptivaclient - Within the same command window, change directory to the location where you unpacked the UDPChecker.exe;
e.g.cd C:\temp\UDPChecker
The UDPChecker.exe must be allowed on the client firewall, if that is used.
Create a firewall rule using the following command from an Administrative command prompt:
Be sure to enter the correct path to the exe.
netsh advfirewall firewall add rule name = "Adaptiva UDP Checker" action=allow dir=in enable=yes profile=domain,private,public protocol=any edge=no program="<path>\UDPChecker.exe"
-
Run the required command to listen on the ports you want to check (in this example, we will check ports 34323 and 34324. For more examples, see the Examples section at the bottom of this article);
e.g. UDPChecker.exe /listenports=34323;34324
You should see a confirmation that the tool is listening on each port specified;
|
Listening for messages on port 34323 |
If you do not receive a confirmation for a port, it means the tool is not able to bind to that port; ensure the AdaptivaClient service is stopped and there are no other applications bound to that port.
- On the sender, run the UDPChecker tool command to send on those same ports, and put the destination as the receiver IP address;
e.g.UDPChecker.exe /directedsendports=34323;34324 /directeddestinations=10.x.x.x
-
The sender will start sending UDP packets on these ports to the client IP specified, you should see below to confirm these are being sent;
Successfully sent [UDPDirectedSent]:[UDP Directed Datagram sent successfully] from [10.60.0.2] to [10.70.0.8] on port [34323]
Successfully sent [UDPDirectedSent]:[UDP Directed Datagram sent successfully] from [10.60.0.2] to [10.70.0.8] on port [34324] - Each port should be listed, if not then that indicates there is a problem sending data on that port from this client.
- Next check on the receiving client that it confirms it has received each datagram sent by the sender. Ensure a received message is listed for each port
[10.70.0.8] received [UDPDirected]:[Directed UDP Message] from [10.60.0.2] on [34323]
[10.70.0.8] received [UDPDirected]:[Directed UDP Message] from [10.60.0.2] on [34323]
[10.70.0.8] received [UDPDirected]:[Directed UDP Message] from [10.60.0.2] on [34323] - In this example above, we have not received the datagrams on port 32324, which indicates the port is blocked on the network or by a local firewall on the client.
- To test connections in the other direction, run the alternate command on the other client so the sender is now receiver, and visa versa.
Examples
To test client to server communication:
Run on the Adaptiva Server (with the AdaptivaClient and AdaptivaServer services stopped):
Validating Client to Adaptiva server ports: 34322;34323;34331;34333;34339;34341
Validating Client to Adaptiva server client ports: 34324;34325;34335;34337;34343;34345;34545;34546
In case you want to validate both Adaptiva Server & Client ports at same time use the below command with the following ports.
UDPChecker.exe /listenports=34322;34323;34331;34333;34339;34341;34324;34325;34335;34337;34343;34345;34545;34546
Make sure all the 14 mentioned ports are listening
Run on the Client:
UDPChecker.exe /directedsendports=34322;34323;34331;34333;34339;34341;34324;34325;34335;34337;34343;34345;34545;34546 /directeddestinations=x.x.x.x
Where x.x.x.x is the IP Address of the Adaptiva Server
The sender will start sending UDP datagrams to Adaptiva Server on all the mentioned ports to the specified Adaptiva Server IP
At the same time, you should see a line for each port on the receiving end (Which is on the Adaptiva Server), if not then that indicates there is a problem sending data on that port from the client. Engage the Network\Firewall team to open those ports that are not listed.
To test server to client communication:
Run on the Client (with the AdaptivaClient service stopped):
UDPChecker.exe /listenports=34324;34325;34335;34337;34343;34345;34750;34546
Include port 34760, if you are validating Adaptiva client communication to the machine in Central Office.
Make sure all the 8 mentioned ports are listening.
Run on the Adaptiva Server:
UDPChecker.exe /directedsendports=34324;34325;34335;34337;34343;34345;34750;34546 /directeddestinations=x.x.x.x
Where x.x.x.x is the IP Address of the Client
The sender will start sending UDP datagrams to Adaptiva Client on all the mentioned ports to the specified Adaptiva Client IP
At the same time, you should see a line for each port on the receiving end (Which is on the Client), if not then that indicates there is a problem sending data on those ports. Engage the Network\Firewall team to open those ports that are not listed.
To test client to client communication:
Run on the Client (with the AdaptivaClient service stopped):
UDPChecker.exe /listenports=34324;34325;34329;34335;34337;34343;34345;34546;34760;34750;34545
Run on another client from the same subnet (with the AdaptivaClient service stopped):
UDPChecker.exe /directedsendports=34324;34325;34329;34335;34337;34343;34345;34546;34760;34750;34545 /directeddestinations=x.x.x.x
The sender will start sending UDP datagrams to Adaptiva Client on all the mentioned ports to the specified Adaptiva Client IP
At the same time, you should see a line for each port on the receiving end (Which is on the Client), if not then that indicates there is a problem sending data on those ports. Engage the Network\Firewall team to open those ports that are not listed.
To test client to client communication for PXE:
Run on the Client (with the AdaptivaClient service stopped):
UDPChecker.exe /listenports=67;68;69;4011
Run on another client from the same subnet (with the AdaptivaClient service stopped):
UDPChecker.exe /directedsendports=67;68;69;4011 /directeddestinations=x.x.x.x