Socket Policy Server Suddenly Broke

ericheimburg · Post by **ericheimburg** » 14 May 2011, 03:43

SmartFoxServer's socket policy server suddenly stopped working on my development machine. (It's running Windows 7, and I'm developing for Unity). The option is still turned on in the admin panel, and the file it's serving is still there, but the Unity player can't talk to port 843 anymore, so Unity fails to connect due to the lack of a policy server. (And I can verify that port 843 is not accessible when I try to connect to it with PuTTY.)

When I run sockpol.exe (the simple policy server that comes with Unity), everything works fine again.

I haven't made server-side changes since it stopped working. The only thing that raises red flags is that I just accepted a bunch of Windows 7 system updates. But I'm not sure how that would cause a problem.

(I made sure that TCP port 843 is open, along with 9933, in my Windows firewall, just in case. When that didn't help, I turned off the firewall completely; still no luck.)

Any ideas why it broke?

EDIT: telling Unity to prefetch the socket policy from port 9933 does work. But port 843 worked just yesterday... something changed.

appels · Post by **appels** » 14 May 2011, 07:25

as far as i know the policy server in SFS2 has only been on 9933, not 843.

appels · Post by **appels** » 14 May 2011, 07:30

appels wrote:as far as i know the policy server in SFS2 has only been on 9933, not 843.

oops, yeah it runs on 843.
is it still enabled in the config tool ?
maybe a reboot would help.

ThomasLund · Post by **ThomasLund** » 16 May 2011, 17:32

I can only guess - but on a Unix system when you start a server as a non-admin, then you cannot have it open ports on below 1024.

Maybe Windows 7 patch added that?!?! Are you running the service as admin?

/T