469,645 Members | 1,941 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

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

Active Directory Services cannot find the web server

Hello Everyone,
I am hoping someone could help me out with this.I am using Visual
Studio .NET 2003 to create a web application on a remote IIS 5.0
server using the File Share web access method.The problem is I get the
following two errors everytime I try to create the application:

Error 1:
The web was created successfully, but an error occured trying to
configure the application root of this web.Web projects may not
operate correctly without an application root.The returned error
was"Active Directory Services cannot find the web server.A possible
cause of this is an incompatibility between versions of Internet
Information Server(IIS) on the client and the server.The usual cause
for this error is creating web projects on a windows 2000 or newer
server from a windows NT 4.0 client.
You can manually configure the application using the Internet Services
Manager.

Error 2:
Unable to set the permissions on the 'bin' folder to restrict browse
access.Active Directory Services cannot find the web server.A possible
cause of this is an incompatibility between versions of Internet
Information Server(IIS) on the client and the server.The usual cause
for this error is creating web projects on a windows 2000 or newer
server from a windows NT 4.0 client.
You can manually configure the application using the Internet Services
Manager.

Now I have read the article related to these errors on microsoft at
this address:
http://support.microsoft.com/?id=320451

And true to its word,the solution that the article suggests resolves
the above mentioned errors i.e. If I install IIS on the client
machine,the errors are eliminated.But,we don't want to install IIS on
all the client machines which will be used to create a web application
on the remote server.We feel there is a security issue with doing
this.Is there any way to get around the above mentioned errors without
having to install IIS on all the client machines? I would really
appreciate it if someone could help me out with this.Thanks in
advance,do reply.

Amol.
Jul 21 '05 #1
0 3267

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Andrew | last post: by
reply views Thread by Amol Shambharkar | last post: by
2 posts views Thread by Jim in Arizona | last post: by
5 posts views Thread by Kaamp | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.