From: Wolfy on
I have two identical (or as near as identical as makes any difference)
Solaris 10 boxes. Home directories are shared across systems via NFS
(the home directories are exported by a 3rd server), and the user
names and uids are identical where it matters. When I connect to
server A with:

ssh -X username(a)A.domain.com

I can easily run X11 applications (xclock, for instance). But, when I
connect to server B instead:

ssh -X username(a)B.domain.com

I get:

X11 connection rejected because of wrong authentication.
X connection to B:10.0 broken (explicit kill or server shutdown).

There is plenty of disk space on all file systems on both servers (low
disk space is often mentioned as a cause for this message). "xauth
list" works on both servers, but only shows cookies for system A.
Both servers are set up like this in sshd_config:

X11Forwarding yes
X11DisplayOffset 10
X11UseLocalHost no

The underlying cause of this appears to be that system B is unable to
(or is refusing to) write to the .Xauthority file, which is owned by
"username" with permissions 600. All parent directories have at least
permissions 711. If I delete the .Xauthority file, system A will
happily recreate it. However, if I delete it again and go to system
B, the file is not recreated. If I run:

xauth list

I get:

xauth: creating new authority file /home/.../.Xauthority

but the file is not actually created.

Any suggestions? Help gratefully accepted...