hello,

i have a remote object in a windows service (local system) that client
computers connect to (or create? do clients create a server object or
do they connect to a server object? or both? well, anyways...)
everything works fine if the user is logged on the client machine with
an account that is in the domain and he uses the same password as when
logged in to the domain.

but when a user is not in the domain the client cannot create the
remote object. also when a user is in the domain but has logged on to
his machine locally with another password as the one he uses in the
domain the server blocks the user account after several unsuccessful
attempts to connect to the remote object.

now i don't know who is responsible for all this authentication issue.
is it the windows service or the remote object server?
and how can i control the way users/client are authenticated when
connecting to the remote object?
can i configure the windows service or the remote object server so
that it always accepts requests even if the user client is not
authenticated in the domain?

any help would be greatly appreciated!

regards,
simon m.