On Thu, Jan 1, 2009 at 12:00 PM, Jeffrey Altman <
[email protected]> 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

Reply via email to