Results 1 to 5 of 5

Thread: No process listening on port 445

  1. #1
    Join Date
    Jun 2009

    No process listening on port 445

    I am running Windows XP SP3 on my computer. When we try to connect to port 445, I get an error message saying "Error 67 - Network path not found". Nestat shows the system listening on TCP port 445 but I do not see any service listening on UDP 445. I have fiddled around with NetBT parameters in the registry but didn't found anything odd. What else do I need to get things work?

  2. #2
    Join Date
    Jan 2006

    Re: No process listening on port 445

    Which internet security, firewall, anti-virus program are you running? I suppose this may be blocking the SMB protocol. Are all the computers in your network running the same software? Is it working on other computers? It may also be due to some registry misconfiguration which prevents port 445 from being used by the networking stack.

  3. #3
    Join Date
    May 2008

    Re: No process listening on port 445

    Perform a repair installation of TCP/IP. Apart from that what does your Event log says about the same? And is your WINS proxy server enabled. You can disable it from the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetBT\Parameters\EnableProxy
    Set it to "0".

  4. #4
    Join Date
    Jun 2009

    Re: No process listening on port 445

    If your concerned is just that no process is currently listening to port 445 then don't worry. Its normal. You never connect to ports but to applications. A port is basically a Layer 4 address which is associated with a "listening" application. If it is no one is listening to that port then there must not be application currently running or may be some one has just stopped or will be starting and so the connection to the port was left opened in order to wait until the process complete its procedure.

  5. #5
    Join Date
    Apr 2008

    Re: No process listening on port 445

    May be due to some failure in your connection it was left open by some process which have used it but due to abnormal closure of it, it was unable to close the port that it has used during its operation. So in order to manually close it, here are the below steps:

    Start - Run - type "regedit" and press Enter. Navigate to HKLM\System\CurrentControlSet\Services\NetBT\Parameters. Search for "TransportBindName" registry entry, right-click on it and select "Modify". Under "Value data:", remove its content and leave it blank. This will close the port. Click on "OK". Close the registry and restart your computer.

Similar Threads

  1. Unblock listening port for bitcomet.
    By Upendra in forum Networking & Security
    Replies: 6
    Last Post: 27-06-2011, 09:00 PM
  2. XP Port 3389 Not Listening
    By Harnoor in forum Networking & Security
    Replies: 6
    Last Post: 30-12-2010, 10:51 PM
  3. When Listening port vs Proxy SOCKS port are used?
    By rooki in forum Windows Software
    Replies: 3
    Last Post: 24-06-2010, 04:05 PM
  4. Port Not Listening
    By Thomas R Grassi Jr in forum Windows Server Help
    Replies: 4
    Last Post: 13-12-2008, 03:47 PM
  5. DNS listening port?
    By mcRon in forum Windows Server Help
    Replies: 5
    Last Post: 07-11-2008, 04:15 PM

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Page generated in 1,642,523,105.22520 seconds with 17 queries