This is actually by design. Sending on a mailslot goes across all the available protocals installed on the machine. This means if you have both TCP/IP and IPX installed, you'd get two messages. If you peruse the documentaion more carefully you'll see that this is documented. You need to include some kind of ID with the message to you can throw out duplicates. Also note that this protocal does not ensure order of deliverly. Just because msg 1 went out before msg 2 doesn't mean you'll get msg 1 before msg 2. In testing i've found that 99% of the time you'll get them in order, but the documentation say's it this isn't guaranteed. If you need further help, let me know. Joel Lucsy (jjlucsy@concentric.net)