On Saturday, 13 February 2021 22:11:49 GMT Grant Taylor wrote: > On 2/12/21 4:00 AM, Michael wrote: > > Samba uses the native MSWindows 'Active Directory Domain Services' > > over TCP port 445 to resolve IP addresses when printing over Samba. > > I question the veracity of this. > > My understanding is that name to ip resolution, particularly in Active > Directory environments, is that it is all DNS based.
You are probably right. My knowledge of MSWindows environments has been on a need to know basis, when I can't avoid it. ;-) Active Directory Domain Services use port 445 to store and communicate domain names, IP addresses, list of services available, etc. for a domain. I suppose initial name to IP resolution happens over port 53, or UDP 5355 if there is no local DNS resolver configured and the MSWindows setup uses LLMNR. Microsoft- ds listens on TCP 445 and communicates stored DNS information to clients regarding domain names, domain controller(s) and services. I don't know to what extent microsoft-ds is integrated with the basic TCP-IP DNS service, but expect there would be some logical linkage in there. Anyhow, I think the OPs problem is down to the wrong CUPS driver used in remote client(s).
signature.asc
Description: This is a digitally signed message part.
