Signed jar still won't allow remote connection

I've compiled this Java applet and rolled it into a jar and signed the jar with an authentic cert from Thawte.

The jar lives on server X. I'm trying to make a connection to server Y. I am not allowed to do this for some reason. I keep getting a SecurityPermission exception when creating the socket.

I've read that applets can't normally connect to any server except the server the jar came from. But in this case, the jar is signed. Its authentic code. Why won't it allow me to connect?

Is there some way to "ask" the user for permission to connect to a different server? If so, is there some way to save this permission to the users local policy so they won't get asked again?

Thanks,

Matthew

[737 byte] By [utdrmaca] at [2007-10-2 6:12:44]