Link to home
Start Free TrialLog in
Avatar of Ashen_Shugar
Ashen_Shugar

asked on

Delphi 6 Client Server Application to Windows 2000 running IIS 5 "Access is denied" when attempting to run client.


We have a client/server application written in Delphi 6 using Midas. All was working fine until the Webserver was recently overhauled and everything reinstalled.

The WebConnection component in the Client shows a list of the available application ServerNames correctly but when changing Connected to True we get the "Access is denied" error and the client program terminates. The Server executable runs on the server and FileMon shows no failed file access on the Server.

I have ran dcomcnfg on the server and changed the identity to my own account (which has admin rights) for testing with no change.

I feel dcom is the problem somewhere, maybe with regards to the IUSR or IWAM account but don't know enough about that side of things.

If you feel this would be better posted in the IIS section I will set up a question there and close this one.

We need the answer quite quickly if possible.



Thx in advance,

Stephen

Avatar of sftweng
sftweng

I do recommend that you post to the IIS forum because it sounds very much like an IIS file permissions problem to me, especially since you appear to have made no changes to the Delphi application.

One way of confirming this would be to run a test with all permissions allowed for everyone made on C:/InetPub/WWWRoot. If this gets rid of the problem, then it will just be a case of finding the right permissions for the IIS user, which will probably be "IUSR.<nodename>".

Alan
ASKER CERTIFIED SOLUTION
Avatar of sftweng
sftweng

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
listening
Avatar of Ashen_Shugar

ASKER


We have a solution of sorts.

After taking the advice of sftweng I discovered that the server was now accessing the 403.3 and 403.1 htm error files when connecting (using FileMon). This suggested to me that anonymous access had somehow become disabled. I spoke to the IT people who set up the server and found out they had attached the server to a Domain Controller. The domain controller enforces its own policy on the server causing problems with the IUSR and IWAM accounts.

Microsoft KB275167 gives the full details. After making the changes in the knowledge base we could get the client-server application working, but not reliably. I have now reinstalled W2K Server and IIS 5 without putting it on the domain. It would appear the IT people here are not quite ready for Servers running Internet applications while on their Domain Controller.

I have given sftweng full points as his advice put me on the right path, and that is good enough for me.



Thx, Stephen
Thank you. I'm pleased to have been able to help.