If I log in as a local user, the "LSA Principal logon user" and
"WNetAddConnection2" lines don't show up, and there is no delay -
though I only tried this once. If I'm logged in as a domain user,
the delay happened before the first "WNetAddConnection2" line. This
isn't isolated to just this computer - I've heard of other
departments on campus seeing the delay. It doesn't seem to break
things, its just....a short delay. :) Also, It doesn't seem to
matter if the domain account has a kerberos name mapping in place or
not.
I wonder if there is a way to log whatever is happening during that
pause.
- Robbie
On Sep 14, 2006, at 7:45 PM, Gurganus, Brant L wrote:
Robbie, does this only occur for Windows domain-joined accounts as
it does
for me? I tried asking the helpdesk at my school if they knew of
anything in
the environment that could cause this, but they dismissed it
because I am
using a setup that they do not support.
-----Original Message-----
From: Robbie Foust [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 14, 2006 5:42 PM
To: Jeffrey Altman
Cc: Gurganus, Brant L; [email protected]
Subject: Re: [OpenAFS] context menu handler slow in OpenAFS 1.5.8 for
Windows
Hi,
I'm seeing the exact same thing. Have been for a long time, but
never had proof it was the AFS client causing the right-click delay.
I could send screen shots but its the same behavior already posted
here. I've confirmed it using the pioctl debugging and fs whereis
"my documents" command. I'm using v1.4.1 on a Windows 2003 advanced
terminal server.
Thanks,
- Robbie
On Sep 13, 2006, at 10:23 PM, Jeffrey Altman wrote:
There is nothing wrong with using drive mappings.
My guess is that there is something wrong because the SamCompatible
name is not a prefix of the full Domain Name.
Lots of sites use domain logins without any delays. So its something
unusual about your environment.
Jeffrey Altman
Gurganus, Brant L wrote:
Another potential contributing factor is that domain logon scripts
automatically map AFS paths to drive letters, so I am not sure if
I can
prevent those mappings from occurring and see what happens then.
-----Original Message-----
From: Jeffrey Altman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 9:56 PM
To: Gurganus, Brant L
Cc: [email protected]
Subject: Re: [OpenAFS] context menu handler slow in OpenAFS 1.5.8
for
Windows
What if you login with:
[EMAIL PROTECTED]
Gurganus, Brant L wrote:
Actually, I was wrong about the delay, I was just trying soon after
login when those results were still cached. The output is different
though:
C:\Documents and Settings\gurganbl>fs whereis "My Documents"
pioctl CreateFile(C:\_._AFS_IOCTL_._) failed: 0x2
[The system cannot find the file specified.
]
pioctl Explorer logon user: [MSROSE-HULMAN\gurganbl]
pioctl CreateFile(C:\_._AFS_IOCTL_._) failed: 0x2
[The system cannot find the file specified.
]
pioctl LSA Principal logon user: [EMAIL PROTECTED]
pioctl WNetAddConnection2(\\afs,[EMAIL PROTECTED])
failed:
0x4C3
pioctl WNetAddConnection2(\\afs\all,[EMAIL PROTECTED])
failed:
0x4C3
pioctl SamCompatible logon user: [MSROSE-HULMAN\gurganbl]
pioctl CreateFile(C:\_._AFS_IOCTL_._) failed: 0x2
[The system cannot find the file specified.
]
fs: Invalid argument; it is possible that My Documents is not in
AFS.
The delay occurs after the first WNetAddConnection2 call in the
case
of
both login forms.
-----Original Message-----
From: Jeffrey Altman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 9:28 PM
To: Gurganus, Brant L
Cc: [email protected]
Subject: Re: [OpenAFS] context menu handler slow in OpenAFS 1.5.8
for
Windows
ok. What is the pioctl output when using that name form?
Gurganus, Brant L wrote:
With that information, if I login with MSROSE-HULMAN\gurganbl
instead
of
[EMAIL PROTECTED], I do not experience the delay.
-----Original Message-----
From: Jeffrey Altman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 8:29 PM
To: Gurganus, Brant L
Cc: [email protected]
Subject: Re: [OpenAFS] context menu handler slow in OpenAFS
1.5.8 for
Windows
There you go. Its taking pioctl() many tries before it can
find the name form that matches the authentication name used
to login the session. This name is required in order for
authentication to the AFS SMB server to succeed since that is
the only name that will be accepted over the loopback interface.
I don't have a solution for you. The real fix for this is to
stop using an SMB server and instead begin use of a Network
Redirector. Completing this work is a long time off.
Jeffrey Altman
Gurganus, Brant L wrote:
I turned on the pioctl debugging as you suggested and these
were the
results. This is a domain-joined limited user account.
0x4c3 is:
ERROR_SESSION_CREDENTIAL_CONFLICT
1219
Multiple connections to a server or shared resource by the same
user,
using more than one user name, are not allowed. Disconnect all
previous
connections to the server or shared resource and try again.
C:\Documents and Settings\gurganbl>fs whereis "My Documents"
pioctl CreateFile(C:\_._AFS_IOCTL_._) failed: 0x2
[The system cannot find the file specified.
]
pioctl Explorer logon user: [EMAIL PROTECTED]
pioctl WNetAddConnection2(\\afs,[EMAIL PROTECTED]) failed:
0x4C3
pioctl WNetAddConnection2(\\afs\all,[EMAIL PROTECTED])
failed:
0x4C3
pioctl LSA Principal logon user: [EMAIL PROTECTED]
pioctl WNetAddConnection2(\\afs,[EMAIL PROTECTED])
failed:
0x4C3
pioctl WNetAddConnection2(\\afs\all,[EMAIL PROTECTED])
failed:
0x4C3
pioctl SamCompatible logon user: [MSROSE-HULMAN\gurganbl]
pioctl CreateFile(C:\_._AFS_IOCTL_._) failed: 0x2
[The system cannot find the file specified.
]
fs: Invalid argument; it is possible that My Documents is not in
AFS.
C:\Documents and Settings\gurganbl>fs whereis "My Documents"
pioctl CreateFile(C:\_._AFS_IOCTL_._) failed: 0x2
[The system cannot find the file specified.
]
pioctl Explorer logon user: [EMAIL PROTECTED]
pioctl WNetAddConnection2(\\afs,[EMAIL PROTECTED]) failed:
0x4C3
pioctl WNetAddConnection2(\\afs\all,[EMAIL PROTECTED])
failed:
0x4C3
pioctl LSA Principal logon user: [EMAIL PROTECTED]
pioctl WNetAddConnection2(\\afs,[EMAIL PROTECTED])
failed:
0x4C3
pioctl WNetAddConnection2(\\afs\all,[EMAIL PROTECTED])
failed:
0x4C3
pioctl SamCompatible logon user: [MSROSE-HULMAN\gurganbl]
pioctl CreateFile(C:\_._AFS_IOCTL_._) failed: 0x2
[The system cannot find the file specified.
]
fs: Invalid argument; it is possible that My Documents is not in
AFS.
-----Original Message-----
From: Jeffrey Altman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 6:37 PM
To: Gurganus, Brant L
Cc: [email protected]
Subject: Re: [OpenAFS] context menu handler slow in OpenAFS 1.5.8
for
Windows
Turn on pioctl() debugging (as per the debugging section of the
OpenAFS Release Notes), and then run the "fs whereis" test again.
I suspect you will find the problem is that your systems are
having
a
hard time authenticating to the AFS Client Service. In which
case
all operations to AFS are suffering the same delays
Jeffrey Altman
Gurganus, Brant L wrote:
The delay characteristics are reproducible using the command you
mentioned. If it is newly run, there is a delay. If it has
recently
ran
(probably has results in a cache), then it finishes quickly.
There appears to be no difference in output of the command when
there
is
a delay and when there is not a delay:
C:\DOCUME~1\gurganbl>fs whereis "My Documents"
fs: Invalid argument; it is possible that My Documents is not in
AFS.
C:\DOCUME~1\gurganbl>fs whereis "My Documents"
fs: Invalid argument; it is possible that My Documents is not in
AFS.
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
