Winform cannot connect to webservice via CAS policy

[Dan]

Hi

I have a dotnet application that communicates with a web service running
locally on my machine. It connects fine and works ok when I run the
application from the c: drive. Am having problems running it from my ftp
location, so

ftp://localhost/setup.exe

In the Runtime security policy I have created a new code group under my
machine entry, and made the membership conditions to use Strong name, and
assigned the public key from setup.exe to it. The permission set is set to
FullTrust.
The application now launces, but when accessing the web service I get the
following exception thrown:

************** Exception Text **************
System.Net.WebException: Unable to connect to the remote server --->
System.Net.Sockets.SocketException: No connection could be made because the
target machine actively refused it
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot,
SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure,
Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState
state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)


I've tried setting all the permission manually, but nothing work. and I've
tried the evaluate assembly util which tells me I've got things setup
correctly.

But the application works fine when not via the ftp!!! so I now the web
service is working ok.


The FTP on ISS is set to use annouymous access

Am using vs2005 on windows xp pro.

thanks for any help
dan

 

[Dan]

ah! fixed it!

just incase anybody needs to know. I had the apppointing to the webservice
from localhost - which wouldn't work from running from the ftp location. I
switched it to my machine name and it worked! must be because running via
CAS it's know about or allow localhost connections.

!