[gentoo-user] Re: TCP port 445

[Grant Taylor]

On 2/14/21 4:42 AM, Michael wrote:
> You are probably right.  My knowledge of MSWindows environments has
> been on a need to know basis, when I can't avoid it.  ;-)

Fair enough.

I've managed to avoid more Windows in the last 10 years than I could in 
the previous 10 years.

> Active Directory Domain Services use port 445 to store and communicate
> domain names, IP addresses, list of services available, etc. for
> a domain.

TCP port 445 is not directly related to AD DS.  Sure, AD DS /uses/ TCP 
port 445, but so do computers that are not participating in AD DS.

TCP port 445 is the port that SMB runs over natively.  Historically, SMB 
would use TCP ports 137, 138, and 139 when it was still using the 
NetBIOS over TCP (NBT).

> 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.

I do not recall seeing anything about name resolution running over TCP 
port 445.

...

Even the venerable WINS (NetBIOS Name Service) ran over TCP port 137.

If you have any authoritative information that you can point to where 
name resolution, of any type, runs over TCP port 445, please share it as 
I'd like to read it.

> Anyhow, I think the OPs problem is down to the wrong CUPS driver used
> in remote client(s).

Agreed.



-- 
Grant. . . .
unix || die