using System.Net.NetworkCredentials on windows NT

[[MSFT]]

Hi Tim,

Did you specify a domain user or a local user here? Did the Windows NT
server is in same domain as others?

Luke

[Joe Kaplan \(MVP - ADSI\)]

Does it work if you specify the local machine name for the domain parameter
of specify the username as machine\user?

Joe K.
"Tim B." <TimBur@seattletimes.com> wrote in message
news:6C87280A-C822-4478-A218-A05DE6152AE4@microsoft.com...

> I specified a non domain user just as the example line of code shows
>
> "[MSFT]" wrote:
>

> > Hi Tim,
> >
> > Did you specify a domain user or a local user here? Did the Windows NT
> > server is in same domain as others?
> >
> > Luke
> >
> >

[Joe Kaplan \(MVP - ADSI\)]

I'm not sure it would help me to look at the IIS logs. It might be useful
to look at the headers passed back and forth in the exchange though. The
Negotiate protocol will stick a bunch of headers in the request as it
bounces back and forth, and looking at the differences between the request
and response headers that work and don't work might be helpful.

Joe K.

"Tim B." <TimBur@seattletimes.com> wrote in message
news:CAB15F8C-63C5-4B00-AA61-B33C5CDEA732@microsoft.com...

> I haven't tried that, but that wouldn't work in the solution anyway.
> I could try it if you think it pertinent.
>
> Would seeing the IIS logs on the server hosting the service be helpful ?
>
> It appears to me that NT just gives up at the first 401 error, but win2k

and above retry will send the credentials on subsequent attempts and finally
get a '200' response.

>
>
>
> "Joe Kaplan (MVP - ADSI)" wrote:
>

> > Does it work if you specify the local machine name for the domain

parameter

> > of specify the username as machine\user?
> >
> > Joe K.
> > "Tim B." <TimBur@seattletimes.com> wrote in message
> > news:6C87280A-C822-4478-A218-A05DE6152AE4@microsoft.com...

> > > I specified a non domain user just as the example line of code shows
> > >
> > > "[MSFT]" wrote:
> > >
> > > > Hi Tim,
> > > >
> > > > Did you specify a domain user or a local user here? Did the Windows

NT

> > > > server is in same domain as others?
> > > >
> > > > Luke
> > > >
> > > >

> >
> >
> >

[Joe Kaplan \(MVP - ADSI\)]

You can always use a packet sniffer like netmon or Ethereal to do this
unless SSL is in the mix. I'd probably use this first if it's an option.

As I recall you are using the HttpWebRequest class, right? In that case,
HttpWebResponse class has Headers collection that you can also access that
should work.

HTH,

Joe K.

"Tim B." <TimBur@seattletimes.com> wrote in message
news:3BCEB930-13A8-4ED8-B958-45E2C984429C@microsoft.com...

> Joe,
>
> How can I capture the headers ?
>
> Tim
>
> "Joe Kaplan (MVP - ADSI)" wrote:
>

> > I'm not sure it would help me to look at the IIS logs. It might be

useful

> > to look at the headers passed back and forth in the exchange though.

The

> > Negotiate protocol will stick a bunch of headers in the request as it
> > bounces back and forth, and looking at the differences between the

request

> > and response headers that work and don't work might be helpful.
> >
> > Joe K.
> >

[[MSFT]]

You may create a user on the Win NT server, with same name and password,
and then test again. Will this correct the problem?

Luke

[Tim B.]

Luke,

This does already work for win2k and xp - so yes I do have the user already on the server.

"[MSFT]" wrote:

> You may create a user on the Win NT server, with same name and password,
> and then test again. Will this correct the problem?
>
> Luke
>
>

[[MSFT]]

Hello,

Has the Win NT 4.0 applied NT Service pack 6 and installed IIS 5.0 or 6.0?
Additionally, have you tried to capture the headers as Joe suggested?

Luke

[[MSFT]]

Hi Tim,

You may check if it is an expired evaluation account on the Win NT
computer. And, you can execute the client code on the Win NT server
directly, to see if it a network issue. Furthermore, you can also check
the IIS log to see if we can get more information from it.

Luke

[Tim B.]

I've opened a case with Dev support on this.

Tim

"[MSFT]" wrote:

> Hi Tim,
>
> You may check if it is an expired evaluation account on the Win NT
> computer. And, you can execute the client code on the Win NT server
> directly, to see if it a network issue. Furthermore, you can also check
> the IIS log to see if we can get more information from it.
>
> Luke
>
>

[[MSFT]]

That sounds reasonable. Thank you for the share.

regards,

Luke