Dave Botsch wrote: > So, in concert with the Symantec Client Firewall, we've seen some systems give > the "network path not found" when accessing ThisCell. Usually, this goes away > after a while as specified in: > > http://www.openafs.org/pipermail/openafs-info/2007-January/024992.html > > Note that "network path not found" does not mean that communication with > the file servers doesn't work. It more often means that Windows is > timing out the connection to the AFS SMB server, tearing it down, and > waiting for a while, and reconnecting. In that period of "waiting for > a while" you get "network path not found" errors and "NET USE" will > report paths to \\AFS as disconnected. > > I can't yet reproduce this on command to be able to capture debugging > information, but am willing to spend some more time on this if it's not > yet known what is going on (I see mention in the above email of a bug > report... did that ever happen?). In the meantime, I wanted to ask: > > any known issues as to why this would happen and why it only seems to happen > with ThisCell? We've seen it be more prominent it seems when the ThisCell is > using freelance. > > Any known way to kick Windows to stop "waiting a while" and try again now? > > Thanks!
OAFW has special logic in it to allow it to configure the Windows XP
Firewall to open the 7001/UDP port and allow AFS servers to send
callbacks to the OpenAFS cache manager. There is no such automatic
configuration for the Symantec Firewall. Have you configured it to open
the port used for communicating with the cache manager?
"Network path not found" is the error that is returned when:
* The CIFS client has dropped the connection to the AFS client service
and it has not yet reached the end of its retry back-off algorithm
* The AFS Cache Manager is unable to talk with the file server to
obtain current status information for the specified path
+ file server is down, volume is busy, etc.
+ network outage
+ file server refuses to talk to the client because it thinks the
client is at an addr/port that it is no longer at (bug in 1.4.1)
* The path really doesn't exist in AFS
What do you mean by "ThisCell" in this context?
You can't kick Windows. If the problem is the AFS client thinks the AFS
file servers are down, you can "fs checkservers -cell cellname". If the
AFS file servers won't talk to the client and you are running 1.4.1 you
can upgrade your servers to 1.4.2 or wait for the file servers to timeout.
However, you have not provided sufficient data to be able to identify
which of these possibilities this instance of the error message is.
More debugging is required.
Jeffrey Altman
Secure Endpoints Inc.
smime.p7s
Description: S/MIME Cryptographic Signature
