Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

W2K E2K Global Address List Problem; already checked KB :(

Status
Not open for further replies.

ffanta

Programmer
Apr 7, 2002
3
AT
Hi there,

I usually don't post do forums or newsgroups, because usually I can find all the wisdom needed to solve my little problems, but this time there's not other way than to tell you my problem. Maybe you can help ? (PLEASE ;-))

The network is a small TCP/IP W2K network (W2K pro on the client side, W2K Server on, guess what, the server side). There are 12 users, everyone with his own email-address, everything very simple. And everything worked fine, until a consulting-guy ;) did some technical stuff...

since then, nobody is able to browse the global address list, outlook can not resolve the profile for an e2k-mailbox, and when I try to add an additional profile to an outlook profile, I get the msg "The name could not be resolved..." (at least the german version of it).

I've already checked the following KB-articles:

Q309622
Does not apply, because neither hotfix nor srp1 are installed and RestrictAnonymous-Key is set to 0x0
(BTW: do I have to reboot after changing this key ?)

Q257885
Rebooted Catalog server, no change of behaviour. Server runs as Global Catalog Server.

Q322832
Error message does not really apply to my situation here, but I checked the security settings, and the group "authenticated users" does have read-permission on the AD users list.

Q274668
This article best describes my problem, but I also checked these security settings, and they were correct (Read-Permission set for authenticated Users in the Users-container).

As I said at the beginning, usually I can find solutions from other posts in a forum, and I really don't want to bother you with another "global address list" problem.

But I really can't find a solution to this problem.

Maybe you can open my eyes somehow...

Thanks in advance,
Frounz
 
As far as your question about Q309622 is concerned, yes you do have to reboot after changing the key to 0x0, also, as is the case with us, it will change back during day to day server operation but only seems to affect the GAL if the server is rebooted after it has changed to 2

I hope you find the solution to your particular problem and if anyone has found a way to fix Q309622 permanently please let me know

Kathy
 
Perhaps your consultant has a solution?

Daniel
 
Hi, I had this issue and found that if you change the reg key manually it reverts after a reboot. But if you change the value in the "local security settings-local policies-security options" and set "additional restrictions for annon" to "none" then the reboot won't effect it.

Connan
 
These are the things you always need to do that "always" fix check name.

Verify from ESM that you can browse the GAL. This always works unless users aren't stamper (RUS Problem). Then the article on troubleshooting check name. I don't recall the number exactly. Next the 0x2 needs to be 0x0 on ALL GC's.
Then if it is still broke after a reboot of the GC then make another DC a GC and remove that role from this DC and reboot both DC's.

I have never had a case (worked at least 50) that this didn't resolve the issue. Dan
Microsoft Exchange Support @ Microsoft
 
Thanks for all your answers !

kathanon:
hmm... The reg key stays at 0x0 also after reboot, so I don't really want to touch it... ;)

leinad:
nope... he's on vacation... and please let me say things clear -> he's not MY consultant (god bless :))

Connan:
The reg key doesn't change after reboot, it's 0x0. Thanks anyway...

Xybertron:
I don't have the possibility to setup another DC as a GC at the customers site. But I didn't try to browse the GAL from the ESM. Thanks.

Thanks for your help... I'll post the solution here, if I find the problem (hopefully my account here doesn't expire... ;-))

Frounz
 
Hi.

Okay, the solution wasn't THAT tricky after all... just a security setting (only two users were allowed to browse the GAL) for the GAL was wrong...

Everything is working fine now. Thanks for your help !

Frounz
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top