Since updating, my Apple Remote Desktop 3.7 is not working properly.

There's something else that might be messing up ARD.

It looks like, if you have a machine that has both Ethernet AND a Wireless connection ON at the same time, ARD gets confused.

Our Machines are set up with Ethernet first, and Wireless second, normally when a user unplugs from Ethernet to move their laptop to a conference room or something, it just automatically switches to Wireless, and everything is fine. Up until 10.9 I would only see one IP address, so if they were on a floor, I culd scan by floor, and if they switched to Wireless I could search the wireless range to log on and help them.

But now it "feels" like both Ethernet and Wireless are reporting to ARD at the same time. That would explain why when I search the Wireless range, which is a xxx.xxx.101.xxx range I am seeing machines reporting IP addresses in the xxx.xxx.97.xxx range when the Wireless Scanner is only set to scan the .101.xxx range

Just a thought. but i'm finding that the new 3.7.1 ARD is still not quite right...

Robman I have tried to disable WiFi completely in the network and removed all computers in the 3.7 admin but it's a dead end. It's said to be something that was fixed in 3.7.1 but if that's Apples only fix about this flickering it just tells me they need to do a better job in the 3.7.2-update.

If you are removing all the computers from All Computers list, note that it took me 4X to get all the machines out. I would clear them all, quit the app, restart it, and scan a subnet and notice that machines were still in there. I'd remove them all again and quit the app.

This took me 4 times before the All Computers would stay empty. Your mileage will vary.

Then re-verified and re-added all my machines into their Scanners. It's looking better, DNS is clean now, but still i'm seeing wrong IP addresses in a Scanner range where they should not be... But, the users could just be moving around and things are going to be OK..

ARD is at least useable for me now. Hope this helps you all...

I installed the 3.7.1 update. It seems to have fixed some of my problems with our remote office. I am goign to continue to test it and see what happens. I still have 1 user in that remote office that still is not showing up on ARD. I have made sure that the sharing preferences are configured correctly. I will post more if I find anything.

I installed 3.7.1 last night but didn't try it until this morning. I started by throwing away the ARD folder in ~/Library/Components and am rebuilding the ARD database from scratch. The building of the new database is going well, but it also went well in 3.7. The test will be who ARD operates after a few days and client machiens get assigned new IPs via DHCP.

The current update appears to have resolved my problems. I am running OSX 10.9, have installed ARD Admin 3.7.1 and updated my clients to 3.7.1. I followed the suggestions on this board to delete computers from the All Computers list and rebuild my own lists. It did take several deletes and restarts to get rid of them all. (Thanks for that suggestion) Initially, I had problems with screen sharing locking up on my clients. The only way out was to restart those machines. I did several total restarts of those machines and then the whole lab, then tested screen sharing again and now it works. No more freeze ups and computers in my list appear to be stable and normal. I will keep my fingers crossed today that it will hold up and work while actual people are logged in to the computers.

Add me to the list of "ME TOO!"

- Computers flickering between available and offline.

- computers completely disappearing from computer lists and sometimes reappearing

- ARD admin network scans are completely blind to some computers that I know for a fact are turned on, connected to the LAN and configured to permit access.

- attempting to view or control computers randomly will actually connect to entirely different computers

- Client versions range from 3.4 through 3.7.1... ALL are affected

- client computers are a wide variety of Mac models produced over the past 7 years: (intel and PPC) iMacs, Minis, Pros, MBP, MBA, PowerMac G5

- completely deleting all computer lists and removing all computers from the All Computers group and then attempting to rebuild from scratch does not fix the problem.

- symptoms are present on all our admin Macs running ARD Admin 3.7.x. and OSX 10.8 and 10.9

- everything worked just fine under ARD 3.6 (relatively speaking)

- updating ARD Admin from 3.7 to 3.7.1 does not make it any better.

Well, so far ARD 3.7.1 is working for me.

Screen control/share through 10.8/10.9 with Client 3.7.1 AND the local firewall on.

I've had to completely delete all previously accessed computers and add them again which was a ***** to do but I'm there. Several run/delete/quit cycles as old Macs suddenly appeared from nowhere.

So far so good...

Everything is OK as of day 2. The real test will be Monday when most of our clients will have a new IP address assigned to them.

I am having the same issues as in this discussion since the 3.7 upgrade.

I have updated the Admin to 3.7.1 and one of my clients to 3.7.1 to see if I could get it to work like some of the previous posters. Once I delete my client machine from the All Computers list however I am having trouble getting it to add again to the list. It looks like it's going to add and then displays the drop-down list where you'd add the User Name and Password for about 1 second and then it's gone. Not very helpful. Any chance Apple is going to this fixed?

Day 3 and ARD is working much better now.. No more Flickering. Machines are not jumping LAN subnets anymore, But it still has some confusion where I will see IP's show the WI-FI IP even though it should jsut be showing me the LAN IP. but again, i think Apple made a change somewhere where machines broadcast BOTH the LAN and Wi-FI IP at the same time now, instead of just one. Could also be the way our Wireless is set up. It's pretty tight and certificate-based. Not sure if that's in the OS or ARD not filtering them right.

They key for me was getting everything out of All Computers. Took Multiple times, but once that was clean, ARD is much more useable.

If it gets bad again (Probably right after I post this :-), you know how it goes) I'll post back..

Good Luck to all, and to all a good day!!!!

ARD 3.7.1 , 10.9 > 7.5

After doing everthing but restarting the client, I finally restarted the client...and now it works!

...really a nube to this, but restarting worked for me.