Running the Samples in a Workgroup and Across Machines

A number of issues relating to security may arise when running the Windows Communication Foundation (WCF) samples on machines that are not part of a domain but are part of a workgroup and when the samples are run across machines.

Common Problems

The following table describes some of the common problems that arise when running the WCF samples across machines and how to resolve these problems.

Problem	Solution
Windows security does not work across machines when the client is running with the credentials of a local user account (MACHINE\user or Administrator).	Ensure that local user account exists on the service machine. The user account must have the same password on both machines, and the password must not be blank.
Both the service and client are running on machines that are part of a domain, but Windows security does not work across machines.	Ensure that both the client and service are running on machines that are part of the same domain so that the client can logon to the service with its domain user account.
Default settings in the local security policy prevent samples from running across machines. Client fails to logon to service.	Modify the local security policy (Security Settings\Local Policies\Security Options) as follows: Set the Guest account status to Enabled. Ensure that the sharing and security model for local accounts is not set to Guest only - local users authenticate as guests, but are set to Classic - local users authenticate as themselves.
Accessing a service file (.svc) using Internet Explorer fails.	Modify the firewall to enable the machine that is hosting the service to access the network. See Firewall Instructions.

Send comments about this topic to Microsoft.
© Microsoft Corporation. All rights reserved.