Jump to content

Recommended Posts

Posted

Anybody using the Netsupport DNA Web Browser app for IOS

If so anything you've done to get the app capturing to the server. I can get it to show hardware info. Just won't capture anything.

 

Stuck at the moment with being told its a filtering issue by support. And ISP opening all ports and no filtering and still having the same issue.

Posted
It shouldn't be a filtering issue, as you specify your local server IP (where the DNA Console/Database are installed), on the installed iOS App unless you're using a remote server?
Posted

I didnt think it would be. Like i say it pulls the device hardware with local ip or server name so it's communicating. Just no captures.

Do you have the app working?

Posted

Yes it works absolutely fine, ranging from iOS9 to iOS11, no issues.

 

I'd stick with the IP myself, rather than the hostname. It doesn't need to rely on DNS that way.

Posted

Cool good to know it works. Thanks i'll try ip again.

Same ios9-ios11 at school.

Anything specific on server firewall you've done. Just opened the port it uses. I have firewall off at the minute while i'm testing.

Not sure what else there is to try

  • 2 months later...
Posted
Did you get anywhere with this? I have one iPad that doesn't go through any filtering and it's exactly the same as the others. They all appear on the list but you don't get any information on them.
Posted
I’m stuck. Set up a test DNA server. With app on my phone. On a standard ‘home’ internet connection. Works perfect. But back at any school with filtering (all the same provider though but different versions of filtering) even when the device is set to bypass filtering. Can’t get it to work. I can’t get any url or ports that need to be allowed from netsupport and isp can’t see anything being blocked. So I’m stuck
Posted
that's frustrating. I've been in a similiar position with the Chromebooks but they are just about end of life and we are moving to iPads, so I had hoped the iOS app would work.
Posted

Hi @Bev , @whartomt01

 

The DNA iOS/Chrome agent connects to the DNA Server on port 1743 via a Web Socket. The DNA Server listens on port 1743. The only filtering exception that we are aware of that will need adding is for port 1743 for the DNA server's local IP Address.

 

It does appear as though there is filtering in place which is restricitng this traffic from reaching the DNA Server, however, we will need to confirm what this is.

 

We have recently been reviewing some additional wireshark tracing which captures all packets on port 1743 from a specific IP address. As such, we would like to apply this to your DNA Server and one of the iOS/Chrome devices so we can determine at which point the the connection is failing at.

 

I can see that you both have existing tickets with us regarding this so we will be in contact shorlty to advise on the steps that we would like to take.

 

Adam

  • 2 weeks later...
Posted

We go through our council's smoothwall

 

I have received your email about testing the link but I'm a bit swamped with setting up 1;1 ipads for all our new pupils, so I haven't had a chance to run the test yet. I will do it soon though

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...