Why have my 6500 and PGxl gone MIA on my network?

fpmacko

I'm doomed to always have weird problems. So yesterday I walked into the shack and powered up my equipment after an overnight shutdown due to T-storms in the area. I also started SSDR and the PG utility.  

****? None of the software can see my equipment. Everything was working fine until it wasn't. No configurations have changed nor was there an overnight windows update on any of the four PCs. 

I've tried two Windows 11 and two Windows 10 PCs with identical results. But I can connect locally from my iphone or ipad using SSDR and I can see and control the radios perfectly. The weird thing is that I can successfully ping the hardware from any pc as well as from my Verizon router's management page.

SSDR v2.9.2

Any ideas before I submit a help desk ticket?

73..... Frank / WA3NHK

ka9ees

@fpmacko Just for grins. I would restart your router.

fpmacko

Already did that while grinning. Plus I cold started the radio and pgxl. No change. I found a similar posting earlier this month and Mike told him to open a ticket, which I'm about to do.

ka9ees

Good idea!

Mike-VA3MW

This sounds like your FireWall is turned on and it is blocking the communication.

What is the IP address of the computer and radio? Can you post them here and that will confirm a few things.

73

fpmacko

I dunno, Mike. It seems odd that all of a sudden the windows firewall would activate on two w11 and two w10 machines at the same time. But I'll keep an open mind.

6500 192.168.1.209

PGXL 192.168.1.251

BTW, I submitted a support request late yesterday.

73

DonS

Wireshark which is freeware is an excellent tool for determining what is on the network and what is happening on the network.

Don - kx9q

fpmacko

Tnx, Don. I just got things working again. Ken Wells at the help desk pointed me toward my "ESET" security software as the likely culprit because within the past two weeks others running ESET have reported the same problem. I had to add firewall rules to allow smartsdr, dax, cat, and PGXL utility to use any protocols. I've been using ESET for several years and never had to do that before, but it appears that an update on 14 Aug to the "Antivirus and antispyware scanner" module caused the problem even though the name indicates it has nothing to do with the firewall. Go figure.

73.... Frank / WA3NHK