Lars Schimmer wrote: > Jeffrey Altman wrote: >> patrick daniels wrote: >>> I suspect your problem is in trying to initiate the AFS session PRIOR to >>> the VPN connection. Or, at least it's a point to start trouble-shooting. >> There is no reason why the AFS service must be started after the VPN >> when Freelance mode is used. You can always access \\AFS\all even when >> the laptop has no network. > > Is this even true for "not freelance mode" ?
When you are not using "Freelance" mode, the AFS client service cannot start unless it is able to read the "root.afs" volume from the default cell. Non-Freelance mode should only be used on machines that are going to have consistent connectivity with the default cell. Once the AFS client service is up and running, the machine can drop off the network. Of course, you won't be able to access the cell if the servers are unreachable. > To be more specific: > I start my vista, obtain my token and work with no problem in my local net. > But I needed to test something in a private, secure network. > > So I started the cisco VPn client and connected to the private net. > to be sure: the private net has NO connect to the "internet" and any AFS > cell, its firewalled. > But after I successfully connected to the private net via VPN, I could > not reach anything (DNS was gone). If you have no DNS, then you have a configuration problem with your VPN. You should be getting DNS from the VPN network. > So I closed the VPN connection and was in my local net with "normal" > internet as usual. > But I see, I lost my token (key sign was with the red symbol in tray). > I tried to open the "obtain token" dialogue, and nothing happened. > After some time I got the window and typed in my data. And now it seemed > to hung, nothing happend, as if client was dead, after some time I got a > error (sorry, I need to write it down next time). Errors are useful. Debugging information is useful. Anything else is not useful. > So I needed to stop and restart the service to get it working again. > > I assumed OpenAFS connect to the AFS private local-loopback network > 10.254.* on every disconnect, and it works flawless, but maybe some > timing here is evil. Perhaps the Cisco VPN is disabling the loopback network. > btw, I see that specific error sometimes after I changed the wlan and > laptop was in "sleepmode". So far timing issues seems it to be. What is the output of "nbtstat -n" when you are experiencing the problem? What is the output of "dir \\afs\all" ? What is the output of "ipconfig /all" ? Are there any errors in the Application Event Log? Are there any errors in the afsd_init.log?
smime.p7s
Description: S/MIME Cryptographic Signature
