We had problems using the Symantec dektop firewall with AFS (and several other things, too). Originally, the firewall was blocking AFS attempts and manually modifying the rulesets allowed AFS to work; until we live updated. The live update added some hidden rules that blocked AFS and could not (as far as we could find) be over-ridden.
-frank > Date: Sun, 27 Jan 2002 15:58:28 -0500 (EST) > From: "Steven N. Hirsch" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: [OpenAFS] Problems under WinNT 4.0sp6 > > All, > > I am getting nowhere quickly trying to use OpenAFS in a VMware NT 4.0 > session. This VM is also running Symantec Desktop Firewall > and a Nortel > 'Contivity' VPN client. The latter shows up as an additional > adapter in > network settings and I'm wondering if it's confusing AFS. > > Symptoms are the dreaded Error: 0x0000042A when I attempt to > start the afs > client service. FWIW, the Transarc 3.6 Patch 4 client fails > in precisely > the same manner. > > Any suggestions for debugging? > > Steve _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
