• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 207
  • Last Modified:

Internal DNS and Authentication

I am running a 2003 AD domain with 2000 and 2003 member servers. Why is it that when I create an internal website on "serverx" using IIS6 and just type http://serverx the server doesn't ask me to authenticate, but if I type in the FQDN of "serverx" like http://serverx.corporate.domain.com then it asks me to authenticate? Why do I need this additional authentication if I've already authenticated with the AD when I logged in and how do I get rid of this? Additionally, I am forced to also log in using "domain\username" when I login. This is annoying and unnecessary since I only have one domain. Is there a way to turn this off and default to a certain domain?

1 Solution
Try adding *.corporate.domain.com to your "Trusted Sites" in Internet Explorer. Un-check the "Use https:" checkbox.
mannonAuthor Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now