Configuring UDPSEND.EXE

Configuring UDPSEND.EXE

The first thing to look at when you start UDPSEND.EXE is the "Your IP" field. If the field is blank, then your Network Interface Card does not have an IP address already assigned to it. Refer to your Windows Help file for information on assigning static IP addresses to your Network Interface Card. Some versions, such as Windows 98 can assign IP addresses. Again, refer to Windows Help.

Once each of your Network Interface Cards on the LAN has an IP address assigned, when you bring up UDPSEND that IP address will automatically be present in the "Your IP" field. However, and this is very important. If IP addresses are assigned by a DHCP server or router acting as a DHCP server, the IP addresses may change each time the PC is rebooted. Always verify correct IP addresses in the "Your IP:" or "Send to:" entries when applicable.

UDPSEND on PC "A" running DXTelnet will be different than PC's "B" and "C".

Since this is the PC that is running DXTelnet, check the box for "Broadcast". This will cause the packet spots to be sent to all PC's on the LAN running UDPSEND. Leave "CT net protocol" unchecked.
Enter the value 9870 in both the "Local port" and "Remote port" fields.

UDPSEND.TXT states to enter a value of 0.0.0.0 in the "Bind address:" field. However, in my own experience, I've always left this field blank. The Bind address is used when a PC has more than one NIC installed. See UDPSEND.TXT for instructions if you have more than one NIC card installed.

When you're finished and any time you make changes to UDPSEND, click on the "Apply" button. Click on NEXT below to see COMMENTS on UDPSEND on PC's "B" & "C".

Installation steps:

1. Locate UDPSEND.EXE on your hard drive and create a shortcut on your Desktop.

2. Run UDPSEND.EXE on PC "A", the PC that will run DXTelnet.

3. Verify an IP address in the "Your IP:" entry box. If no IP Address is specified, you will need to assign a static IP address to your NIC. Refer to Windows Help file.

4. Set UDPSEND parameters as follows:

Send to:               Leave Blank
File exchange:      Check, then hit "OK" button when path windows pops up
Broadcast:           Checked
CT net protocol: Unchecked
Local port:           9870
Remote port:        9870
Bind address:       Leave Blank (If your PC has more than one NIC, refer to UDPSEND.TXT for further instructions.

5. Click on the "Apply" button. Leave the UDPSEND running.

6. Run UDPSEND.EXE on PC's "B" and "C".

7. Verify an IP address in "Your IP:". If none is present, you need to assign a static IP address to your NIC. Refer to Windows Help file.

8. Set UDPSEND paraments as follows:

Send To:              Enter the IP address of PC "A" (or leave blank and check 'Broadcast')
File exchange:      Check, then hit "OK" button when path windows pops up
Broadcast:           Unchecked
CT net protocol: Unchecked (or check if you leave 'Send To' field blank)
Local port:           9870
Remote port:        9870
Bind address:       Leave Blank (If your PC has more than one NIC, refer to UDPSEND.TXT for further instructions.

9. Leave UDPSEND.EXE running on all PC's.

10. Verify proper UDPSEND.EXE by sending test spots back and forth using the "Send test spot" button.

Comments:

Creating a UDPSEND shortcut on each PC's Desktop will facilitate running UDPSEND. You will run UDPSEND and minimize it on each PC during a contest. When you first run UDPSEND, it will look like this.

UDPSEND on PC "A"

When you check the "File exchange" box, a "File Path" window will open as shown below. Just click "OK" and the box will disappear. This links UDPSEND with DXT2WL at it's default location. If you were running DXTelnet on a PC that was NOT running WriteLog, then you could leave this box unchecked. On all PC's that will run WriteLog you need to check "File exchange".

Back to Running DXTELNET over a LAN

Configuring UDPSEND.EXE Page 2