Anybody got experience with socket permissioning in VB.Net?

I've got the TCP/IP connection part working in theory, as I can send and return data when running the server and client on the same machine. However, I'm now trying to send data to a remote server and finding that the connection attempt is getting blocked with a Security Permissions error. I've tried demanding various levels of permission through the code but it's not having any of it.

The guys who run the system security have no idea how one might go about adding an application to some sort of .Net "trusted zone", and it appears that all the permissions in the .Net editor (the ConfigWizards app in the Windows\.Net\1.1 folder) are up to the maximum grantable. There is a sub-application in there to Trust a particular assembly, but

a) Even if this worked, it's not a good install procedure to have to go round users' PCs doing this manually

and b) Can it be done through code? I suspect not.


So, the questions are:

1) Is there a way round this in code? (I imagine not, otherwise it'd be pointless security..)

2) Should my system security guys know how to arrange matters so that this assembly can be automatically trusted by the networked PCs?

3) How is the above accomplished?



Any thoughts?



zaza