RHEL3 XAUTH problems with shared home
 

Stock RHEL 3 using Stock Xfree86 running KDE.

I've got an odd problem. Two computers with same user account sharing the same $HOME directory via NFS.

On the first computer (missiops1) the user logs in and xauth list includes:

missiops1/unix:17 MIT-MAGIC-COOKIE-1 f813ecb7ed40327a0fef630e9bbc52a5
missiops1/unix:13 MIT-MAGIC-COOKIE-1 f813ecb7ed40327a0fef630e9bbc52a5
missiops1/unix:0 MIT-MAGIC-COOKIE-1 f813ecb7ed40327a0fef630e9bbc52a5
missiops1:0 MIT-MAGIC-COOKIE-1 f813ecb7ed40327a0fef630e9bbc52a5


Then, on the second computer (missiops10), the same user logs in and the xauth list shows:

missiops1/unix:17 MIT-MAGIC-COOKIE-1 f813ecb7ed40327a0fef630e9bbc52a5
missiops1/unix:13 MIT-MAGIC-COOKIE-1 f813ecb7ed40327a0fef630e9bbc52a5
missiops1:0 MIT-MAGIC-COOKIE-1 f813ecb7ed40327a0fef630e9bbc52a5
missiops10/unix:0 MIT-MAGIC-COOKIE-1 48937860df570d6b8f2adbadc2ea77af
glastops10:0 MIT-MAGIC-COOKIE-1 48937860df570d6b8f2adbadc2ea77af

Then on the first computer, that user can not bring up any more xwindows. It is because his missiops1/unix:0 entry in the shared xauth file has been removed.

Computers with dissimilar names sharing the same home directory do not have this problem. So why am I having a problem with missiops1 and missiops10 operating together? I have this problem in multiple deployments because I've named the systems numerically at each deployment, ie. missiops1-22. I also have the same problem with missiops1 vs any computer named missiops1X. Using dissimilar names solves the problem, but I would love to track down the script that is removing the incorrect xauth entries.