|
|
|
|
|
|
|
  |
||||||
|
|
|||||
|
       |
|||||
|
||||||
|
 |
|||||
|
WolfCall Frequently Asked Questions |
|||||
1.0 General WolfCall Information
- 1.1 What is WolfCall?
- 1.2 I've heard about KAUTH. How is WolfCall related to KAUTH?
- 1.3 Who supports WolfCall?
- 1.4 Where can I get WolfCall?
- 2.1 Which versions of Windows does WolfCall work with?
- 2.2 How
dodon't I make WolfCall work with Windows NT4?
- 3.1 How do I get access to AFS from my Windows-based computer?
- 3.2 What's the difference between the OpenAFS Client and the IBM AFS Client?
7.0 Questions from Systems Administrators
- 9.1 WolfCall won't work for me. How do I troubleshoot the problem?
- 9.2 I can't get WolfCall to work. Who do I contact for help?
1.0 General WolfCall Information
1.1 What is WolfCall?WolfCall is a Windows-based application that works with an AFS Client and the Kerberos for Windows software from MIT to let you easily access your AFS space from Windows-based computers. For more information about how WolfCall interacts with Kerberos for Windows and the AFS Client, see About Authentication.
1.2 I've heard about KAUTH. How is WolfCall related to KAUTH?KAUTH is the predecessor to WolfCall. We renamed KAUTH to WolfCall because WolfCall sounds cooler*.
KAUTH used a now ancient version of the Kerberos software from MIT. WolfCall should be more robust than KAUTH because of more careful error checking and a much newer set of Kerberos client libraries.
*O, be some
other name! What's in a name? That which we
call a rose by any other name would smell as sweet.
Yeah, but Shakespeare never had to try to pronounce "KAUTH"
1.3 Who supports WolfCall?Hopefully, the community.
The WolfCall project web site and the WolfCall program are currently developed and supported by the Systems group in Information Technology and Engineering Computing Services (ITECS) of the College of Engineering. It is done by Engineering staff for Engineering students, faculty, and staff but made available to the larger University community. More details on WolfCall support can be found in the WolfCall Statement of Support.
1.4 Where can I get WolfCall?Click here for installation instructions and a link to downloads.
2.0 WolfCall and Windows
2.1 Which versions of Windows does WolfCall work with?WolfCall is targeted at Windows 2000 and Windows XP. WolfCall will not work with NT4 or Microsoft Vista.
We do not plan on porting WolfCall to Windows 95/98/ME.
2.2 HowThis answer used to explain how to get around some problems and get WolfCall to work in NT4. However, new additions to the program make it no longer operate at all in NT4. We do not see a compelling reason to go out of our way to correct this.
3.0 WolfCall and AFS
3.1 How do I get access to AFS from my Windows-based computer?In short, if you are running Windows 2000 or XP:
- Get an AFS Client.
- Get Kerberos.
- Get WolfCall.
The WolfCall home page has installation instructions and links to downloads for all three.
3.2 What's the difference between the OpenAFS Client and the IBM AFS Client?The OpenAFS client (http://www.openafs.org) is an Open Source release of the IBM/Transarc AFS client to the community.
See IBM's FAQ at http://www-124.ibm.com/developerworks/oss/afs/info.html.
The OpenAFS client and the IBM AFS Client behave pretty much the same. However, ITECS recommends the OpenAFS client because it is continually updated and fixes many small bugs found in the Transarc Client.
4.0 WolfCall and Kerberos
4.1 Why do I need Kerberos software? Doesn't AFS already have Kerberos?In short, AFS only supports a prehistoric iteration of the Kerberos protocol. NCSU does not run Kerberos servers supporting this protocol, so AFS needs a little help authenticating.
See About Authentication for more details.
5.0 WolfCall Development
5.1 Can I get the source code to WolfCall?Yes. WolfCall is open source. See the Installation Instructions for information on obtaining and using the source code.
5.2 How do I help out with WolfCall development?WolfCall is meant to be community supported and is an open source product. If you have some interesting development ideas or code contributions, bug fixes, whatever, contact the WolfCall mailing list, wolfcall@lists.ncsu.edu.
6.0 Known Issues
6.1 Auto-login appears to work, yet I am not authenticated. What gives?WolfCall's auto-login feature uses a two-stage process. The first stage occurs after you press the Enter key after typing your username and password. The second stage occurs after your session is created.
Certain things will cause the second stage to not get kicked off. Currently, the Novell Client and Microsoft's "fake" Novell Client are known to do this.
To work around this problem, you must start the second stage yourself. Either create a Novell login script or a startup shortcut to fire up WolfCall and complete the second stage. You must execute WolfCall as follows:
"C:\Program Files\NC State\WolfCall\WolfCall.exe" /tfsl_login
7.0 Questions from Systems Administrators
7.1 How do I do an automated install?WolfCall uses an ordinary MSI database, so
you can do an automated install in the ordinary way:
msiexec /qb-! /i wolfcall.msi ADDLOCAL=ShortCuts,WolfCall,HesUtils,TFService,RenewService,WKAuthLib
This will install all of WolfCall's features with a minimal progress display and no cancel button or end prompt. Replace "/qb-!" with "/qn" for a completely silent install. See Microsoft's msiexec documentation.
You can pick and choose features (although nothing will work without WKAuthLib, etc), or do "ADDLOCAL=ALL". Note that the names of features may change in subsequent versions.
KfW is much the same:
msiexec /qb-! /i kfw-ncsu.msi ADDLOCAL=Shortcuts,KfW,Custom
And lastly, the NCSU-customized
OpenAFS MSI can be extracted by running the installer executable (which
will expand some files to %temp%), fishing the MSI out of %temp%, and
running:
msiexec /qb-! /i "OpenAFS for NCSU.msi" ADDLOCAL=Client
snAppShotting MSI-based applications is always an iffy proposition. The Windows Installer registration database, which resides in the Windows registry, does not generally transfer from machine to machine very well.
At the time of this writing, WolfCall does not refer to its MSI registration unless it is called with the self-repair command-line argument, so it should be OK to snAppShot. However, the instructions above should accomplish the task, and work better.
8.0 Debugging WolfCall
8.1 How do I turn on logging in WolfCall?
To help find potential problems, The Ticket-File Service, the Ticket Renewal Service, and Wolfcall executable itself all can write debugging information to log files. However, this behavior is disabled by default.
The WolfCall Reference has the exact registry keys that need to be set to turn on debug logging for one or all of these portions, as well as how to specify the locations of the log files.
Note that many "expected errors" are logged to these files. For example, the function that lists credentials logs an error if there are no credentials to list, even though that condition is perfectly normal.
8.2 How do I do hesiod lookups at the command line?
Type the following in. You can (if you want) replace the server IP address with any of the NCSU DNS servers.
nslookup
server 152.1.1.206
set type=TXT
set class=hesiod
UNITYID.filsys.ns.eos.ncsu.edu
If you get a nonexistant domain error instead of the filsys entry it means that your router is intercepting DNS traffic.
9.0 Getting Help
9.1 WolfCall won't work for me. How do I troubleshoot the problem?
First of all, if you are using WolfCall on your own machine, make sure it was installed per the instructions.
If authentication with WolfCall is stopping with an error, be sure to copy and paste the error message. To do this, select the text, right click the selection, and select "copy."
Check the Remedy solutions page for WolfCall to see if there is a documented solution for the problem.
9.2 I can't get WolfCall to work. Who do I contact for help?
If you need assistance, and are in the College of Engineering, contact the ITECS Help Desk. Otherwise, contact your departmental or collegiate support personnel.
Frequently Asked Questions
Technical Documents
![< to Top]](../Media/graphics/footer_links/top_arrow.gif){kind=icon}
![[ ENGR Template ]](../Interface/images/banner.gif){kind=small}