...
If the Symantec Client Firewall is installed, you will need to add a rule
allowing all traffic to/from 10.254.254.253
A. Open Symantec CLient Firewall
B. Client Firewall - Configure
C. Advanced Tab
D. General Button
E. Add a rule
F. Permit
G. Connection to and from other computers
H. Only the computers and sites listed below: Add 10.254.254.253
I. TCP and UDP and All types of communication
J. Don't log anything
K. Name the rule AFS Loopback Rule
L. Check All Locations
M. Finish
N. FInd the rule in the list of General Rules (it will be at the bottom) and
repeatedly click "Move Up" to get the rule to the top of the list
If, during the Symantec configuration process, you get a pop up window about a script error, you have two choices:
1. Reinstalling Symantec usually fixes this.
2. Disabling the firewall portion of Symantec and just enabling the built in Windows firewall.
J. NOW, REBOOT. After rebooting, your firewall may prompt you to allow the various afs applications access to the network. You should choose to Always Allow these.
...
and use your netid password.There will be a delay before you get tokens due to a dns problem on
CNF/Cornell's end -- the delay will go away once we get the problem fixed.
To access afs from windows, you can:
...
4. Path should be //afs/cnf.cornell.edu
Lengthy delays in obtaining tokens or trying to browse through the AFS filespace are most likely the result of firewall issues (Symantec or others). If you experience these problems, consult with CNF IT staff on how to resolve the problem.
Mac
Linux/Solaris
To get tokens, after logging in to the machine:
...