Check your open ports on the router — ARD uses TCP 3283 and 5900 -
> On Jun 22, 2016, at 9:42 AM, Nicola Ferrari (#554252) <[email protected]> > wrote: > > Hi everybody. > I'm new to the list. Please be patient if my english will not be perfect: I'm > italian.. > I'm experiencing a quite strange problem in a customer's OSX Network. > (I'm not an expert about MacOSX networks..) > > An imac workstation runs on a subnet 192.168.1.0/24. > We're having a L3 switch that serves multiple labs with their own > vlans/subnets. (192.168.11.0/24, .12.0/24,...) > In each labs there are a number of imacs running, with the "remote control" > service enabled (osx 10.9). > > If I do a network scan from my imac, specifying the subnet range (eg. > 192.168.11.11 to 192.168.11.249) I can see machines and all > > status informations are listed, but I can't make the screen control feature > work. > (message saying "connecting to ...." appear, and remains on the screen..) > > With machines that are directly on the 192.168.1.0/24 network, instead, no > problem: I can control them regularly. > > Since (as far as I know..) ARD use the standard 5900 port, why doesn't it > work correctly across different subnets? > Routing is working fine (i can reach remote imacs using ping or other diag > commands, and status messages on ARD are displaying fine) > > Do these systems use some kind of "out-of-the-box" firewall that I need to > reconfigure to accept requests from subnets that are not the subnet where the > client runs on? > > N > > -- > +---------------------+ > | Linux User #554252 | > +---------------------+ > > _______________________________________________ > MacOSX-admin mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-admin _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
