Discussion:
Cannot Authenticate using TcpClientChannel to a workgroup Server
(too old to reply)
dgcooper
2008-07-03 17:36:07 UTC
Permalink
I am able to connect to a remote TcpServerChannel from a Workgroup PC to a
Domain Server using the domain name in the credientials. However, I cannot
connect a Domain PC to a Workgroup Server. I used the Workgroup Server's
name as the domain name but it does not work.

What should I use as the domain name for a Domain TcpClientChannel
connecting to a TcpServerChannel in a Workgroup?
Jeff Winn
2008-07-04 04:52:36 UTC
Permalink
More than likely there is a configuration on your server preventing it from
authenticating to machines outside the domain. I have the same problem using
my work laptop to connect to my home PC.

Might want to check with your system administrators.
Post by dgcooper
I am able to connect to a remote TcpServerChannel from a Workgroup PC to a
Domain Server using the domain name in the credientials. However, I cannot
connect a Domain PC to a Workgroup Server. I used the Workgroup Server's
name as the domain name but it does not work.
What should I use as the domain name for a Domain TcpClientChannel
connecting to a TcpServerChannel in a Workgroup?
dgcooper
2008-07-07 16:55:02 UTC
Permalink
I found the problem, I needed to disable Simple File Sharing on the Server
Machine

Thanks for your help
Post by Jeff Winn
More than likely there is a configuration on your server preventing it from
authenticating to machines outside the domain. I have the same problem using
my work laptop to connect to my home PC.
Might want to check with your system administrators.
Post by dgcooper
I am able to connect to a remote TcpServerChannel from a Workgroup PC to a
Domain Server using the domain name in the credientials. However, I cannot
connect a Domain PC to a Workgroup Server. I used the Workgroup Server's
name as the domain name but it does not work.
What should I use as the domain name for a Domain TcpClientChannel
connecting to a TcpServerChannel in a Workgroup?
Loading...