Hi
I don't think the problem is in the code since this is an isolated case.
The application is currently running on approx. 5 networks without any
problems.
In this case, it is a laptop that has just been installed with Windows XP SP
2 with all the latest updates and fixes.
I've loading the server (hosted by a Windows Service) and client components
on the same computer and attempt to connect to the server components. The
computer isn't connected to a network so I also tried connecting from
another computer to the server components on that computer via a VPN but the
same problem. I can however connect the client components on that computer
to another server and that works. So I guess the problem is somewhere
related to the server components or Windows Service.
Any suggestions now?
[quoted text, click to view] "William" <van_diesel@bigfoot.com> wrote in message
news:%23DEEp2a6HHA.4252@TK2MSFTNGP05.phx.gbl...
> Hi
>
> I've developed a remoting application that uses a TCP channel with a
> Binary
> formatter. The server side is a Windows Service that is on the same server
> as the database.
> When I deploy the server part, I usually create a user account on the
> server that the clients use to connect with (the clients aren't always on
> a domain).
> Now this application works on my computer (server and client installed on
> same pc), it works on all our customer's networks but for some reason I
> can't get it to work on my partner's new computer that is set up with
> Windows XP SP2. The Windows Service and SQL Server 2000 is loaded on his
> computer and the client components which basically connects to the service
> on the same computer. I've tried connecting by specifying the location's
> IP address, localhost and the computer's name. I tried connecting via the
> user account that I created. tried using the username that I was logged on
> with, Administrator and even tried leaving it blank.
> Is there some setting that can cause this? The "Allow this computer to be
> accessed from network" policy has the users linked to it.
>
> Oh yes... the error that I get is "A remote side security requirement was
> not fulfilled during authentication. Try increasing the ProtectionLevel
> and/or ImpersonationLevel."
>
