First off -
 Code:
DEBUG=Y
in the header section of Login.ini is not valid. Please delete it. The parameter is supported, but not with a Y/N value, so the result may be unpredictable. It's only used for our internal testing.

Second, the
 Code:
AllowedDomains=DM001
DeniedDomains=ThatTrustedDomain
values are only used when you have interdomain trusts, and you log in to a foreign domain using trusted credentials and don't want the login script to run. Even in that case, only one line should be used. Comment both lines out.

It looks like you fixed your resource records per my earlier email, so lets look at your logindebug file:

Updating cache... Your local ini file was missing or outdated, the cached copy was updated
=========================================================
2009/07/27 - 07:56:59
Kixtart: 4.53
Version: 2.6.2a
User: Bart Dirkx
LoginServer: \\DC-138
Domain: DM001
OU String: OU=VW,OU=Administrators,DC=dm001,DC=net,DC=local
OU Offset: 1
User OU: Administrators
Logon Mode: 0 You manually ran the login script
Detected O/S: Windows XP Professional / Version 5.1
Privelege: USER
ScriptDir: C:\KIX your script & kix32 folder path
StartDir: C:\KIX
Language: 0
Session Type: Console

Since you're running from C:\Kix, make sure that "debug.txt" does not exist in that folder. This will force debug level 2, which will not map any drives.


Processing IBB Kondor 1
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1 result of authoriZation logic
No MANDATORY membership, No INVERSE MEMBERSHIP, No INVERSE ACTION, IN-GROUP is TRUE
Member of allowed group GS_IBB_Kondor_ACAD - continuing.
Logic: AND, Value: 2, Required: 2 Must meet GROUP and OU requirements!
(No OU requirement, so that defaults to OK)
OK to process this resource!
Check for path and description translations - none found!
MVLookup: \\dc-034\netapps$
Translated: \\dc-034\netapps$
MVLookup: Netapps
Translated: Netapps

Processing IBB Kondor 2
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1
Member of allowed group GS_IBB_Kondor_ACAD - continuing.
Logic: AND, Value: 2, Required: 2
OK to process this resource! This indicates that the resource can be mapped
MVLookup: \\dc-034\USR$\&USER&
Translated: \\dc-034\USR$\AdminWPBDX
Note that the above path was translated to the username!
MVLookup: USERSHARE AUTOCAD
Translated: USERSHARE AUTOCAD

Processing IBB Kondor 3
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1
Member of allowed group GS_IBB_Kondor_ACAD - continuing.
Logic: AND, Value: 2, Required: 2
OK to process this resource!
MVLookup: \\dc-034\acad$
Translated: \\dc-034\acad$
MVLookup: Autocad
Translated: Autocad

Processing IBB Kondor 4
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1
Member of allowed group GS_IBB_Kondor_ACAD - continuing.
Logic: AND, Value: 2, Required: 2
OK to process this resource!
MVLookup: \\DC-034\ACAD DIRECT$
Translated: \\DC-034\ACAD DIRECT$
MVLookup: AUTOCAD SYNCHRONISATIE
Translated: AUTOCAD SYNCHRONISATIE

Four resources from the IBB Kondor group were authorized

Processing Bebouw 1
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1
Member of allowed group GS_Bebouw_ACAD - continuing.
Logic: AND, Value: 2, Required: 2
OK to process this resource!
MVLookup: \\dc-073\netapps$
Translated: \\dc-073\netapps$
MVLookup: Netapps
Translated: Netapps

Processing Bebouw 2
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1
Member of allowed group GS_Bebouw_ACAD - continuing.
Logic: AND, Value: 2, Required: 2
OK to process this resource!
MVLookup: \\dc-073\USR$\&USER&
Translated: \\dc-073\USR$\AdminWPBDX
MVLookup: USERSHARE AUTOCAD
Translated: USERSHARE AUTOCAD

Processing Bebouw 3
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1
Member of allowed group GS_Bebouw_ACAD - continuing.
Logic: AND, Value: 2, Required: 2
OK to process this resource!
MVLookup: \\dc-073\acad$
Translated: \\dc-073\acad$
MVLookup: Autocad
Translated: Autocad

Processing Bebouw 4
Eval: 1, Man: 0, IM: 0, IA: 0, InG: 1
Member of allowed group GS_Bebouw_ACAD - continuing.
Logic: AND, Value: 2, Required: 2
OK to process this resource!
MVLookup: \\DC-073\ACAD DIRECT$
Translated: \\DC-073\ACAD DIRECT$
MVLookup: AUTOCAD SYNCHRONISATIE
Translated: AUTOCAD SYNCHRONISATIE

Four resources from the Van Atmaal group were authorized.
The remaining resources were all declined because you aren't a member of the group that is allowed to access them. I've trimmed all but one of these messages.

Processing Van Atmaal 1
Eval: 0, Man: 0, IM: 0, IA: 0, InG: 0
No match in allowed group GS_Van Agtmaal_ACAD - ignored.

Here is where I see a problem.. You are authorized to map to two different sets of resources. The first set connects to DC-034, and the second set to DC-073. You were authorizd to use 8 different resources, yet only 5 show that they will be mapped. This is because 3 of the 4 have the same target drive letter. You haven't set a PRIORITY value, so the second (last) resource to be authorized will be the one that maps.

This is the list of resources that should be mapped.
Processing active resources:
Disk: F \\dc-073\netapps$
Disk: G \\dc-073\USR$\AdminWPBDX
Disk: M \\dc-034\acad$
Disk: N \\dc-073\acad$
Disk: O \\DC-073\ACAD DIRECT$

Part of the problem here may be due to the fact that you are a member of both groups, which may not be the case for other users. If you have two resource records with the same target (drive letter), obviously only one can be mapped. The resource record can have a PRIORITY value to determine which one to map. Alternatively, you need to use other methods, such as OUS or more complex group definitions (GROUPS=+,autocad,site1 for one, GROUPS=+,Autocad,site2 for the other) to handle the authorization process.

Post your updated login.ini file and a copy of the login messages. Explain how you want the mappings to work and we'll fine-tune your config file. You may need to explain your AD groups or OUs - you can PM that to me instead of publishing them here..

Glenn
_________________________
Actually I am a Rocket Scientist! \:D