Remote Desktop - remote computer that was reached is not the one you specified

Question

I am working at revamping some previous blog apps. I parse the XML, but so far, when a table view cell is clicked, I just have it open the URL for the article that was clicked by the user. This is beginning to get frowned upon by Apple, and I need to change it anyways, so I can gain some more options with display. The entire article is displayed with this tag:

<content:encoded>

I am able to get the data from within this tag, but there are a couple issues. It always starts off with

<![CDATA[<p>

And ends with

</p>]]>

As you can see, it also contains not true text but code, such as

<p> and </p> and aren&#8217;t &#8220

Any suggestions for how I can parse this to remove the beginning and ends of the string, and convert to all true text that I can load in my view?

Solution 1

It appears this was at least partially related to the clock on the domain controller being off. Once the time was corrected then it worked.

Solution 2

Have you tried flushing the dns cache?

ipconfig /flushdns

Sounds like the problem lies somewhere in the DNS.

1. Check normal name lookup through DNS.
2. Check reverse DNS lookup on the IP address of the Windows 2008 R2 machine.
3. Examine the DNS records created for the servers / windows 7 machines on the DNS server.
4. Try disabling IP6 on both machines.

Reference this

Time and again we see the IPv6 stack operating under the hood, having a silent affect on applications. One area we have seen this is in DNS calls for application servers. Depending on the application and specific stack in use, the client may make DNS calls over IPv4 requesting the IPv6 address of application servers

Solution 3

To fix this issue login to the affected server using IP address and run the following cmd,

• net stop w32time
• net start w32time

I believe this will fix the issue.

Solution 4

This can happen if you use a certificate and the names don't match.

View more solutions

Comments

[Admin]

Got one R2 server experiencing this after a reload as well. It has its hostname A record and reverse lookup correctly defined and there's a CNAME pointing to the FQDN that was previously used to address it. Now this throws this error and server, client and all DCs are in sync... getting annoying as there was no problem with the previous RC R2 install on that particular machine - and it has retained the same IP address...

[Bernie White]

The answer would be improved by providing a reference to an official KB or further explaining why installation the connection broker on two servers causes the problem.

[Hubert Kario]

gotta love detailed error messages...

[Bernie White]

You have not provided any substance to your answer. To answer you need to provide some workings to how to diagnose the issue and then provide a suggestions on how to resolve it. To improve the answer further you can provide references to support your workings.

[Neil P]

In my case, the server IP address had changed, and the DNS on the DC was still holding the old value. Fix was to run ipconfig /registerdns on the problem server.

[Dan Henderson]

I just had a similar situation; in my case the clock of the machine I was trying to connect to was wrong, and the Windows Time service was disabled for some reason.