| 1 |
On Sunday, 14 February 2021 17:16:33 GMT Grant Taylor wrote: |
| 2 |
> On 2/14/21 4:42 AM, Michael wrote: |
| 3 |
> > You are probably right. My knowledge of MSWindows environments has |
| 4 |
> > been on a need to know basis, when I can't avoid it. ;-) |
| 5 |
> |
| 6 |
> Fair enough. |
| 7 |
> |
| 8 |
> I've managed to avoid more Windows in the last 10 years than I could in |
| 9 |
> the previous 10 years. |
| 10 |
> |
| 11 |
> > Active Directory Domain Services use port 445 to store and communicate |
| 12 |
> > domain names, IP addresses, list of services available, etc. for |
| 13 |
> > a domain. |
| 14 |
> |
| 15 |
> TCP port 445 is not directly related to AD DS. Sure, AD DS /uses/ TCP |
| 16 |
> port 445, but so do computers that are not participating in AD DS. |
| 17 |
|
| 18 |
These are the services using port 445: |
| 19 |
|
| 20 |
445 TCP SMB Fax Service |
| 21 |
445 TCP SMB Print Spooler |
| 22 |
445 TCP SMB Server |
| 23 |
445 TCP SMB Remote Procedure Call Locator |
| 24 |
445 TCP SMB Distributed File System Namespaces |
| 25 |
445 TCP SMB Distributed File System Replication |
| 26 |
445 TCP SMB License Logging Service |
| 27 |
445 TCP SMB Net Logon |
| 28 |
|
| 29 |
|
| 30 |
> TCP port 445 is the port that SMB runs over natively. Historically, SMB |
| 31 |
> would use TCP ports 137, 138, and 139 when it was still using the |
| 32 |
> NetBIOS over TCP (NBT). |
| 33 |
> |
| 34 |
> > I suppose initial name to IP resolution happens over port 53, or UDP |
| 35 |
> > 5355 if there is no local DNS resolver configured and the MSWindows |
| 36 |
> > setup uses LLMNR. Microsoft- ds listens on TCP 445 and communicates |
| 37 |
> > stored DNS information to clients regarding domain names, domain |
| 38 |
> > controller(s) and services. I don't know to what extent microsoft-ds |
| 39 |
> > is integrated with the basic TCP-IP DNS service, but expect there |
| 40 |
> > would be some logical linkage in there. |
| 41 |
> |
| 42 |
> I do not recall seeing anything about name resolution running over TCP |
| 43 |
> port 445. |
| 44 |
|
| 45 |
Right, it isn't. My bad. FS Namespaces mapping uses port 445, a different |
| 46 |
function - see URL at the bottom. |
| 47 |
|
| 48 |
> ... |
| 49 |
> |
| 50 |
> Even the venerable WINS (NetBIOS Name Service) ran over TCP port 137. |
| 51 |
> |
| 52 |
> If you have any authoritative information that you can point to where |
| 53 |
> name resolution, of any type, runs over TCP port 445, please share it as |
| 54 |
> I'd like to read it. |
| 55 |
|
| 56 |
All I found from a random search in the interwebs, is the following link. |
| 57 |
Port 445 is used for file/printer data sharing as discussed. It is also used |
| 58 |
for 'Distributed File System Namespaces' across different domains - but this |
| 59 |
is not DNS-IP resolution. |
| 60 |
|
| 61 |
https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/ |
| 62 |
service-overview-and-network-port-requirements |
Archives