Hello,
according to view-61-scenarios-ssl-certificates.pdf, I added a locked.properties file under C:\Program Files\VMware\VMware View\Server\sslgateway\conf
and then restarted the service even the connection server, but got nothing changed.
netstat -na output:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4002 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4101 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4172 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
any idea?
On the face of it, it looks like the config should be picked up. A couple of things to check:
1. Make sure that you've not accidentally created "locked.properties.txt", I've seen this more times than you'd think!
2. Check the debug log file during service startup for information (c:\programdata\vmware\vdm\logs), you should see something along the lines of "Server mode: HTTP_FORWARD" along with the other configuration lines
Mike
Hi Mike,
Thanks for your reply. I double checked the two points you mentioned,
1. this is a *.properties file, not a *.txt file
2. something like HTTP_FORWARD
but connection server does not listen on port 8670
