billdossett wrote:
hmm, about what I expected... the firewall people say it is open... they are pointing to the fact that the desktop is trying to connect to a private 192.168 address.... I love outsourcing IT :-(
If I can't show that the desktop is trying to connect to the security server, I haven't got a lot to go on to tell them what is wrong.
You can prove this by running wireshark on a test Windows client on the outside. If you've configured things according to those 3 steps, you'll see a PCoIP connection to the Security Server IP address on TCP port 4172. You'll then see UDP datagrams on destination port 4172 to the same Security Server IP address. If your wireshark trace on the Security Server doesn't see these UDP 4172 datagrams arriving at the Security Server than that is your problem. It will show that the UDP 4172 datagrams from the client to the Security Server are being blocked somewhere and you will therefore get a black screen.
The fact that the desktops are trying to connect to a 192 address is normal until it receives a UDP datagram from the Security Server. This part is not the problem.
Let us know what it was.
Mark