Localhost not resolving to proper computer name in

We have a XenDesktop 7.5 environment running two DDC's on Windows Server 2012 and SQL Server 2012 running on Server 2012.

We are having issues with DDC01 talking/syncing/going out on dates with DDC02. The error logs show DDC01 trying to contact an endpoint (DDC02) but it can't reach it via the supplied URL.
(http://testDDC.domain.com:80/etc/etc/etc) The URL SHOULD say something like (http://DDC02.domain.com:80/etc/etc/etc)

I have swept the registry and hosts file of the DDC's and the SQL server and the name of testDDC is not there.
The computer name of DDC02 is correct and DNS is correct. SQL Server only shows DDC01$ and DDC02$ as the machine names which have security rights to the database.

The Citrix configuration settings show that URL (listed above) as being http://localhost:80/etc/etc/etc which tells me that something is making the localhost name resolve to testDDC and not DDC02. Since all Windows related tasks/functions seem to be fine and resolve to DDC02, it tells me that Citrix or SQL is probably making that change but I don't know where to look.

Question:
Where should I start to ensure that localhost properly resolves to DDC02 and not testDDC?
LVL 5
Paul WagnerFriend To Robots and RocksAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Dirk KotteConnect With a Mentor SECommented:
would try to remove the second ddc from the pool and rejoin with ddc02.
0
 
footechCommented:
localhost is defined in your HOSTS file on each machine to point to 127.0.0.1 (and ::1 if using IPv6) by default.  HOSTS is located under C:\Windows\System32\drivers\etc\
0
 
Paul WagnerFriend To Robots and RocksAuthor Commented:
@footech
Right, but the hosts list has the right name (DDC02)
0
Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

 
footechCommented:
If at a command prompt you type
ping localhost
and it comes back with the name of the local computer, then there is nothing messed up with name resolution.  At that point it's probably something with the Citrix config, but I can't help you there.
0
 
Paul WagnerFriend To Robots and RocksAuthor Commented:
ping localhost works properly.

I already knew that the issue lied somewhere in the Citrix or SQL config but didn't want to leave out a possible Windows issue. Windows doesn't seem to be the issue so hopefully a Citrix or SQL guru can propose a solution.
0
 
Paul WagnerFriend To Robots and RocksAuthor Commented:
That worked.
0
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.

All Courses

From novice to tech pro — start learning today.