Monitor clients on different gateways

[lfowler]

Since we can already scan various subnets and directly connect to an IP... Why not allow to [b]scan across default gateways[/b]? OR for that matter... add [b]scan for DNS's [/b]to the same request?

Maybe make the Network tab work more like a [b]DHCP Scan[/b] area and assign various additional scan funtions and ranges!

We as a school district share a basic common sub (ex. 255.252.0.0) & district sub (ex. 255.252.255.252), but each are assigned separate gateways (ex. 10.54.0.1, 10.67.0.1, 10.72.0.1) w/in the common sub. :cyclops:

And when I'm at home, I'm not even using same ip / sub / gateway (ex. 72.180.127.215) as school district (FIOS which is actually faster than them); but could actually do some work from home when caring for a sick child.

Just a thought - don't even know if it's possible??? :stare:

[AlexA]

The only way you can connect from home is via a VPN connection to where you work , which would provide you with a 10.X.X.X ip address, so you're "Virtually" in the network. 10.X.X.X Addresses are never routed by ISPs.

So working from home is an easy posibility, just if your district sets up a VPN for you. I've never done or tried this with AB tutor, but it's the only way to connect to an internal business/district network from home.

AB Tutor automatically scans the local broadcast range of the subnet the Monitor/Tutor software is installed on via their Physical Addresses (Layer 2), which sends a request to every PC looking for the client.

Gateways are your routers (Layer 3 Devices), and usually in a large network they block multicasts and firewalls can also block these multicasts, which is the best thing a network admin can do for such large networks to keep performance high.

DHCP is a passive application. It waits for requests and then provides valid host addresses to make network admins life easy.

Instead of a scan you would need a feature you can specify on the client, saying perhaps the IP of your Tutor/Monitor machine. Example:

My Tutor is on Host X with IP A.B.C.D
ROUTER
I'm installing client on Host Y with IP A.B.C.E

They are seperated by a router, but are able to reach one another within the same business inter-network. My Tutor on host X Can't scan and fine Host Y, it can't pass the Router with multicast filtering enabled.

Now if ABtutor developed a client request, we could during the installation of the AB Tutor Client on Host Y, Input Host X's IP Address (A.B.C.D). Then everytime Host Y was turned on, and every X Seconds it could send a direct request to Host X (A.B.C.D) requesting to be added to the list of computers, and once added stop requesting. If connection is lost it will start requesting verification that it's connected again.

In a sense you're asking for the cleints to request the Host. Not the Host scanning for clients, a very good idea for a feature I think. Instead of having to add the Ip of EACH client, and worrying about them changing due to DHCP, you can have the clients come to you : ).