Webster, Bill wrote: > However, what I found was that if I manually changed the IP of the > user’s laptop to something else and tried again, everything would work > and ‘fs checkservers’ would report that all servers were ok. Setting > the laptop back to DHCP so it retrieved its original IP address caused > the problem to return. Also, if I manually set another laptop to use > that IP, it would begin experiencing the same problem.
You should also find that "fs uuid -generate" on the client will have the same affect. > So, it seems as if the server stops communicating with whatever is at > that IP address. Then usually after a day or two, the problem just > disappears on its own. Its a problem with the client host tracking code in the file server and it is fixed in 1.4.5. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
