rats. No, I didn't. But I'll put that in my bag of responses when troubleshooting openafs.
On Fri, Jun 30, 2006 at 01:22:22PM -0400, Jeffrey Altman wrote: > David Bear wrote: > > I solve the problem -- but I never diagnose the issue nor did I > > control my changes to the system to see which really affected openafs. > > > > I solved it by > > > > 1) removing checkpoint > > 2) removing openafs > > 3) reseting the ms tcpip stack using the netsh command. > > 4) reloading openafs > > 5) reloading checkpoint > > > > After doing that -- openafs was snappy and worked well. > > By any chance did you "netsh winsock dump" before you made the > change so we could figure out what was misconfigured? > > Jeffrey Altman -- David Bear phone: 480-965-8257 fax: 480-965-9189 College of Public Programs/ASU Wilson Hall 232 Tempe, AZ 85287-0803 "Beware the IP portfolio, everyone will be suspect of trespassing" _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
