2019年4月25日 · However, Port 135 is needed in an active directory and server/client environment for many services to operate properly. For a client, such as a surface, the port can probably be safely closed because services that depend on …

These services aren't directly assigned to port 135. Rather, they all run over MSRPC (a remote process communication protocol used by Windows NT), and MSRPC uses port 135 when transported over TCP. Instead of reinventing the protocol separately for each service (data types, framing, semantics, client & server code) they all simply exchange ...

2015年12月12日 · Having testded RPC 135 port via tools rpcdump.py impacket open source project and something else concerned, i have confirmed something about TCP port 135: Anyone can connect to TCP port 135 then get RPC interfaces list without any permission.

2024年4月3日 · I was able to create a rule to block port 135 using Windows Firewall. However when looking at nmap output. The port is still open.

2022年12月10日 · If the server has NBT enabled, it listens on UDP ports 137, 138, and on TCP ports 139, 445. If it has NBT disabled, it listens on TCP port 445 only. And this site (archived) mentions: "In Windows 2000/XP/2003, Microsoft added the possibility to run SMB directly over TCP/IP, without the extra layer of NetBT. For this they use TCP port 445.

After a lot of troubleshooting, I was able to determine that there was a Windows firewall rule enabled that would only allow connections from PC1 over TCP/135 and TCP/1027 if the connection is secure. In Windows Firewall with Advanced Security-> Inbound Rules, I went into the suspect rule properties.

All the ports above are listening for connections, hence why it says 'Listening'. However, most are listening to connections on 'Any' IP your machine may have, so that can be the local loopback address (127.0.0.1) but also any IP given on any interface on your machine - In this case you can see that one process is listening on port 139 (NetBios), on what appears to …

2013年8月11日 · Among the new ports used by Windows 2000 is TCP port 445 which is used for SMB over TCP. The SMB (Server Message Block) protocol is used among other things for file sharing in Windows NT/2000/XP. In Windows NT it ran on top of NetBT (NetBIOS over TCP/IP), which used the famous ports 137, 138 (UDP) and 139 (TCP).

1026: Remote Procedure Calls, DCOM: Kept open by the event log, same reason as 135. 1027: IIS: But why does this port still shows up when the IIS-related service have been disabled? 1028: NFS or IIS: Same reason as 1025. 1036: Nebula Secure Segment Transfer Protocol: What is this for? Seems a randomized port... So, these are my questions:

From another TechNet article, NetBIOS implementation over TCP/IP?: The Windows 2000 implementation of NetBIOS over TCP/IP is referred to as NetBT. NetBT uses the following TCP and UDP ports: UDP port 137 (name services) UDP port 138 (datagram services) TCP port 139 (session services) NetBIOS over TCP/IP is specified by RFC 1001 and RFC 1002.