The most common reason why DinkeyNet does not work properly is because it has not been setup correctly. Please check the following points:

1. The DinkeyNet Path specified in DDNet does not match the DinkeyNet Path specified in the <prodcode.ini> file.
2. If you are running DDNet as a service then the DinkeyNet Path must be local to the machine running DDNet. You can not use mapped drives or UNC pathnames in refering to this drive (can you do this in the <prodcode.ini> file.
3. Your protected program will look in the Windows directory and your program directory to find the ini file. Maybe it is finding the file you are not intending it to find.
4. Your protected program and DDNet must have create, read, write and delete access rights to the DinkeyNet Path and its subdirectories. If you are running DDNet under Mac or Linux then all users (and DDNet) must be in the same group.

You can also look up the errors you protected program is giving in the Error Numbers section.

DDNet will write warnings and error codes to the ddnet.log file if it is running as a program or the event log (application log) if it is running as a service.