My sincere apologies, your suggestion was correct – it was the NTFS
permissions. Unfortunately while ‘trying out’ your suggestions I was usi
ng a
Windows Server 2003 computer (one I could ‘Remote Desktop’ into from hom
e),
and unlike the Windows XP box I was testing with this afternoon, Server 03
sets all the security to high – meaning that my webserver was not being
classed as ‘Local Intranet’ by default (I was lucky to notice this). A
combination of these two factors has now resulted in a successful
authentication – and I thank you very much for your assistance!

Cheers,

G. Sharp


"G. Sharp" wrote:
[vbcol=seagreen]
> Thanks for your response. I have made sure all of those things are set (al
l
> but NTFS authentication had been set - and this hasn't made a difference
> anyway - although good to keep in mind). I'm not quite sure you understand
 my
> exact problem - the WebServer is part of the Domain, but not a Domain
> Controller. Therefore as far as I can tell: all the clients are trying to
> authenticate against the webservers local user accounts (eg. Administrator
> password different on DC & Webserver - therefore authentication fails, and
> all the students/teachers are obviously not on the local machine - there o
n
> the Domain).
> When the user enters in their username in the DOMAIN\USERNAME format - the
re
> are no problems. The problem is: I want the authentication to happen
> automatically - I need the webserver to try the Domain as well as the Loca
l
> Machine.
> This confuses me... Does everyone out there have their Webserver running o
n
> a Domain Controller (If this is the case - authentication is seamless)?
> Surely others have required their sort of authentication on a stand-alone
> webserver.
> If there is no solution - I will simply make the webserver a DC - but didn
't
> really want to...
>
> I would really appreciate any comments.
>
> Cheers,
>
> G. Sharp
>
>
> "Miha Pihler [MVP]" wrote:
> 

[ Post a follow-up to this message ]