Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing problems using Remote Desktop from Windows boxes. The rather useless and completely misleading error message states: "The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead." We are able to RDP using the IP address from a Windows machine. We are also able to RDP by either name or address from a Linux machine. It's only when we try to connect by name from a Windows machine that we have this problem. It all worked perfectly fine prior to the Samba upgrade. It most certainly is not a DNS issue but just to be ultra sure the caches on both the client and destination boxes were flushed, We also rebooted both machines. The clocks were also checked against those on the DCs, with a maximum discrepancy of one second. The time on the two DCs matched to within 0.002 seconds. Anyone have any theories about this? Or a solution? regards, John
What is the hostname of the computer your connection to? If it contains a dash or other special sign, make a cname of that computer without any special signs and try to connect to that cname with rdp client. And ! try connection to : hostname.domain.tld Last, any change the computer your connections has ethernet and wifi? ( so if has 2 ipnumbers and one hostname ) If so, disable the wifi. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens John Gardeniers > via samba > Verzonden: donderdag 17 november 2016 22:49 > Aan: samba > Onderwerp: [Samba] Problem since upgrade to 4.5.1 > > Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing > problems using Remote Desktop from Windows boxes. The rather useless and > completely misleading error message states: > > "The connection cannot be completed because the remote computer that was > reached is not the one you specified. This could be caused by an > outdated entry in the DNS cache. Try using the IP address of the > computer instead." > > We are able to RDP using the IP address from a Windows machine. We are > also able to RDP by either name or address from a Linux machine. It's > only when we try to connect by name from a Windows machine that we have > this problem. It all worked perfectly fine prior to the Samba upgrade. > > It most certainly is not a DNS issue but just to be ultra sure the > caches on both the client and destination boxes were flushed, We also > rebooted both machines. > > The clocks were also checked against those on the DCs, with a maximum > discrepancy of one second. The time on the two DCs matched to within > 0.002 seconds. > > Anyone have any theories about this? Or a solution? > > regards, > John > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
On 17/11/16 21:48, John Gardeniers via samba wrote:> Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing > problems using Remote Desktop from Windows boxes. The rather useless > and completely misleading error message states: > > "The connection cannot be completed because the remote computer that > was reached is not the one you specified. This could be caused by an > outdated entry in the DNS cache. Try using the IP address of the > computer instead." > > We are able to RDP using the IP address from a Windows machine. We are > also able to RDP by either name or address from a Linux machine. It's > only when we try to connect by name from a Windows machine that we > have this problem. It all worked perfectly fine prior to the Samba > upgrade. > > It most certainly is not a DNS issue but just to be ultra sure the > caches on both the client and destination boxes were flushed, We also > rebooted both machines. > > The clocks were also checked against those on the DCs, with a maximum > discrepancy of one second. The time on the two DCs matched to within > 0.002 seconds. > > Anyone have any theories about this? Or a solution? > > regards, > John > >Hi John, I've just tested on our newest test domain and I could not reproduce this connecting to our single Server 2008 R2 Terminal Server from Windows 7. I presume you can resolve the names OK from your Windows client machine? Cheers, Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. This email is not intended to, nor should it be taken to, constitute advice. The information provided is correct to our knowledge & belief and must not be used as a substitute for obtaining tax, regulatory, investment, legal or any other appropriate advice. "Transact" is operated by Integrated Financial Arrangements Ltd. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).
Just a though as I was passing in the neighbourhood: does your Terminal Server have related SPN (ServicePrincipalName) created on computer objects? servicePrincipalName: HOST/W7AD-02 servicePrincipalName: HOST/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02 HOST/<hostname> should exist on all computers, that's just to be thorough. TERMSRV/<hostname> should exist on Windows you want to access through RDP (if my little understanding regarding SPN is correct) 2016-11-18 10:20 GMT+01:00 Alex Crow via samba <samba at lists.samba.org>:> On 17/11/16 21:48, John Gardeniers via samba wrote: > >> Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing >> problems using Remote Desktop from Windows boxes. The rather useless and >> completely misleading error message states: >> >> "The connection cannot be completed because the remote computer that was >> reached is not the one you specified. This could be caused by an outdated >> entry in the DNS cache. Try using the IP address of the computer instead." >> >> We are able to RDP using the IP address from a Windows machine. We are >> also able to RDP by either name or address from a Linux machine. It's only >> when we try to connect by name from a Windows machine that we have this >> problem. It all worked perfectly fine prior to the Samba upgrade. >> >> It most certainly is not a DNS issue but just to be ultra sure the caches >> on both the client and destination boxes were flushed, We also rebooted >> both machines. >> >> The clocks were also checked against those on the DCs, with a maximum >> discrepancy of one second. The time on the two DCs matched to within 0.002 >> seconds. >> >> Anyone have any theories about this? Or a solution? >> >> regards, >> John >> >> >> > Hi John, > > I've just tested on our newest test domain and I could not reproduce this > connecting to our single Server 2008 R2 Terminal Server from Windows 7. > > I presume you can resolve the names OK from your Windows client machine? > > Cheers, > > Alex > > -- > This message is intended only for the addressee and may contain > confidential information. Unless you are that person, you may not > disclose its contents or use it in any way and are requested to delete > the message along with any attachments and notify us immediately. > This email is not intended to, nor should it be taken to, constitute > advice. > The information provided is correct to our knowledge & belief and must not > be used as a substitute for obtaining tax, regulatory, investment, legal or > any other appropriate advice. > > "Transact" is operated by Integrated Financial Arrangements Ltd. > 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 > 5300. > (Registered office: as above; Registered in England and Wales under > number: 3727592). Authorised and regulated by the Financial Conduct > Authority (entered on the Financial Services Register; no. 190856). > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
Hi Louis, While it wasn't spelled out, it was firmly implied in my previous message that this problem appeared only after the Samba upgrade. Nothing else has changed that might impact RDP. There has been no change to machine names, IP addresses (we use DHCP reservations) or DNS entries. If a dash in the computer's name or DNS entry is behind this issue then it's clearly a rather serious bug in Samba. regards, John On 18/11/16 19:10, L.P.H. van Belle via samba wrote:> What is the hostname of the computer your connection to? > > If it contains a dash or other special sign, make a cname of that computer without any special signs and try to connect to that cname with rdp client. > > And ! try connection to : hostname.domain.tld > > Last, any change the computer your connections has ethernet and wifi? > ( so if has 2 ipnumbers and one hostname ) > If so, disable the wifi. > > > Greetz, > > Louis > > > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens John Gardeniers >> via samba >> Verzonden: donderdag 17 november 2016 22:49 >> Aan: samba >> Onderwerp: [Samba] Problem since upgrade to 4.5.1 >> >> Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing >> problems using Remote Desktop from Windows boxes. The rather useless and >> completely misleading error message states: >> >> "The connection cannot be completed because the remote computer that was >> reached is not the one you specified. This could be caused by an >> outdated entry in the DNS cache. Try using the IP address of the >> computer instead." >> >> We are able to RDP using the IP address from a Windows machine. We are >> also able to RDP by either name or address from a Linux machine. It's >> only when we try to connect by name from a Windows machine that we have >> this problem. It all worked perfectly fine prior to the Samba upgrade. >> >> It most certainly is not a DNS issue but just to be ultra sure the >> caches on both the client and destination boxes were flushed, We also >> rebooted both machines. >> >> The clocks were also checked against those on the DCs, with a maximum >> discrepancy of one second. The time on the two DCs matched to within >> 0.002 seconds. >> >> Anyone have any theories about this? Or a solution? >> >> regards, >> John >> >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >