Our domain architecture is solid. Three separate people here have verified the failures. We are setup using a master model.
#1
W2K pro -> W2K DC -> NT4 BDC1
#2
W2K pro -> NT4 DC -> NT4 BDC2
The third is the same as #2
The 4.01 INGROUP function works for existing groups that have been around for a while. Did you create a new global group and try it? As stated when this problem was brought to my attention I tried some of my existing groups with INGROUP and they all worked. I then added my self to the group that was brought to my attention and it failed. I then tried multiple other groups. They all failed. I used Kix32 3.62 and they all worked. BAck to 4.01 and the new groups failed while older group worked. I then went to ENUMGROUP just to see what happened. All the groups that worked with INGROUP were displayed. The ones that INGROUP report I was not a member of were not listed.
After adding my account I forced a complete domain syncronization and validated all were "IN SYNC" with "NLTEST.exe /BDC_QUERY".
How big is your domain? Could size/timing be an issue?
[ 17 January 2002: Message edited by: Howard Bullock ]