Our company has a small domain with a web server and a Sql Server database 
server and a small work group for the office staff.  The development machine, 
with two NICs, is a member of the workgroup but accesses the domain 
routinely.  I have developed a client-server app that connects to the SQL 
Server database.  It runs without problem on the development machine and on 
all machines in the domain; but trying to run the development machine's 
assembly remotely from the workgroup poses numerous security errors not 
(apparently) resolvable through .Net Config.  Since the work group machines 
don't have visibility to the Sql Server, using the development machine as the 
server seemed a likely alternative; but now I'm beginning to wonder if it can 
be made to work.  Does anyone have any thoughts or experience on how to 
configure this?
Thanks for any help.

-- 
Sincerely,
Tom Corcoran