Windows blocking Pat

[Dave Menges WB9TEN]

I am sure this is not a Pat problem but maybe someone here has run across this issue.
My setup runs Pat on Windows 10. Local browser access is fine. When I try to connect from a browser on a Pi 4, it won’t connect. The message is “192.168.1.150 took too long to respond.”

• Trying from a second Pi and an Android tablet gives me the same results.
• I have turned McAfee off in Windows with the same results.
• There are four “Pat” entries in the Windows firewall but nothing looks restrictive.
• I changed ports from 8000 to 5000.
• Checked the WiFi router for restrictions and didn’t see any. The setup is pretty minimal as I am in the country and the only user.

I’m sure I have worked cross-platform before but maybe Pat was on the Pi and  used a browser in Windows.

Any thoughts are appreciated.
73
Dave
WB9TEN

[Dominic ›OE7DRT‹]

<pat-...@googlegroups.com> on 2026-03-18 1236 +0100:

> My setup runs Pat on Windows 10. Local browser access is fine. When I try
> to connect from a browser on a Pi 4, it won’t connect. The message is
> “192.168.1.150 took too long to respond.”

Does pat listen on that address? (Do you access from local computer via
that address or do you use 127.0.0.1 (localhost))

Can you "ping" the computer that runs Pat from any computer/machine that
wants access to Pat? Can you ping reverse (from Pat to the clients)?

Does the Firewall zone match the zone the network is actually in? (I
don't use Windows for long time but I remember Windows moving my home
network into public network once, so everything was blocked)

If you turn off MacAffe FW, is the Windows Firewall enabled?

HTH

-dominic


--
Excellence is never an accident. It is always the result of high intention,
sincere effort, and intelligent execution; it represents the wise choice
of many alternatives - choice, not chance, determines your destiny.
- Aristotle

[Dave Menges WB9TEN]

Got sidetracked. This is something I needed to do during setup but not during daily ops.

BTW I was using port 8080 not 8000. Typo was in this thread not on the system.

I can ping both ways.

Windows Firewall was on but not the McAfee

I have a Win 7 in storage that has pat on it I'm going to dig that out and see what happens.

Thanks for the help. I'll report back

Dave

[Dominic ›OE7DRT‹]

"'Dave Menges WB9TEN' via pat-users" <pat-...@googlegroups.com> on
2026-03-22 04:20:30 -0700:

> Got sidetracked. This is something I needed to do during setup but
> not during daily ops.
> BTW I was using port 8080 not 8000. Typo was in this thread not on
> the system.

I thought more of the IP address/the interface on which pat listens on.
Like, when you start pat, you get a line like this:

| 2026/03/22 21:05:02 Starting HTTP service (http://:8080)...

So pat will listen on any interface on port 8080.
If that line looks more like "http://localhost:8080" or
"http://127.0.0.1:8080" pat listens only on the local interface, which
is not reachable from another host or network.

> I can ping both ways.
> Windows Firewall was on but not the McAfee

It might then be blocked from the windows firewall.
Would be worth to try disabling any firewall that could potentially
block that port (or create an exception).

I personally wouldn't run two firewalls on the same host at all, as it
might get confusing anyway.

-dominic

--
The pay is good and I can walk to work.
- John F. Kennedy