[kennedy]

My large network at my business is working fine, overall.
My 2-computer network at home is not...

The server seems to be working fine. But when I go to
login at the client, it takes about 3 minutes for the
login screen to switch to the barber pole saying its
logging in, and then another couple of minutes to login.
If that wasn't bad enough, when it comes up, it has
invented an empty home directory where the real one
should be. And although my server and its shared volumes
are visible in Network as expected, the volumes are empty
other than the invented home directory.

I'd say the client computer seems to be talking to the
server since it does manage to authenticate me (an account
only known on the server), however given that its inventing
a fake home directory, I suppose it could be quietly going
off of cached or invented login info, as ludicrous as that
sounds.

I can ping the server... and I can ftp into it.

In the past I've had temporary problems such as this... logging
out and back in would sometimes fix it and restarting would
always fix it... but in this case, I've completely restarted
both server and client multiple times and nothing is working.

Any ideas??? Any at all???

Thanks.

[kennedy]

Many months later, I am still having problems with this behavior popping up... has *anyone* else seen similar?

On my network at work, this popped up on one client computer. I am going to wipe it clean and re-install later today in hopes of fixing it.

At home, in attempt to solve the problem, I did just that. It mostly solved the problem... every network user account can log in okay *except* myself. My one account is only peculiar in that it is an Administrator account. It seems that when I log in as that account, it takes a very long time and then fails to mount any of the disks from the server. Since my home is on one of those disks, it fakes a minimal home directory as if it was mounted.

Any ideas on what the problem might be?

Thanks,

Brian