Highlighted
baedamichi Absent Member.
Absent Member.
2239 views

Login script issues on slow computers

Hi guys

I could really need some help here.

Novell Client 2 SP4 on Windows 7 x64.

I have one Login Script in our eDirectory, which is applied via the containers (OUs) where users reside.

I'm pretty sure my problem doesn't have any server-side issues (such as permissions and such), let me tell you why:

Exactly the same login script for exatly the same eDirectory user runs on some machines, and on some it doesn't (at least not reliably). To simplify things, let's assume I got three types of computers: 1) fast 2) medium speed 3) slow
On the "fast" computers, the login script always runs.
On the "medium" computers, it almost always runs (maybe one login per month where it doesn't).
On the "slow" computers, it almost never runs (a guesstimate would be in 2 out of 100 logins).

Like I said, apart from their hardware, those computers are the same (even installed with the same image through ZenWorks imaging, really, only difference are the drivers I added).

I hope you get why I assume this must be a timing issue of some sort, I just guess on the slow computers the Novell Client runs into a timeout after trying to execute the script and then just doesn't.

Being an admin rather new to Novell, maybe you can help me out a bit with a few things:

1) Where would I find the logs relevant to login scripts and possible errors? I looked into the Windows event log and the folders where the Novell Client is installed, but I found nothing. Maybe I have to enable logging first?

2) Are there any (preferably registry-configurable) ways of making the Novell Client more "patient" (in the sense of just making it wait for server connections and such instead of simply not executing scripts)?

3) Am I completely off the mark with my assumption? Maybe someone with more Novell experience could take a guess why a login script would run on some computers and not on others (repeat: same OS, same user, same server, same context, same OU, same loginscript, computers on same subnet, really, only difference is the computer's hardware).

Thanks a lot!

Peter
Labels (1)
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Login script issues on slow computers

Could be a million things. Most likely name resolution. Can you start
by posting the script for us to look at?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
baedamichi Absent Member.
Absent Member.

Re: Login script issues on slow computers

Thanks for the reply!

Here's the script:

; ==================================================
; Allgemeine Parameter
; ==================================================
pccompatible
map display on
map errors off
NO_DEFAULT

; ==================================================
; Default-Server
; ==================================================

dos set DATASRV="s02"
dos set PROGSRV="s02"

IF <WEBACCESS> = "1"
dos set NetStorage="on"
else

; ==================================================
; Primäre Laufwerke
; ==================================================
; map root h:=%HOME_DIRECTORY
map root p:=\\%<PROGSRV>\DAT\Programme

; ==================================================
; User-Verzeichnisse pruefen und verbinden
; ==================================================
map root s:=%HOME_DIRECTORY\Daten

; ==================================================
; Sonderlaufwerke
; vCEType:
; 431 : Schueler
; 411 : Lehrer
; 421 : Betreuer
; ==================================================

if "%vCEType"="431" then begin
map root m:=\\%<DATASRV>\DAT\FOSBOSMDF
map root k:=\\%<DATASRV>\DAT\FOSBOSMDF\Klassen
map root j:=\\%<DATASRV>\DAT\FOSBOSMDF\Kurse
map root i:=\\%<DATASRV>\DAT\FOSBOSMDF\Projekte
map root z:=\\%<DATASRV>\DAT\Programme\NTDESK
end

if "%vCEType"="411" then begin
map root m:=\\%<DATASRV>\DAT\FOSBOSMDF
map root t:=\\%<DATASRV>\DAT\FOSBOSMDF\Lehrkraefte\_TAUSCH
map root z:=\\%<DATASRV>\DAT\Programme\NTDESK
end

if "%vCEType"="421" then begin
map root h:=%HOME_DIRECTORY
map root m:=\\%<DATASRV>\DAT\FOSBOSMDF
map root o:=\\%<DATASRV>\DAT\
map root t:=\\%<DATASRV>\DAT\FOSBOSMDF\Lehrkraefte\_TAUSCH
end

; ==================================================
; Protokollierung der Anmeldung
; ==================================================

REM Wer meldet sich wo an?
REM 1. Runde: Setzen der Netware-Variablen als Umgebungsvariablen
set jahr=year
set monat=month
set tag=day
set stunde=hour24
set minute=minute
set sekunde=second
set name="%CN"
set cnt="%LOGIN_CONTEXT"
set ln="%FULL_NAME"
set ipaddr="%NETWORK"

REM 2. Runde: Aufruf der login.cmd mit Übergabe der Variablen
write "%<jahr>/%<monat>/%<tag> %<stunde>:%<minute> IP: %<ipaddr> Name: %<name> Context: %<cnt>"
#p:\login\login.cmd %tag% %monat% %jahr% %stunde% %minute% %ipaddr% %name% %cnt% "%ln%"

; ==================================================
; NAL Aufruf
; ==================================================

if OS_VERSION <= "V5.9" then
write "XP erkannt"
@C:\Programme\Novell\ZENworks\nalwin32.exe /C="Anwendungen fuer %FULL_NAME"
end

if OS_VERSION >= "V6.0" then
write "Windows 7 erkannt"
REM 32/64 BIT:
IF <processor_architecture> = "AMD64"
@C:\Progra~2\Novell\ZENworks\bin\nalwin.exe /s /min /C="Anwendungen fuer %FULL_NAME"
else
@C:\Program Files\Novell\ZENworks\bin\nalwin.exe /s /min /C="Anwendungen fuer %FULL_NAME"
end

end
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login script issues on slow computers

OK. First thing that I notice is that you use bindery/UNC-syntax for
mapping. Ie \\server\vol\dir. This will generally only work
fast/reliably if the workstation can do a lookup for the server, in
this case "s02" through DNS.

A better choice would be to use NDS-syntax, ie:

MAP Q:=.server01_vol1.rd.acme:dir

Ie, use the fully qualified NDS-name.

What you can do is to replace s02 with the IP address of the server and
see whether that changes things.

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
baedamichi Absent Member.
Absent Member.

Re: Login script issues on slow computers

Hello again

I replaced the DNS name with the IP address of our OES server, unfortunately, nothing has changed.

I just wonder to which path the Novell Client writes its logfiles?

Cheers and thanks,

Peter
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login script issues on slow computers

Baedamichi,
> I replaced the DNS name with the IP address of our OES server,
> unfortunately, nothing has changed.
>
> I just wonder to which path the Novell Client writes its logfiles?


OK. Then it must be something else? Routing, antivirus. Try looking at packets with Wireshark.

http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7007070

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
baedamichi Absent Member.
Absent Member.

Re: Login script issues on slow computers

Anders Gustafsson;2417082 wrote:
Baedamichi,
> I replaced the DNS name with the IP address of our OES server,
> unfortunately, nothing has changed.
>
> I just wonder to which path the Novell Client writes its logfiles?


OK. Then it must be something else? Routing, antivirus. Try looking at packets with Wireshark.

http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=7007070

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms


Okay, I'm back after the weekend. 🙂

It would surprise me if it were routing or Antivirus, you see, one of the slow computers is sitting right next to one of the fast ones, in the same room, so they're connected to the network on the same switch. But just to make sure, I carried the slow computer down to the basement and hooked it to the same switch on which the server is, didn't help either.

Also, with regard to Antivirus, all of our systems have Sophos installed (same policies et for both the slow and fast computers in Sophos Enterprise Console), so I don't think that i's that either. But just to test, I uninstalled Sophos from one of the slow computers, no luck either.

Thanks for the link, now I at least know where to find the logs and how to enable enhanced debug logging (or whatever it's called), I put some here:

https://www.dropbox.com/sh/mfvyrbvdl2sf1rd/AACQHQXorTWM187qGG10EDpsa?dl=0

Also, I tried replacing the Novell Client 2 SP4 on one of the slow computers with the Novell Client 2 SP4 IR1, didn't change anything either.

I put some logs online (theses are taken from when the Novell Client 2 SP4 IR1 was installed:

https://www.dropbox.com/sh/udo1xz8svhuyona/AAAbbg-q297vjXZKNHY0k03na?dl=0

I still think this must be some timing issue of some sorts. You see, it is not like the slow clients cannot find the server at all, once login has completed (unfortunately without the login scripts being run), I can perfectly well manually map NSS network locations (with "net use"), and they work as expected with the logged on user's rights, so the connection to the server seems to be fine, it's just that it seems there's no connection initially, when the machine tries to run the login scripts.

I came across one line which interested me, it's line 107 in NCCredProvider-0002.log (first link, the one without IR1):

[NCCredProvider-AE4][14:36:37.663] CNetwork::xplatInit Windows running for 253 seconds; longer than boot threshold of 240 seconds. Use timeout of 0 seconds.

To somebody who's new to Novell and with only Windows experience, this seems to me the Novell Client is "complaining" about a computer which is too slow. And what does "use timout of 0 seconds" mean? That it will wait indefinitely (whenever I was dealing with timeouts in Windows (for instance when you set how long GPO scripts are supposed to run), 0 usually means "no timeout at all, client waits indefinitely") or is the 0 to be taken literally? The latter wouldn't really make sense, as if a slow computer is detected, there should be a longer wait until a timeout occurs, right?

What also seems interesting is lines 447 and 448:

[NCCredProvider-AE4][14:36:44.199] CNetwork::LoginStart() called, but login thread is already running.
[NCCredProvider-AE4][14:36:44.199] [1] CCredential::Connect [0] LoginStart() returned status 0x8007139F.

Is there some sort of database where these codes (like 0x8007139F) are explained? I googled it, and came up with quite some results for Windows Defender, but none for the Novell Client.

Anyway, I'll try to look at it with Wireshark, but it would be a lot of help if somebody could tell me what to look for exactly?

Thanks a lot!

Peter
0 Likes
baedamichi Absent Member.
Absent Member.

Re: Login script issues on slow computers

Oh, one more question, I was just thinking of a workaround: Is it possible to use the Novell Client as a script engine in general, i.e. apart from having it execute login scripts stored directly as an eDirectory object? I was thinking of putting my login script in a text file, and sort of make a ZenWorks Bundle that is set to be started on Logon (maybe with a 30 seconds delay)? So, is it possible to have the Novell Client execute scripts stored as a file?
0 Likes
baedamichi Absent Member.
Absent Member.

Re: Login script issues on slow computers

Hi again!

I was able to resolve my issue, also thanks to being told here where the Novell Client stores its log files.

The cause was that on my machines, Adobe CS4 is installed. Even though I didn't install Adobe Drive CS4, the installer still installed a network provider called Adobe CS4, and put it first in the network providers order in the registry. So all I had to do to fix the issue was to change the registry keys

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order\ProviderOrder

and

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder\ProviderOrder

from

AdobeDriveCS4_NP,ZenCredManager,LCredMgr,NCFSD,RDPNP,LanmanWorkstation,webclient,iPrntWinCredMan

to

ZenCredManager,LCredMgr,NCFSD,RDPNP,LanmanWorkstation,webclient,iPrntWinCredMan,AdobeDriveCS4_NP

Now, all machines execute the loging script as expected.

I want to thank Anders Gustafsson for his help!

Cheers,

Peter
0 Likes
Knowledge Partner
Knowledge Partner

Re: Login script issues on slow computers

In article <baedamichi.79pdlc@no-mx.forums.microfocus.com>, Baedamichi
wrote:
> Is there some sort of database where these codes (like 0x8007139F) are
> explained? I googled it, and came up with quite some results for Windows
> Defender, but none for the Novell Client.

They should be up in https://www.novell.com/documentation/nwec/
but in this case they don't seem to have made it up there. I suspect that
the thinking was that the logs you were seeing weren't intended for anyone
outside development and support.

>
> Anyway, I'll try to look at it with Wireshark, but it would be a lot of
> help if somebody could tell me what to look for exactly?

Generally you are looking for the flow of when what lookups have happened.
In your case you may well have seen the Adobe CS4 provider style lookups
before the Novell style. Experience with periodic packet analysis is what
it takes to get the feel for these things, and given how you tacked this
issue I think you would do well even if you just played with it a bit.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Knowledge Partner
Knowledge Partner

Re: Login script issues on slow computers

In article <baedamichi.79pein@no-mx.forums.microfocus.com>, Baedamichi
wrote:
> Is it
> possible to use the Novell Client as a script engine in general, i.e.
> apart from having it execute login scripts stored directly as an
> eDirectory object? I was thinking of putting my login script in a text
> file, and sort of make a ZenWorks Bundle that is set to be started on
> Logon (maybe with a 30 seconds delay)? So, is it possible to have the
> Novell Client execute scripts stored as a file?

Sort of. You need a script to at least initiate within eDir, but then
you can use the include command in a number of ways either to have
system wide scripts within eDir or even as files.
https://www.novell.com/coolsolutions/feature/16744.html
Calling batch (.BAT) files is also a common thing since before Windows.

Thank you for posting your findings so clearly. This will help others.


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.