DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Fri, 17 Aug 2007 14:53:34 -0700,    posted on: microsoft.public.dotnet.distributed_apps        back       

Thread Index
  1    Joel Lyons


Authentication during secure remoting   
I would like to use a "secure" TCP remoting channel to ensure that my data is 
encrypted.  I have my own authentication mechanism since clients will 
normally not be members of the server's domain.

From reading newsgroup posts, it appears that when using a secure TCP 
channel, the server's operating system will always try to authenticate the 
client's credentials.  Is this true?!  It seems to be true since I get "The 
server has rejected the client credentials." whenever I test from non-domain 
client machines.  Testing from client machines logged into the domain works 
fine.

I don't want Windows to try to authenticate the client.  I simply want 
encryption.  Am I out of luck?
Date:Fri, 17 Aug 2007 14:53:34 -0700   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us