Server working but Client does not see the server

The other option is to simply change the port that wfview is using (both on the server tab of the server computer and radio tab of client) to something like 50011

Phil

I changed the port to 50013 for both the server and client same result - no connection. Did go to the command line and

Microsoft Windows [Version 10.0.19045.3448]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Sprcial>netstat -aon

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1040
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:3648 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:4533 0.0.0.0:0 LISTENING 17524
TCP 0.0.0.0:5040 0.0.0.0:0 LISTENING 4336
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:7070 0.0.0.0:0 LISTENING 4208
TCP 0.0.0.0:7680 0.0.0.0:0 LISTENING 1268
TCP 0.0.0.0:7779 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING 988
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING 836
TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING 1516
TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING 1396
TCP 0.0.0.0:49671 0.0.0.0:0 LISTENING 3612
TCP 0.0.0.0:49705 0.0.0.0:0 LISTENING 968
TCP 0.0.0.0:52355 0.0.0.0:0 LISTENING 5860
TCP 0.0.0.0:54950 0.0.0.0:0 LISTENING 4200
TCP 127.0.0.1:8884 0.0.0.0:0 LISTENING 4
TCP 127.0.0.1:23401 0.0.0.0:0 LISTENING 12480
TCP 127.0.0.1:49746 0.0.0.0:0 LISTENING 2344
TCP 192.168.1.200:139 0.0.0.0:0 LISTENING 4
TCP 192.168.1.200:50876 92.38.177.14:443 ESTABLISHED 4208
TCP 192.168.1.200:53081 192.168.1.128:8080 ESTABLISHED 10436
TCP 192.168.1.200:54406 193.111.230.10:443 ESTABLISHED 12864
TCP 192.168.1.200:54467 20.25.241.18:443 ESTABLISHED 3912
TCP 192.168.1.200:54627 34.147.46.37:443 ESTABLISHED 12864
TCP 192.168.1.200:54666 44.215.131.66:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54671 44.215.135.131:443 ESTABLISHED 12864
TCP 192.168.1.200:54672 44.215.135.131:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54684 18.172.124.29:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54685 13.32.176.218:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54686 13.32.176.218:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54687 13.32.176.218:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54688 13.32.176.218:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54689 52.85.90.116:443 CLOSE_WAIT 12864
TCP 192.168.1.200:54690 44.215.116.72:443 ESTABLISHED 12864
TCP 192.168.1.200:54691 44.215.116.72:443 ESTABLISHED 12864
TCP 192.168.1.200:54703 20.189.173.16:443 TIME_WAIT 0
TCP 192.168.1.200:54708 204.79.197.222:443 TIME_WAIT 0
TCP 192.168.1.200:54709 192.229.211.108:80 TIME_WAIT 0
TCP 192.168.1.200:54721 20.189.173.16:443 ESTABLISHED 2680
TCP 192.168.1.200:54725 204.79.197.222:443 ESTABLISHED 2680
TCP 192.168.1.200:60197 20.40.207.23:8883 ESTABLISHED 8204
TCP [::]:135 [::]:0 LISTENING 1040
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:3648 [::]:0 LISTENING 4
TCP [::]:4533 [::]:0 LISTENING 17524
TCP [::]:5357 [::]:0 LISTENING 4
TCP [::]:7680 [::]:0 LISTENING 1268
TCP [::]:7779 [::]:0 LISTENING 4
TCP [::]:49664 [::]:0 LISTENING 988
TCP [::]:49665 [::]:0 LISTENING 836
TCP [::]:49666 [::]:0 LISTENING 1516
TCP [::]:49667 [::]:0 LISTENING 1396
TCP [::]:49671 [::]:0 LISTENING 3612
TCP [::]:49705 [::]:0 LISTENING 968
TCP [::]:52355 [::]:0 LISTENING 5860
TCP [::1]:49767 [::]:0 LISTENING 7632
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54381 [2607:f8b0:4023:1407::bc]:5228 ESTABLISHED 12864
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54661 [2600:9000:2506:3800:7:49a5:5fd2:8621]:443 ESTABLISHED 12864
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54662 [2a04:4e42:83::272]:443 ESTABLISHED 12864
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54664 [2a04:4e42:83::272]:443 ESTABLISHED 12864
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54669 [2a04:4e42:83::307]:443 ESTABLISHED 12864
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54693 [2620:1ec:c11::200]:443 TIME_WAIT 0
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54694 [2603:1036:304:86e::2]:443 TIME_WAIT 0
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54695 [2620:1ec:c11::200]:443 TIME_WAIT 0
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54696 [2620:1ec:c11::200]:443 TIME_WAIT 0
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54697 [2620:1ec:c11::200]:443 TIME_WAIT 0
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54718 [2620:1ec:c11::200]:443 ESTABLISHED 2680
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54719 [2603:1036:304:86e::2]:443 ESTABLISHED 2680
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54720 [2620:1ec:c11::200]:443 ESTABLISHED 2680
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54722 [2606:2800:11f:17a5:191a:18d5:537:22f9]:443 ESTABLISHED 2680
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54723 [2620:1ec:50::254]:443 ESTABLISHED 2680
TCP [2600:1702:3b10:7950:44c9:c7d2:9090:3877]:54724 [2603:1006:2:1::2]:443 ESTABLISHED 2680
UDP 0.0.0.0:123 : 4844
UDP 0.0.0.0:500 : 3920
UDP 0.0.0.0:3702 : 2240
UDP 0.0.0.0:3702 : 2240
UDP 0.0.0.0:4500 : 3920
UDP 0.0.0.0:5050 : 4336
UDP 0.0.0.0:5353 : 20440
UDP 0.0.0.0:5353 : 20440
UDP 0.0.0.0:5353 : 2748
UDP 0.0.0.0:5355 : 2748
UDP 0.0.0.0:50001 : 17524
UDP 0.0.0.0:50001 : 4208
UDP 0.0.0.0:50002 : 17524
UDP 0.0.0.0:50003 : 17524
UDP 0.0.0.0:50591 : 2240
UDP 0.0.0.0:51759 : 2240
UDP 0.0.0.0:54955 : 4200
UDP 127.0.0.1:1900 : 2392
UDP 127.0.0.1:48200 : 12480
UDP 127.0.0.1:49668 : 4708
UDP 127.0.0.1:51900 : 2392
UDP 192.168.1.200:137 : 4
UDP 192.168.1.200:138 : 4
UDP 192.168.1.200:1900 : 2392
UDP 192.168.1.200:51899 : 2392
UDP [::]:123 : 4844
UDP [::]:500 : 3920
UDP [::]:3702 : 2240
UDP [::]:3702 : 2240
UDP [::]:4500 : 3920
UDP [::]:5353 : 20440
UDP [::]:5353 : 2748
UDP [::]:5355 : 2748
UDP [::]:50001 : 17524
UDP [::]:50002 : 17524
UDP [::]:50003 : 17524
UDP [::]:50592 : 2240
UDP [::]:51760 : 2240
UDP [::1]:1900 : 2392
UDP [::1]:51898 : 2392
UDP [::1]:58932 : 4760
UDP [::1]:58933 : 4760
UDP [fe80::7b39:61c9:da00:e997%14]:1900 : 2392
UDP [fe80::7b39:61c9:da00:e997%14]:51897 : 2392

C:\Users\Sprcial>

The only application I have added since I started working with WFView is AnyDesk for remote login to the server and client.

That is your issue probably.

That is absolutely your problem then, Anydesk uses ports 50001-50003 for it’s ‘discovery’ feature.

You will need to change all ports on the server and the control port on the client, try adding 100 to each of them.


I added 100 to each to give 50101, 50102, 50103 to both the client and server side still no connection. I have the URL for the logs below

CLIENT
https://termbin.com/s8c1

SERVER
https://termbin.com/eya9


It looks like you also set a manual C-IV address on the client, this MUST be left on auto

Server log
https://termbin.com/k3nfz

client
https://termbin.com/j55u

I have checked everything again and added the 100 to the port and removed the security software from the client and I am still not able to connect

On the server log:

023-09-19 09:06:09.625 INF serial: Could not open serial port  "COM5"  , please restart.

This means the radio serial port is incorrect!

Also why are you running the server on the client machine? Server should be disabled.

The “server” machine is still listening on ports 50001-3

ok, let’s do a full restart here. Let’s see if you have the basics set up right.

Did you install the windows driver of the 7300 (icom site) without having the 7300 connected?

Tell us the ip address, netmask, gateway address of the server
Tell us the ip address, netmask, gateway address of the client
You are on a local network, so not over the internet?
What is the ip address of the router/modem you use?

First need to be 100+% be sure that your network is set up connect.

Do you use dhcp on your router, or have the ip addresses set fixed?

And if all is fine after we have said that, we’re going to check basic connectivity between the client and server side.

After that It’s time to set up the wfview server side and check out all the settings while the 7300 is on and connected as well as setup the right way, right speed, settings and all.

If that all (!) is fixed/checked, we’re going to the client part.

Withtout a basic klowledge of your network, there is no reliable way of telling what to do.

And if the server side of all is fixed, we’re doing the same for the client part.

The problem is that it takes at most 5 minutes to set up the server side and same for the client side normally.

Well I took the last suggestion and took it a little further. I went back to the very beginning.

  1. I went back to the ICOM-7300 and made the called for changes
  2. I went to the manuals and the information on the Internet and configured the server and it again worked.
  3. I went to the client and did the same.
  4. I then went back and changed the 50001-50002-50003 ports to 50007-50008-50009.
  5. i then went and erased my webroot security software and made sure the Microsoft Defender was turned off.

i still had work work with some of the settings but finally got it working on my Dell Latitude Laptop. The sound is now loud and clear.

I was able to get the screen up and working on my Asus Laptop but not the voice. Still working on why

The logs are

Client
https://termbin.com/2z2f
Server
https://termbin.com/7f3p

The problem is I had it working but when I turn it back on I can not get the client to connect. I had taken a snapshot of each configuration window for both the client and server and went back to compare to see if anything has changed and I am not able find any differences in the settings areas for either the client or the server.

I know one of the first questions is did you save the configuration settings before you shutdown the laptop and the answer is yes

I hope this makes some sense to you

I specifically ask you for information and you, again, totally drift off. No answers to questions.

I cannot help you.

First I would like to apologize not answering your questions. I am asking to accept my apology and rest assured that i will stay focused on what you need and get it to you in a timely fashion. I have tried to the best of my ability to answer the questions you asked. If I have missed anything or need more detail let me know.

Did you install the windows driver of the 7300 (icom site) without having the 7300 connected?
Yes

Tell us the ip address, netmask, gateway address of the client.
IPv4 Address. . . . . . . . . . . : 192.168.1.193
Subnet Mask . . . . . . . . . . . : 255.255.255.0

IPv4 Address. . . . . . . . . . . : 192.168.1.200 netmask for server
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::feae:34ff:fe24:d3f0%14
192.168.1.254

What is the ip address of the router/modem you use?
Do you use dhcp on your router, or have the ip addresses set fixed?
I am not sure of the answer to these questions and hope the data below answers the question. If not, Let me know what I need to do to get the data. It is the data from a ipconfig /all command on the client side. The client is a Dell Latitude Laptop.

Microsoft Windows [Version 10.0.22621.2283]
(c) Microsoft Corporation. All rights reserved.

C:\Users\blake>ipcpnfig
‘ipcpnfig’ is not recognized as an internal or external command,
operable program or batch file.

C:\Users\blake>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Annie
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : attlocal.net

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6E AX211 160MHz
Physical Address. . . . . . . . . : 8C-17-59-C6-E3-28
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2600:1702:3b10:7950::45(Preferred)
Lease Obtained. . . . . . . . . . : Thursday, September 21, 2023 11:35:26 AM
Lease Expires . . . . . . . . . . : Thursday, September 21, 2023 12:35:26 PM
IPv6 Address. . . . . . . . . . . : 2600:1702:3b10:7950:b5b1:6890:4104:729d(Preferred)
Temporary IPv6 Address. . . . . . : 2600:1702:3b10:7950:5020:669c:ed8d:5436(Preferred)
Link-local IPv6 Address . . . . . : fe80::cf86:e7a4:c2ff:7082%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.193(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, September 21, 2023 8:50:35 AM
Lease Expires . . . . . . . . . . : Friday, September 22, 2023 8:50:35 AM
Default Gateway . . . . . . . . . : fe80::feae:34ff:fe24:d3f0%11
192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 109844313
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2C-30-E4-36-8C-17-59-C6-E3-28
DNS Servers . . . . . . . . . . . : 2600:1702:3b10:7950::1
192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
attlocal.net

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 8C-17-59-C6-E3-29
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 8E-17-59-C6-E3-28
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 8C-17-59-C6-E3-2C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

You are on a local network, so not over the internet?
Yes -Both the client computer and the server computer are on the same network. Also the client and the server are running on two different Dell computers

What is the ip address of the router/modem you use?
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 109844313
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2C-30-E4-36-8C-17-59-C6-E3-28
DNS Servers . . . . . . . . . . . : 2600:1702:3b10:7950::1
192.168.1.254

What do you mean by “but not the voice” ?

I have reached my limit of expertise and patience. This application appears beyond my technical capabilities. I appreciate all your help and guidance. I was close but there is something I am missing and am unable to find it. To answer your last question, I was able to get the application to work most of the time. That is I am able to connect the server to my ICOM 7300 every time. I can connect the
client to the server most of the time. Not sure why sometimes I can connect and sometimes not.

So as I said earlier, I give up. It doesn’t help to have an individual who I answered their questions to the best of my ability came back with their sarcasm.

Again thank you for your help

but do not appreciate the sarcastic attitude of the other individual.

I am sorry - I wasn’t able to give you better information -

Hi Bob,

Running a server isn’t for everyone. I understand.

BTW your “not the voice” issue is probably because your server’s audio settings are still not correct.

2023-09-20 18:26:48.392 INF audio: "Server Audio output device Speakers (High Definition Audio Device) found! "

On your server, that should be the radio, generally “USB Audio CODEC” or similar name.

There are two audio devices, and on the server, both need to connect to the radio. One is for sending audio, the other for receiving it. That makes sense, right?

So check it and double-check it. Also FYI, you cannot set this parameter while anyone is connected, so be sure to save the settings and re-launch wfview just to make sure nobody is connected when the change happens. That’s what I do anyway.

–E
de W6EL

Thank you for your note. now I know part of the reason for my issues. You can change it when someone is connected. I am usually connected and am making the changes at the sever PC or at another laptop that is using Anydesk.

I will make the changes and see what happens