"connect to server" doesn't show a volume - why?

[Doug Lassiter]

iMac 10.6.8 connecting to Yikes 10.3.9.

•*"Connect to Server"
•*Select the Yikes ... afp://me@yikes.myplace.net

I get a pane saying "Select the volumes you want to mount on 'Yikes:"

But one of the volumes (one partition of two on an external disk that I use for backup on that Yikes), isn't listed. Huh? So where is it? It used to always be shown on this pane. If I sit down at the Yikes, or VNC to it, that partition is mounted and available. If I use Disk Utility on the partition, it verifies fine. Permissions are identical to the other partition.

So why can't I connect to it remotely?

I will say that because of some error, I had to erase that partition and restore everything on it (SuperDuper). That worked great, and in all other respects it behaves fine now. It was after doing this that I couldn't connect to it remotely. Something has changed. What?

[mclbruce]

Right click or control-click and do a "get info" on both partitions. Take a look at permissions at the bottom of the panel and see if there are differences.

[Doug Lassiter]

Quote: Originally Posted by mclbruce Right click or control-click and do a "get info" on both partitions. Take a look at permissions at the bottom of the panel and see if there are differences.

Thank you. That was my first thought. Both volumes are identical, when viewed in this way. I can r/w, owner is "system", which can r/w, group is "admin" which can r/w, and others can read only.

Again, these volumes look and behave identically *except* that one volume is offered up as a selectable volume to connect to remotely, and the other is not. Something is different about them, and I just can't figure out what.

In fact, these partitions are used as two separate backup epochs. So they are identical in size and by and large, they have the same thing on them.

BTW, it's not an issue with the machine I'm trying to connect to them. I have this problem not just with my iMac, but with other machines.

[Doug Lassiter]

Eh, I rebooted the Yikes remotely, and now all is fine. Strange, as I thought I did that before. There was a period today when that machine needed to be up and functional, so I had to wait until after that before messing around with it.

Sure would be nice to understand what bit got flipped.

When in doubt ... reboot!