MVP please help

Hi,

I have a .NET client / server app developed in C# that uses synchronous TCP
sockets within a Windows 2003 Server Domain. I have 4 cases:

1) Server task runs from Server's desktop, client task runs from any
workstation.

2) Server task runs from Server's desktop, client runs from Server's
desktop.

3) Server task runs from any workstation, client runs from Server's desktop.

4) Server runs from any workstation, client runs from any workstation.

Cases 1, 3, and 4 all work.

Case 2 fails - client returns "No connection could be made because the
target machine actively refused it" message. (WSAECONNREFUSED)

Can anyone suggest why this happens?

Thank you in advance.

Valerie Hough

Furthermore, if I run either the client and the server as different users
from the 2003 Server's desktop, that also works fine. Perhaps this will help
in explaining the issue.

"Valerie Hough" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I have a .NET client / server app developed in C# that uses synchronous
> TCP sockets within a Windows 2003 Server Domain. I have 4 cases:
>
> 1) Server task runs from Server's desktop, client task runs from any
> workstation.
>
> 2) Server task runs from Server's desktop, client runs from Server's
> desktop.
>
> 3) Server task runs from any workstation, client runs from Server's
> desktop.
>
> 4) Server runs from any workstation, client runs from any workstation.
>
> Cases 1, 3, and 4 all work.
>
> Case 2 fails - client returns "No connection could be made because the
> target machine actively refused it" message. (WSAECONNREFUSED)
>
> Can anyone suggest why this happens?
>
> Thank you in advance.
>
> Valerie Hough
>

On 8/12/2005 16:04, Valerie Hough wrote:
> Furthermore, if I run either the client and the server as different users
> from the 2003 Server's desktop, that also works fine. Perhaps this will help
> in explaining the issue.

I have no idea why your system isn't working but as a concerned admin I
would suggest that you make your server application into a proper windows
service rather than requiring a machine to be logged in to run a desktop
app. Furthermore, a windows service can be configured to run under pretty
much any credentials you want (which would probably fix your issue and
enhance application security granularity) and can be scripted and
controlled more easily.

I'm sure your question would be much better answered in a development
newsgroup.

~Jason

--