maxedoutcc
Gawd
- Joined
- Jan 26, 2001
- Messages
- 1,001
Solution found: This appears to be a security feature in Server 2003 acknowledged in the KB 896861 - http://support.microsoft.com/kb/896861
Figured I would post the solution if someone else comes across this problem in the future.
---------------------------------------------------------------------
I have a wierd asp.net 2.0 integrated authentication issue im dealing with.
I have a single webservice that allows you to get roles from active directory. The first service has a single method with a user/pass/domain parameter that then calls a second webservice which uses integrated authentication and returns the active directory roles they are in.
The second service works fine from any remote computer, except the host computer. I can not get the system to accept a username and password regardless if it is valid or not.
If I change the call from the first web service to the second webservice from using a DNS name to its IP address everything works fine.
I have searched google all to find various things that do not work. anyone have an idea? Below are a couple of more info.
each service has its own dns, ip address and website configured on IIS 6.0.
The service works fine on another server when they are configured as applications under a single domain.i.e... http://myname/service1 & http://myname/service2
I really want to get this resolved as opposed to splitting these web services to different servers.
Figured I would post the solution if someone else comes across this problem in the future.
---------------------------------------------------------------------
I have a wierd asp.net 2.0 integrated authentication issue im dealing with.
I have a single webservice that allows you to get roles from active directory. The first service has a single method with a user/pass/domain parameter that then calls a second webservice which uses integrated authentication and returns the active directory roles they are in.
The second service works fine from any remote computer, except the host computer. I can not get the system to accept a username and password regardless if it is valid or not.
If I change the call from the first web service to the second webservice from using a DNS name to its IP address everything works fine.
I have searched google all to find various things that do not work. anyone have an idea? Below are a couple of more info.
each service has its own dns, ip address and website configured on IIS 6.0.
The service works fine on another server when they are configured as applications under a single domain.i.e... http://myname/service1 & http://myname/service2
I really want to get this resolved as opposed to splitting these web services to different servers.