Thanks for the reply Adam, actually the domain name is already part of the freerdp connection, the problem is that the the "change password" dialogue asks for the address of the domain controller as it has to communicate with the domain controller to change the password. If that field is left blank the change password fails with the message something like "can't connect to smb server"
If I manually add the DC address to that dialogue field the password change succeeds. E.G. 10.x.x.x This is not something I would expect an end user to do.
I do have a bit more info
I have a different customer with a similar set up, except that their thins are on the same sub-net as the windows domain controller, which also means that it is windows which handles DNS, DHCP. In that instance the "domain controller" field is automatically filled in,...
