Port 139 Blocked on Windows 10 PC
I have a new WIndows 10 computer that I'm trying to scan with Manage Engine. The scan fails and the log shows Port 139 is closed. I've turned off the firewall and the ESET antivirus software and the scan still fails. Windows file and Print sharing are enabled and I can access the default admin share with no problem.
I'm scanning with NetWork Port Scanner from the Microsoft Store and the only port it shows open is port 135. Again this is with the Widows Firewall and ESET turned off. I've even created a new rule to open port 139 and it still shows closed.
I'm scanning with NetWork Port Scanner from the Microsoft Store and the only port it shows open is port 135. Again this is with the Widows Firewall and ESET turned off. I've even created a new rule to open port 139 and it still shows closed.
Jim Riddles
Ports aren't open, unless there is a service listening on that port. Do you have any software installed on the PC you are connecting to that would provide a service on that port? That port is typically associated with Samba file sharing services.
Turn on then firewall and then create an allow rule - that's it.
However, why would there be something even using port 139? It is not used by default.
However, why would there be something even using port 139? It is not used by default.
ASKER
I use Manage Engine SDP OnDemand and it has a feature to scan remote computers on my network. It works everywhere else with no problem but on this one new PC it can't connect and the error log says Port 139 is closed. I ran a port scanner on the computer and the only port that shows open is 135. To answer the first response I did create a new rule to allow port 139 but it still shows only port 135.
That doesn't answer my response. All ports are closed, until they have a service that listens on that port. Additionally, if there is a firewall, there needs to be a rule to allow traffic to said port.
If there is no firewall blocking access to port 139, then there is no service listening on port 139 on the new PC.
Open a command prompt on the new PC and execute the following command:
It will produce output showing all ports being listened to. Check to make sure that 139 is somewhere on that list.
If there is no firewall blocking access to port 139, then there is no service listening on port 139 on the new PC.
Open a command prompt on the new PC and execute the following command:
netstat -aIt will produce output showing all ports being listened to. Check to make sure that 139 is somewhere on that list.
ASKER
I found the problem. NetBIOS over TCP/IP was disabled. Now that I've reenabled it
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Netbios over TCP/IP, yes, but why would that tool want to have that enabled? Nothing needs netbios over tcp/ip. That's a crappy scanner, netbios over tcp/ip is off by default (or at least it is the decision of the router, not of the computer, to enable it).
ASKER
I figured this on out myself.