Forum Discussion
lewisuk It does sound like a localized problem. Just to be sure, have you tested an alternate network and tried disabling the firewall temporarily before you connect?
Is the firewall a commercial or personal version?
It's a company laptop so I am limited on disabling firewalls and connecting to different networks unfortunately.
I think I will have to contact my IT department and see if they can assist with the firewall side of things.
It will be a commercial firewall.
justincrabtree No it's all Windows 10 based.
Thanks
- Noc14 years agoNew Member
How did you resolved this issue?
- lewisuk4 years agoNew Contributor
I haven't yet. I'm still waiting for our IT team to investigate....
- drobin844 years agoNew Contributor
there is another thread on this. I Updated to 1.3.5282 and i am getting the same errors. Clients on 1.3.5151 are able to remote just fine. but anything newer gives that error message.
At one point I connected and it actually prompted me to wait for host to accept connection. NONE of our clients have this turned on.