As it turns out, that wasn't the problem at all... a communications dll location on the client side turned out to be the culprit...(should have been in c:\windows\system and it wasn't) but...