M
musosdev
Hi guys
Wonder if you could help me out with some security issues I'm having
installing my code on a client's network.
Here's the setup. We've got 2 servers, the first (DC) is a Win2k3 Std
machine running as a domain controller, with Active Directory, etc - and IIS6.
IIS is running an Intranet app, which is setup to use IWA security, and is
running in it's own AppPool on .net framework 2.
The second server (DSQL) is not a DC, but is connected to the network. This
machine is running SQL Server Express, which has the database for the
Intranet app running on the DC. It also had all the user created data for the
Intranet (files generated by the Intranet app).
The SQL side works fine - we got the 2 machines talking and using a specific
account so that, whoever logs in to a client pc and visits the Intranet - it
can connect to the sql and works fine.
The problem is the data folder.
In IIS on DC, we created a virtual directory called IntranetShare, which we
pointed at "\\dsql\IntranetShare", which is a network share coming from DSQL
(C:\Intranet Data" to be precise).
Here's the problem, even though the IIS has Integrated Windows
Authentication, whenever our Intranet tries to load anything from
/IntranetShare/ (ie \\dsql\intranetshare) - windows gives us a "Connect to
server" login box, asking for username and password. Not only that, but even
if you do login, it won't accept the credentials, and just keeps asking to
login.
I'm guessing it's permissions/security - but I'm lost. What have we
missed?!!!?
Thanks in advance!
Dan
Wonder if you could help me out with some security issues I'm having
installing my code on a client's network.
Here's the setup. We've got 2 servers, the first (DC) is a Win2k3 Std
machine running as a domain controller, with Active Directory, etc - and IIS6.
IIS is running an Intranet app, which is setup to use IWA security, and is
running in it's own AppPool on .net framework 2.
The second server (DSQL) is not a DC, but is connected to the network. This
machine is running SQL Server Express, which has the database for the
Intranet app running on the DC. It also had all the user created data for the
Intranet (files generated by the Intranet app).
The SQL side works fine - we got the 2 machines talking and using a specific
account so that, whoever logs in to a client pc and visits the Intranet - it
can connect to the sql and works fine.
The problem is the data folder.
In IIS on DC, we created a virtual directory called IntranetShare, which we
pointed at "\\dsql\IntranetShare", which is a network share coming from DSQL
(C:\Intranet Data" to be precise).
Here's the problem, even though the IIS has Integrated Windows
Authentication, whenever our Intranet tries to load anything from
/IntranetShare/ (ie \\dsql\intranetshare) - windows gives us a "Connect to
server" login box, asking for username and password. Not only that, but even
if you do login, it won't accept the credentials, and just keeps asking to
login.
I'm guessing it's permissions/security - but I'm lost. What have we
missed?!!!?
Thanks in advance!
Dan