[OpenAFS] Problem with OpenAFS on Vista x86
Paul Accisano
shiningmasamune@gmail.com
Thu, 1 Jan 2009 12:36:48 -0500
------=_Part_92071_26360753.1230831408997
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Thu, Jan 1, 2009 at 12:00 PM, Jeffrey Altman <
jaltman@secure-endpoints.com> wrote:
> Paul Accisano wrote:
>
> > \\afs\uncc.edu is indeed accessible before I VPN. But after I VPN,
> > \\afs becomes inaccessible. And I did wait a full 5 minutes after
> > VPN'ing before trying to access \\afs, to wait for any name binding
> > magic to finish.
>
> What is the output of "nbtstat -n" after the VPN connection?
>
> What is listed in the %windir%\temp\afsd_init.log file?
>
>
>
Ahah, now we're getting somewhere. This is the tail end of afsd_init.log.
1/1/2009 12:16:24 PM: Netbios NCBADDNAME lana=9 code=0 retcode=0 complete=0
1/1/2009 12:16:24 PM: Netbios NCBADDNAME added new name >AFS <
1/1/2009 12:16:24 PM: Netbios NCBADDNAME succeeded on lana 9
1/1/2009 12:16:24 PM: smb_NetbiosInit smb_LANadapter=9
1/1/2009 12:16:24 PM: MsV1_0SetProcessOption success
1/1/2009 12:16:24 PM: Setting SMB server domain name to [MAHOKA]
1/1/2009 12:16:24 PM: smb_StartListeners
1/1/2009 12:16:24 PM: smb_Init complete
1/1/2009 12:16:24 PM: GlobalAutoMap thread completed
1/1/2009 12:16:24 PM: Windows Firewall Configuration succeeded
1/1/2009 12:18:14 PM: smb_LanAdapterChange
1/1/2009 12:18:14 PM: NCBLISTEN lana=9 failed with NRC_BRIDGE, retrying ...
1/1/2009 12:18:14 PM: NCBLISTEN lana=9 failed with NRC_NOWILD, retrying ...
1/1/2009 12:18:35 PM: smb_LanAdapterChange
1/1/2009 12:18:35 PM: NCBLISTEN lana=9 failed with NRC_BRIDGE, retrying ...
1/1/2009 12:18:35 PM: NCBLISTEN lana=9 failed with NRC_NOWILD, retrying ...
1/1/2009 12:18:39 PM: smb_LanAdapterChange
1/1/2009 12:18:39 PM: NCBLISTEN lana=9 failed with NRC_BRIDGE, retrying ...
1/1/2009 12:18:39 PM: NCBLISTEN lana=9 failed with NRC_NOWILD, retrying ...
I VPN'd at 12:18:14, right when it starts failing. Here's the nbtstat -n
output for the VPN adapter:
VPN Adapter:
Node IpAddress: [128.235.18.39] Scope Id: []
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
MAHOKA <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
WORKGROUP <1E> GROUP Registered
MAHOKA <20> UNIQUE Registered
WORKGROUP <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered
Finally, here's an extremely telling bit of information: not only do I lose
access to \\afs when I connect to VPN, but I also lose access to all other
comptuers on my network except the only other one that's running Vista.
What's more, I don't regain access even when I disconnect from VPN!
Rebooting seems to be the only cure after I've connected to VPN once.
Unfortunately, this suggests to me that it's some kind of Vista --><-- VPN
conflict, which means I'm getting outside of your area of expertise here...
Any ideas?
--Paul
------=_Part_92071_26360753.1230831408997
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Thu, Jan 1, 2009 at 12:00 PM, Jeffrey Altman <span dir="ltr"><<a href="mailto:jaltman@secure-endpoints.com">jaltman@secure-endpoints.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Paul Accisano wrote:<br>
<br>
> \\afs\<a href="http://uncc.edu" target="_blank">uncc.edu</a> is indeed accessible before I VPN. But after I VPN,<br>
> \\afs becomes inaccessible. And I did wait a full 5 minutes after<br>
> VPN'ing before trying to access \\afs, to wait for any name binding<br>
> magic to finish.<br>
<br>
</div>What is the output of "nbtstat -n" after the VPN connection?<br>
<br>
What is listed in the %windir%\temp\afsd_init.log file?<br>
<br>
<br>
</blockquote></div><br><br>Ahah, now we're getting somewhere. This is the tail end of afsd_init.log.<br><br>1/1/2009 12:16:24 PM: Netbios NCBADDNAME lana=9 code=0 retcode=0 complete=0<br>1/1/2009 12:16:24 PM: Netbios NCBADDNAME added new name >AFS <<br>
1/1/2009 12:16:24 PM: Netbios NCBADDNAME succeeded on lana 9<br><br>1/1/2009 12:16:24 PM: smb_NetbiosInit smb_LANadapter=9<br>1/1/2009 12:16:24 PM: MsV1_0SetProcessOption success<br>1/1/2009 12:16:24 PM: Setting SMB server domain name to [MAHOKA]<br>
1/1/2009 12:16:24 PM: smb_StartListeners<br>1/1/2009 12:16:24 PM: smb_Init complete<br>1/1/2009 12:16:24 PM: GlobalAutoMap thread completed<br>1/1/2009 12:16:24 PM: Windows Firewall Configuration succeeded<br>1/1/2009 12:18:14 PM: smb_LanAdapterChange<br>
1/1/2009 12:18:14 PM: NCBLISTEN lana=9 failed with NRC_BRIDGE, retrying ...<br>1/1/2009 12:18:14 PM: NCBLISTEN lana=9 failed with NRC_NOWILD, retrying ...<br>1/1/2009 12:18:35 PM: smb_LanAdapterChange<br>1/1/2009 12:18:35 PM: NCBLISTEN lana=9 failed with NRC_BRIDGE, retrying ...<br>
1/1/2009 12:18:35 PM: NCBLISTEN lana=9 failed with NRC_NOWILD, retrying ...<br>1/1/2009 12:18:39 PM: smb_LanAdapterChange<br>1/1/2009 12:18:39 PM: NCBLISTEN lana=9 failed with NRC_BRIDGE, retrying ...<br>1/1/2009 12:18:39 PM: NCBLISTEN lana=9 failed with NRC_NOWILD, retrying ...<br>
<br>I VPN'd at 12:18:14, right when it starts failing. Here's the nbtstat -n output for the VPN adapter:<br><br>VPN Adapter:<br>Node IpAddress: [128.235.18.39] Scope Id: []<br><br> NetBIOS Local Name Table<br>
<br> Name Type Status<br> ---------------------------------------------<br> MAHOKA <00> UNIQUE Registered<br> WORKGROUP <00> GROUP Registered<br> WORKGROUP <1E> GROUP Registered<br>
MAHOKA <20> UNIQUE Registered<br> WORKGROUP <1D> UNIQUE Registered<br> ..__MSBROWSE__.<01> GROUP Registered<br><br><br>Finally, here's an extremely telling bit of information: not only do I lose access to \\afs when I connect to VPN, but I also lose access to all other comptuers on my network except the only other one that's running Vista. What's more, I don't regain access even when I disconnect from VPN! Rebooting seems to be the only cure after I've connected to VPN once. Unfortunately, this suggests to me that it's some kind of Vista --><-- VPN conflict, which means I'm getting outside of your area of expertise here... Any ideas?<br>
<br>--Paul<br>
------=_Part_92071_26360753.1230831408997--