Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Background

I have a client running Windows Small Business Server 2003. For reasons too dull to explain, they would access this machine via Terminal Services using the domain mail.foo.com (where "foo" represents the company's domain name). Because I moved their mail to Google Apps (and other reasons), we had to change this domain name to something else: server.foo.com.

Problem

The users cannot connect to the server using server.foo.com. They must connect using the IP address of the server, even though the domain points to that very same IP address. In fact, I have verified this by pinging that domain, copying the resulting IP address from the ping results, and connecting to the server using RDC. It works fine!

Why can they connect using the IP address but not the domain name, even though they are one and the same? I don't get it.

share|improve this question

2 Answers 2

up vote 1 down vote accepted

Probably, your client has different DNS settings. For some reason, the name "server.foo.com" can be resolved on your side, but cannot resolve on his machine. He will receive the negative answer from dns cache, but it certainly depends on his configuration.

share|improve this answer
    
This turned out to be correct. –  Gregory Higley Dec 5 '10 at 5:26

My guess would be that you just need to add an additional Service Principal Name to that server for the new host/domain name.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.