469,920 Members | 2,261 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,920 developers. It's quick & easy.

Do you need Framework 1.1 to access Active Directory objects on a Windows 2003 server with ASP.NET?

Some of our developers are having a problem making certain code work
that reads the contents of OUs in our Active Directory. It reads fine
when querying a 2000 domain controller but when accessing a 2003
server, it gets errors ranging from Item not found to "Unable to
access directory services". The second I take the 2003 server offline,
everything works fine again.

I can't really give much code detail since i work on the network side
of things, but I'd like to try and help them out since until they fix
this, my deployment of 2003 is stalled. Right now it's a low priority
item for them and truthfully, we could live for a long time with just
2000 but I really want to get some of the new 2003 features running to
make my job easier, so any help I can give them would be great.

I just had the idea that maybe 2003 is requiring changes made by
framework 1.1 and since all the ASP.NET servers only use 1.0, maybe
that changes the way LDAP queries are done?
Nov 17 '05 #1
1 1827
CT
I'm only guessing here, but I would think it's the LDAP query and not the
Framework.

--
Carsten Thomsen
Enterprise Development with Visual Studio .NET, UML, and MSF
http://www.apress.com/book/bookDisplay.html?bID=105
"Michael" <op*****@ihomeowner.com> wrote in message
news:66**************************@posting.google.c om...
Some of our developers are having a problem making certain code work
that reads the contents of OUs in our Active Directory. It reads fine
when querying a 2000 domain controller but when accessing a 2003
server, it gets errors ranging from Item not found to "Unable to
access directory services". The second I take the 2003 server offline,
everything works fine again.

I can't really give much code detail since i work on the network side
of things, but I'd like to try and help them out since until they fix
this, my deployment of 2003 is stalled. Right now it's a low priority
item for them and truthfully, we could live for a long time with just
2000 but I really want to get some of the new 2003 features running to
make my job easier, so any help I can give them would be great.

I just had the idea that maybe 2003 is requiring changes made by
framework 1.1 and since all the ASP.NET servers only use 1.0, maybe
that changes the way LDAP queries are done?

Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Jim in Arizona | last post: by
8 posts views Thread by David Thielen | last post: by
7 posts views Thread by CoolBreeze812 | last post: by
dmjpro
3 posts views Thread by dmjpro | last post: by
13 posts views Thread by dancer | last post: by
1 post views Thread by Waqarahmed | last post: by
reply views Thread by Salome Sato | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.