![]()
telnetting on the ports from outside to the security server worked so I knew my firewall ports were opened properly so i started looking at the client i was connecting from. #SONICWALL GUIDE TO PORT FORWARDING WIZARD HOW TO#I followed the article Mark sent me to use wireshark and saw that communication was going out without problems it just wasn't making it back in from the internet. Click Quick Configuration in the top navigation menu.You can learn more about the Public Server Wizard by reading How to open ports using the SonicWall Public Server Wizard. Thanks to all that posted and tried to help. I have since tested it at several other locations and all has been well, it apparently was just this one location having problems. putting my remote client in the DMZ of the remote router fixed the issue for that remote site. strange because the way the NAT policies were set up on that client it was supposed to allow return communication it the original communication was initiated by an internal client. ![]() for some reason or another it was blocking the returning PCoIP communication. the issue turned out to be the firewall at the original test remote location. my environment was set up properly and as it should and was working fine. Without changing anything I tried logging in from a different remote location and was able to log in just fine. I am well aware of Mark's experience and if you refer to my response post to him I clearly stated that I too thought it was the protocol being blocked somewhere, just didn't know where. #SONICWALL GUIDE TO PORT FORWARDING WIZARD WINDOWS#thanks!Īlso, local windows firewall is turned off on the servers, desktops, and the external client my public URL and public PCoIP URL on the security server is set to the public IP address we are trying to connect from externally and the name is resolvable by the external client.Īny thoughts or suggestions would be greatly appreciated. I found many different issues relating to the black screen with the connection being ended, but nothing on the timed out error. but the desktop never loads, i receive a connection timed out error. PCoIP connections connect to security server, i authenticate, select my desktop/pool and get a black screen. ![]() Security server, connection server, and ESX/vCenter serve running the view desktops all on internal LAN, no DMZ.Įverything works internally fine, externally only RDP connections will work SonicWall NSA 2400 firewall, ports 80, 443, and 4172 (tcp and udp) forwarded to security server, no outbound connections filtered. I have followed all related documents and setup guides but cannot get outside office PCoIP connectivity to our view environment working properly. To use port forwarding, first determine the local IP address of the. ![]() This is not the typical black screen displaying the connection ended. On the Rule Type page of the New Outbound Rule wizard, click Custom, and then click Next. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |