|
| I think what is happening is (as Spooled said) when I specify Username and
Password in "Network Directory and Security Credentials" dialog to access the
remote folder, the username-password is taken as windows user and password
and NOT Novell's. I created users with the same username-password in both the
webserver and novell. When I used it with the Username-Password field it does
not work. Says "Network cannot be found". But, if I check the checkbox
"Always use the authenticated user's credentials when validating access to
the network directory" then I can "Browse" into the virtual folder from IIS.
Now how am I to specify that the Username-Password is not Windows but
Novell's.
Niben
"Spooled" wrote:
> When your credentials are submitted to a Novell Netware connection,
> it's sometimes tricky to figure out WHO you're representing. As a
> user, logged in, at a console, browsing and whatnot, you'll be the
> Novell User that you're logged in as--not necessarily your Windows
> logged in user.
>
> Pair this up with IIS doing the connect as, and you might find that
> even though you're specifying an account and password in the connect as
> spot, it'll likely submit that user account in the domain\username
> format. You might run a netmon capture to see what creds are being
> presented. Windows credentials don't make any sense to a Novell NDS
> tree, unless there is an identically named user account object with the
> same password.
>
> You might also temporarily grant NDS permissions to PUBLIC just to see
> if it goes. Also, start a little simpler, instead of executing a
> script, just do a directory browse--be sure to enable directory
> browsing. Have you tried specifying the CONNECT AS user in full
> context? Remember, NDS is case sensitive on the LOGON NAME (as entered
> in the CONNECT AS, or as the WWW logon account, or in ANONYMOUS logon
> account. In addition to the name being CASE SENSITIVE, whereas Windows
> is case insensitive to the username (this is the really funny part),
> NDS is NOT CASE sensitive to the passwords, whereas, of course, Windows
> IS.
>
> Oh, btw, I'd suspect that you're using NOVELL Client, instead of IPX
> based MS Client, right?
>
> In instances where I needed NW connectivity, I'd have to run the entire
> service as a specific user, and, on top of that, use windows MAPPED
> drives instead of UNC, AND to prevent the mapping from dissappearing,
> stay logged in at the console AS the service account. Have had this
> trouble with Backup Exec in the past too.
>
>
|
|