Table of Contents

Callers cannot connect

Nobody can connect

  1. Is PBDispatch running? It must be running for new callers to reach you.
  2. Is the service on? Open Network > Services in PBConfig. See The Services screen. After changing a port or an on/off switch, restart the service in Service Management or restart PBDispatch.
  3. Is the port really open on this PC? In a command prompt, run netstat -ano | findstr “:23 ” (use your port) and look for LISTENING.
  4. Is the Windows Firewall allowing it? See Before you install for the netsh command.
  5. Is your router forwarding it? Callers from the Internet need the port forwarded to this PC.

"Port in use"

Two programs cannot listen on the same port. Another program owns it. Common causes:

PBDispatch writes the reason to its event log. Tools > FTP Sessions says “NOT LISTENING” when FTP is not open.

A caller is refused, or banned

SSH callers get a "host key changed" warning

The host key files in Configs were deleted or replaced. Keep them. Callers must accept the new key once. See SSH.

FTP connects but cannot list or download

The control port is open but the data ports are not. Forward and allow the whole passive range (50100-50200 by default), and set External address to your public address or name. Behind a router “auto” is wrong. To check the settings, run PBFtp.exe -cfg Configs\PBFTP.CFG -test. See FTP downloads.

News (NNTP) will not connect

Run PBNntp.exe -cfg Configs\PBNNTP.CFG -test. See News.