Hello.
I'm trying to deploy a site from our development server to our production server.  We're running DNN 3.2 on a Win 2003 platform.  I have active directory set up and working on development.  And by working I mean when a user who is logged onto the domain hits the site they are automatically logged on to the DNN portal. 

My problem is this.  Now that I've moved my site to production my users no longer get automatically logged on like they did in my development environment.  Instead the username/password dialog box pops up and only after they type domain\user with their password do they get logged on to the site.  I have a suspicion that the manner in which the site is called may be playing a role in my problem.  I say this because of the situation as it stands now.

On development I connect to  http://rhweb1-dev where rhweb1-dev is the develoment machine name
This logs my users straight onto the DNN portal without being promted for user/pass

After moving to production I try to connect to http://home.rhweb.com and get prompted for user/pass.
I've also tried by the IP http://10.1.1.38 and again get prompted for user/pass.  However, when I try the machine name (as I did in development) http://rhweb1 I get passed through windows authentication without being prompted and I'm logged onto the site.  I have many users who have "http://home.rhweb.com" already bookmarked into their browsers so we need to leave our production site available at that address. 

Is there a setting I need to change or set in order for my users to still be logged on when calling the site by something other than the machine name?

I should also note that I've found that if I add add http://10.1.1.38 to the trusted intranet sites list, i.e. the non-machine name URL, then the authentication works.  Again, I'd rather not do this for each computer, we have over 500 terminals we'd have to update with this trusted site information.

Thanks in advance.
Tracy