![]() ![]() I googled a bit more and it seems that TeamViewer uses UDP hole punching to create a direct connection. (I turned off my Win7 firewall for testing sake) Status -> UPNP also showed that no ports were enabled/created at any time during the connection. ![]() I enabled it and allowed both UPNP and NAT-PNP, but still UDP connection could not be established.Īlso, I don't think TeamViewer uses UPNP. ![]() How can I try to fix this UPNP enabled? If not, try enabling it. Status -> System Logs -> General and Firewall - don't show any connections being blocked when I'm trying to connect with TeamViewer.Ĭan someone help shine some light on this issue? I haven't tried outside of the 2.1.x branch, whether UDP works, all my pfSense installations are in the 2.1.x branch… Even without that rule, UDP is still not working. Nothing special, only SMTP port is blocked from non e-mail servers. My outgoing LAN rules are defined like this: Default install, no packages, couple of port forwardings and that's it. Linksys home router -> Cisco ASA => UDP and TCP workingĪll my pfSense installations are fairly simple.Cisco ASA -> Cisco ASA => UDP and TCP working.If there is no pfSense between my side and remote host, then UDP is working fine.Īny combination of pfSense doesn't allow UDP connections to be created: I have the latest TeamViewer 9 version installed on both sides and "Use UDP (recommended)" is ticked under Options -> Advanced -> Advanced networking. For some reason pfSense 2.1.x branch is blocking outgoing/incoming UDP connections for TeamViewer. ![]()
0 Comments
Leave a Reply. |