>The software is designed as a stand-alone. And something like 98%+ of the machines/networks we put it on though don't have problems.
>
>I guess I don't see where I can test it since our application never even starts when we have this problem. Clicking on the icon does nothing. Unless the system has been booted without being plugged into the network..then it works fine. Rebooting with the cabling attached..nothing. And since it works on most NT networks, rather than not working on them, it isn't something conflicting with the generic NT systems..:(

Are the affected computers part of a "managed" network, i.e. one that makes use of Microsoft SMS, Intel LANDesk, etc.? These packages are capable of controlling and modifying the environment of workstation PCs. It is conceivable that "management" settings might be affecting how your app works, and that disabling the remote management (the hard way, by unplugging the cable) might work around that. Not much more that a SWAG, though.