The network provider registry changes have been applied. Directory replication is not used; changes to NETLOGON scripts are manually copied and all are identical. Yes we do have the Novell Client 32 (read kiss of death) I think it's version 2.5.

I initially thought my problem was with the KIXTART.INI entries. Should the domains be prefixed with '\\'? as per your mail? the kixtart manual doesn't show domains prefixed in such a way.

I also think the KIXTART.INI entries mean workgroup as well as domain.

To expand on the detail already posted, I have two domains - 'BMCEN01' is an account domain and 'BMFIN02' is a resource domain. The Windows 95 PCs have their workgroup (in Network Properties) set to 'BMFIN02' and their computer names are FIN02CWxxxx where xxxx is a sequence number.

The logon script seems to work more reliably when the workgroup is set to BMCEN01 (i.e. the same name as the domain to which they're logging on) instead of BMFIN02. When the workgroup is set to BMFIN02 , the PDC of the BMFIN02 domain, \\FIN02PC seems to be the RPC server ( @RSERVER = \\FIN02PC ) even though this is not mentioned in the KIXTART.INI file located in the NETLOGON share of the BMCEN01 domain controllers (\\CEN01PC, \\CEN01BCIIS01 and \\CEN01BCEXC01 respectively). I've not used the registry setting for the RPC server, nor used the environment variable. In this case, INGROUP('xxx') sometimes work during the logon script, but never work once logged on as the script is looking at groups in the BMFIN02 domain.

Up until tonight, the \\FIN02PC server wasn't running the KXRPC service however it's neither more or less reliable with the service running on this server. At the moment, it's stopped.

I will probably specify 'BMCEN01' as the workgroup name instead of 'BMFIN02' even though this breaks the naming standard.

Do you think I'm barking up the wrong tree here?

Ian.