.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Net.TCP Endpoint; Windows Authentication security; client can connect to a server at localhost but n

Posted By:      Posted Date: October 15, 2010    Points: 0   Category :WCF

Hey all, so here's what going on:

I have a WCF Service that I have setup as a Windows Service.  Everything works perfectly when I attempt to use the system with all of the components (i.e. server and clients) on the same machine.  However, when I try to connect my client from a different system, I get an error that is trying to tell me that the server rejected the client's credentials.

I need the client to the able to connect from a different machine.  I want to implement a SQL Role Provider kind of credentialing in the future, but for now, I just need it to work.

What I have tried
I have looked around online and read a few other posts as well some things in the MSDN KB and I have either not found the answer, or not understood it.

  • I have tried setting the <security mode="Transport"> to "None" with the hope that that would disable the accreditation entirely.  All it did was result in a different error saying that there was an error that might have been caused by an invalid message.  I have also tried a few other configurations with this element in the app.config file; to no success.
  • I have read some things about Impersonation, but I am not quite sure I understand how to implement it

    View Complete Post

More Related Resource Links

SOS: Cannot connect to SQL Server 2005 locally by Windows Authentication DOMAIN \ myname. But networ

Cannot connect to SQL Server 2005 locally by Windows Authentication DOMAIN \ myname. But network connection is successful.   But SQL Server Logins contain   BUILTIN \ Administrators, and                                                    BUILTIN \  Administrators contain DOMAIN \ Domain Admins, and                                                    DOMAIN \ Domain Admins contain DOMAIN \ myname.   Creating SQL Server Login with DOMAIN \ myname entail successful local connection.   Removing SQL Server Login with DOMAIN \ myname and creating SQL Server Login with DOMAIN \ Domain Admins do NOT entail successful connection. Cannot connect! System:   Windows Server 2008. Error 18456

Cannot connect to SQL Server 2005 locally by Windows Authentication, but network connection is succe

Cannot connect to SQL Server 2005 locally by Windows Authentication DOMAIN \ myname. But network connection is successful.   But SQL Server Logins contain   BUILTIN \ Administrators, and                                                    BUILTIN \  Administrators contain DOMAIN \ Domain Admins, and                                                    DOMAIN \ Domain Admins contain DOMAIN \ myname.   Creating SQL Server Login with DOMAIN \ myname entail successful local connection.   Removing SQL Server Login with DOMAIN \ myname and creating SQL Server Login with DOMAIN \ Domain Admins do NOT entail successful connection. Cannot connect!                                     &

Cannot connect to local server with windows authentication


When I try to connect to my local server using windows authentication I get the following error:

Login failed for user 'Will-PC\Will'. (Microsoft SQL Server, Error: 18456)


It happens if I try to give the server name as WILL-PC, (local), localhost, or "."

I am on Windows 7, and I am using SQL Server 2005 Standard edition, the and SQL Server service is running.  I can't get into the server in any way to see what users are available.  Please help!

How to connect to a different SQL server by using Windows Authentication?


Hi all

Version: SQL Server 2008 R2

When I use my SQL Server Mgt Studio -> Connect... Database Engine... then click on Authentication: Windows Authentication, my username is gray out and it grabs my current domain\username. I need to type a different Domain\Username.

How do I do that if the field is grayed out?

Thank  you


Client can't connect to WCF on deployment machine Windows 2003 Sp2 server .NET 3.5



I have a WCF service hosted in a Windows service application.  I have a Windows Form client that connects to it.  I am using net.tcp binding for two endpoints.   It all works fine in my environment, but when I deploy it on my cutomer's machine the client does not get a response from the service.

I ran netstat -na and I can see the endpoints listening.  I can even see the connection ESTABLISHED when my client runs the first method.  But my client times out and receives a "Could not communicate with XXX service.  This request operation sent to net.tcp..... did not receive a reply within the configured timeout (00.01.00) The time alloted... etc"

I tried removing all security from the configuration file, but that did not make a difference.

I reinstalled .NET Framework 3.5

I added     System.Net.ServicePointManager.DefaultConnectionLimit = 200 as suggested in another post.

I am creating a trace for the client and the server.  The server does not log any activity of a connection.  The client is catching a communication exception.

Any insight would be greatly appreciated.  What else can I try to see why the client is not able to chake hands with the server on this particular machine?

Many thanks,



Windows Server 2003: Discover Improved System Info, New Kernel, Debugging, Security, and UI APIs


There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003

Security Briefs: Exploring S4U Kerberos Extensions in Windows Server 2003


Building Web sites that provide services external to the corporate firewall is tricky. Usually it's not desirable to grant corporate domain accounts to external clients, and from a purely practical standpoint Kerberos does not work well over the Internet due to the typical configuration of client-side firewalls.

Keith Brown

MSDN Magazine April 2003

Web Security: Part 2: Introducing the Web Application Manager, Client Authentication Options, and Pr


This article, the second of two parts, continues coverage of Web security for Windows. It introduces the Web Application Manager in IIS that allows Web processes to be isolated, decreasing the security risk associated with running in a logon session. The article then picks up where Part One left off-it discusses authentication methods such as basic authentication, digest authentication, integrated Windows authentication, and anonymous logons, and the benefits and drawbacks of each.

Keith Brown

MSDN Magazine July 2000

WCF Client (netTcpBinding) does not connect to remote DNS on Vista and Windows 7

Hi, WCF Client (netTcpBinding) does not connect to remote DNS on Vista and Windows 7. With other OS like XP and Windows 2003, client connects to remote DNS properly. I got the following exception. Same client works in Vista and Windows 7 if service is available in local network. Following are the exceptions: <Exception> <ExceptionType>System.ServiceModel.EndpointNotFoundException, System.ServiceModel, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType> <Message>No DNS entries exist for host icelive.theice.com.</Message> <StackTrace> at System.ServiceModel.Channels.DnsCache.Resolve(String hostName) at System.ServiceModel.Channels.SocketConnectionInitiator.GetIPAddresses(Uri uri) at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.TracingConnectionInitiator.Connect(Uri uri, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.Comm

Unable to connect to SQL Server 2005 remotly, all client protocols are blank

I have an installation of SQL 2005 and had issues connecting remotly. Looking at the client protocolols, they are all blank. I can see that TCPIP, Named Pipes, VIA, etc. are 'enabled', but where the words 'TCPIP', 'Names Pipes', etc. should be, it's just blank. I tried to install SQL 2008R hoping the Client Protocols would be corrected during the installaion, but they were not. I'm assuming the issue with the Client Protocols not showing up is a symptom of the problem. Does anyone have any ideas? Thanks!

How to impersonate a connection to SQL server under IIS app pool account if Windows Authentication i

I have a requirement I should connect to MS SQL server under IIS Application pool account from ASP.NET application where Windows Authentication is enabled. I cannot use user name and password in connection string. ASP.NET application should use Entity Framework 4.0 to work with data. Any ideas how to do it?    

net.tcp://localhost:80/MyService client/server errors while IIS is running - even though all Net.TCP

Hello, I am trying to create a simple WCF client/server solution in two Windows Forms projects, respectively.  I am using net.tcp binding on port 80 and have enabled the port sharing property.  My NET.TCP Port Sharing service is running.  I am using Windows 7 x64 and logged in as an administrator.  I've added my username to the smvchost configuration files, in both Framework and Framework 64 directories. I also have IIS running on port 80. However, there seems to be a conflict between net.tcp on port 80 and IIS on port 80 simultaneously.  My understanding was that the Net.TCP Port Sharing is supposed to be the solution for this very scenario. Here are the specific issues: 1.  I start the server in debug mode, which works fine.  I then try to connect with the client, and get the error: "You have tried to create a channel to a service that does not support .Net Framing.  It is possible that you are encountering an HTTP endpoint".  This seems to imply that the NET.TCP Port Sharing is not forwarding the request to my WCF server, and instead is encountering IIS.  This is the first problem. 2.  The second issue is that the Server starts fine in Visual Studio in debug mode, however when I try to run it as a compiled EXE (and right-click - run as admin) it errors "The TransportMana

SQL server client tool installation on windows XP?

Hi My desktop is Windows XP sp3 and have office 2010, sql express 2005 management studio and Visual studeio 2008 sp1 installed.  We have a SQL R2 server installed last week.  I was able to use sql 2005 management studio to connect to the new sql 2008 R2.  Question is when i try to install 2008 R2's client tool using the 2008R2 iso image.  It look for windows installer 4.5 as prerequisite.  It fail in installing windows installer 4.5 with msg saying I am not the administrator and it require administrator right.  But I am logging in as administrator on local pc.  I also confirmed with our IT/Server guys and they confirmed that I have the admin right.  Then, I tried the following steps: a) reboot, log in as administrator locally b) checked eventviewer, no error/warning msg that stand out to me c) turn off symantec antivirus d) download windows installer 4.5 (WindowsXP-KB942288-v3-x86.exe   - install it locally   - run as administrator to install All the above steps seems not working, I am kind of out of idea.  Could some on please kindly help out.  All I need is the 2008 management studio and profiler install on my PC.  thank you, Ted.  

Security settings for this service require Windows Authentication but it is not enabled for the IIS

Hosting service in IIS 5.1   Config is set to transport layer security. SSL is installed and configured on the virtual folder and BasicHTTP bidings are being used for connection. Authentication in web.config is set to Windows Authorization in web.config is set to Deny Users="?" and Allow Users="*"   When trying to connect to the service using IE, it throws exception that "Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service. "   Can some one tell me what is missing?   Do I have to set anything in Web.Config?   I need to achieve following using Basic HTTP binding   Transport Layer security (SSL), Windows Domain Authentication, Use  user's Domain identity to impersonate the user in service   Please suggest the settings if any   Thanks

Migration of DSN use for SQL Server access from Windows SP-3 clients to Windows 7 64 bit client

We have numerous apps which use a named DSN using SQLSRV32.dll for an ODBC connection from our Windows XP-Pro SP3 32 bit machines client access to remote windows 2003 based SQL servers (mix of 2005 and 2008).  On migrating to Windows 7, this dll will not allow the apps to use the newly constructed DSN (using SQLSRV32.dll with ODBC), even though a test connection is sucessful (abbeit much slower than seen on the XP-Pro machines).  What must I use on the Windows 7 64 bit machine to allow a DSN to be used by the migrated apps?  - I have descerned through Google that WDAC is now the tool to use, but I am cluless how to use it. - The expectations from the app on the Windows XP-Pro and on the Windows 7 64 bit machines is to use a DSN to connect to SQL servers on Windows 2003. I would appreciate any advice, and thanks!

ODBC connection to SQL Server 2005 Standard (on windows xp) with Windows authentication does NOT wor

I reviewed lots of postings, still could not find an answer. If I choose Windows authentication: - with TCP/IP and "Dynamically determine port" checked, I get the following error "The user is not associated with a trusted SQL Server connection; - with Named Pipes, Server Name & Pipe Name as "VSAXAONG", I get two errors, one after the other on the same pop-up:       Connection failed  SQL State 01000  SQL Server Error 1385 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] ConnectionOpen (Connect()).       Connection failed  SQL State 08001 SQL Server Error 17 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] SQL Server does not exist or access denied. If I choose SQL Server authentication and fill in the password - the ODBC connection works fine. I have to say that I created two different logins on the server, one for Windows authentication, and one for SQL Server authentication - both for the same Windows user name. I would appreciate any help I can get on this.  Thank you all in advance.

Using Windows Authentication for connecting sql server from web application using froms authenticati

Hi Experts, I have one web application which is configured to be use froms authentication. But, I don't want to use SQL Authentication to connect to SQL server, I want to use windows authentication. Can somebody plase give me detailed setps for how to implement this? Thanks for your help in advance. -Chintak. 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend