[Samba] Problem since upgrade to 4.5.1

John Gardeniers
2016-11-20T20:42:30Z

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
>