@Yaakov It's Utility>Menu>System Setting>I/O> Then it has LAN Config, Web Server, USB ID (not used), Net Storage (not set up). The LAN Config is set to Auto DHCP and shows IP Addr, Subnet, Gateway, VINC Port, and MAC Addr. The Web Server is only for setting a password, first left it blank then put 123 in it to see if it made a difference (it didn't). Could it be on the Win10 side? It does recognize a Non-Internet (intranet) Network. But putting the IP Addr into edge it times out due to nonresponse but recognized that the IP Addr is there?

 

It must be on the WIN10 side because when I dug into network diagnostics it is trying to connect with my WIFI that I also use instead of the wired ethernet to a hub connecting the computer, scope, and AWG. I am able to connect the scope and AWG but not the computer and scope. I am using a wireless chip and mouse on the scope as well instead of its touch screen.

 

@Yaakov It's Utility>Menu>System Setting>I/O> Then it has LAN Config, Web Server, USB ID (not used), Net Storage (not set up). The LAN Config is set to Auto DHCP and shows IP Addr, Subnet, Gateway, VINC Port, and MAC Addr. The Web Server is only for setting a password, first left it blank then put 123 in it to see if it made a difference (it didn't). Could it be on the Win10 side? It does recognize a Non-Internet (intranet) Network. But putting the IP Addr into edge it times out due to nonresponse but recognized that the IP Addr is there?

First, do some basic network troubleshooting using "ping".

On the WIN10 side,
Open a cmd window, then try to ping the scopes IP address:

C:\>ping n.n.n.n<enter>

Where n.n.n.n is the scopes IP address

report back.

 

Nope, not seeing it...
Pinging 10.11.13.221 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.11.13.221:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

But it does find the intranet hub

 

It must be on the WIN10 side because when I dug into network diagnostics it is trying to connect with my WIFI that I also use instead of the wired ethernet to a hub connecting the computer, scope, and AWG. I am able to connect the scope and AWG but not the computer and scope. I am using a wireless chip and mouse on the scope as well instead of its touch screen.

What is the netmask on on the scope, and on the Windows 10 machine? Also, that screenshot doesn't show an IPv4 address, it has one, right?

 

Nope, not seeing it...
Pinging 10.11.13.221 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.11.13.221:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

But it does find the intranet hub
View attachment 262103

Next....in the same cmd window, ping the WIN10 computer IP address with its own IP address

Report back.

 

Where do I find the IP Addr for the computer?

 

In a command window: ipconfig /all

 

Pinging 66.118.111.57 with 32 bytes of data:
Reply from 66.118.111.57: bytes=32 time=4ms TTL=64
Reply from 66.118.111.57: bytes=32 time=2ms TTL=64
Reply from 66.118.111.57: bytes=32 time=3ms TTL=64
Reply from 66.118.111.57: bytes=32 time=3ms TTL=64

Ping statistics for 66.118.111.57:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 4ms, Average = 3ms

also...
Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-OELCDB7
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Bench Instruments:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Killer E2400 Gigabit Ethernet Controller
Physical Address. . . . . . . . . : D8-9E-F3-99-66-33
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ddac:d3ad:a6c5:9ef5%9(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.158.245(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 165191411
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-B6-1D-98-D8-9E-F3-99-66-33
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Symantec TAP Driver
Physical Address. . . . . . . . . : 00-FF-3F-3F-1B-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 7C-67-A2-80-C1-91
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 7E-67-A2-80-C1-90
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3165
Physical Address. . . . . . . . . : 92-D7-7E-E6-0A-20
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::486e:1b34:2938:f141%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.129(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, March 3, 2022 1:26:14 PM
Lease Expires . . . . . . . . . . : Saturday, March 5, 2022 12:16:55 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 143841150
DHCPv6 Client DUID. . . . . . . . : 00-03-00-01-92-D7-7E-E6-0A-20
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:34a2:52f8:30f2:349e:bd89:90c6(Preferred)
Link-local IPv6 Address . . . . . : fe80::30f2:349e:bd89:90c6%11(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 251658240
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-B6-1D-98-D8-9E-F3-99-66-33
NetBIOS over Tcpip. . . . . . . . : Disabled

 

Your IP configuration looks overly complex.

So…

Let’s start with the network topology.

You have a windows desktop.
It appears to have both a wired network interface adapter and a wifi network interface adapter. Is this correct?

From the info provided in post #29:
Wired Network adapter:
169.254.158.245(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0

Wireless network adapter:
IPv4 Address. . . . . . . . . . . : 192.168.1.129(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0

Gateway is 192.168.1.1

You must also have a hardware router that provides an Internet service connection. Correct?

The router should have two IP addresses assigned to itself.

1) an external IP address assigned to the physical network adapter connected to the internet service provider

2) an internal IP address assigned to the physical network adapter connected to your internal “private” LAN network

Each of these interfaces have an IP address and Subnet mask assigned.

What is the address and subnet mask assigned to each interface?
(you'll have to look at the router configuration to know for sure)

From info in post #29:
External:
66.118.111.57

internal:
192.168.1.1 (implied by dhcp IP assignment to wireless network adaptor)
subnet mask: 255.255.255.0

 

@Yaakov It's Utility>Menu>System Setting>I/O> Then it has LAN Config, Web Server, USB ID (not used), Net Storage (not set up). The LAN Config is set to Auto DHCP and shows IP Addr, Subnet, Gateway, VINC Port, and MAC Addr. The Web Server is only for setting a password, first left it blank then put 123 in it to see if it made a difference (it didn't). Could it be on the Win10 side? It does recognize a Non-Internet (intranet) Network. But putting the IP Addr into edge it times out due to nonresponse but recognized that the IP Addr is there?

Deducing from the info in post #29:

What did you use for the scope:

IP address:
10.11.13.221 <----ok, but could have been in 192.168.1.n range

Subnet mask?
This can be 255.255.255.0

Gateway mask?
This should be 192.168.1.1

With the above noted settings, you should be able to ping without 0% loss.

 

t appears to have both a wired network interface adapter and a wifi network interface adapter. Is this correct?

Yes

You must also have a hardware router that provides an Internet service connection. Correct?

Yes

Do I need to connect my local instrument intranet to the existing network? I intended for this to be a small local net.

The router should have two IP addresses assigned to itself.

Having trouble logging onto router for this info...

 

Nope, PC doesn't find it. Beginning to think my son may not have plugged in the computer to the hub. Not home ATM so will have to get him to check later.

Pinging 10.11.13.221 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.11.13.221:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

Do I need to connect my local instrument intranet to the existing network? I intended for this to be a small local net.

I think your "instrument network" is physically isolated from your PC network.
You need to connect the instrument network to the PC network.

Usually, the router provides DHCP services to the internal network. If the router supports both wireless and wired networks, then the same "gateway' address would be auto assigned (via DHCP) to any device on the internal network, be it wired or wireless. Technically, you only have one logical internal network, so all devices should be auto assigned an IP address in the 192.168.1.n address range via DHCP.

So...in summary, this is what you should have been able to do:

First...connect the new hub to the internal PC network.
Then, verify each of your instruments support DHCP, then enable DHCP on the instrument.
Then, connect the instrument to the network and reboot it.
After it reboots, it should have obtained a new IP address assigned in the 192.168.1.n range along with subnet mask 255.255.255.0 and gateway address of 192.168.1.1.
Verify the device connectivity by using "ping" from the WIN10 PC.

Note-
If the device supports IP connectivity, but doesn't support DHCP, then you will have to manually assign a specific IP address, subnet mask, and gateway, then exclude the IP address from DHCP in the router's DHCP configuration. What I do is restrict the DHCP IP allocation range (on the router) then manually assign an IP addrees outside the allocation range to prevent conflicts.

 

First...connect the new hub to the internal PC network.

Therein lies the rub... There is no wired network connection in my room. Looks like I will need a fast throughput 5G WIFI to ethernet extender in front of the hub. Any suggestions?

 

Therein lies the rub... There is no wired network connection in my room. Looks like I will need a fast throughput 5G WIFI to ethernet extender in front of the hub. Any suggestions?

Look at TPLink devices.

They can use the AC wiring to communicate between network devices.

Each unit plugs into an AC outlet and establishes an Ethernet connection .

 

Why is there any need for a physical network? Why is there a need for a hub? Do all your devices support WiFi?

Configure WiFi on each device to connect to the existing WiFi network. That should be as easy as specifying the network WiFi id and providing the password.

Your device will connect to your WiFi access point (sometimes contained in the router) and the access point normally supplies all the TCP/IP configuration to the device. IP address, gateway, mask are all supplied by DHCP on the access point. I’ve connected dozens of devices all on the same network in this manner.

You can have two wireless networks on a single access point, by specifying different network named. Again, devices in either network are configured automatically.

If any device needs a static IP address, you need to exclude a range of IP addresses in your DHCP server. Once you connect with DHCP, I reconfigure the devices Ethernet settings by unchecking DHCP and adding a static address and associated mask and gateway parks. You can determine these by reviewing your DHCP settings or connecting with DHCP and manually noting the assigned setting with a command like ipconfig/all

 

Do all your devices support WiFi?

No, they don't, that is the problem. The scope and AWG are plugged into the new hub and are communicating with each other. But for the scope to be controlled via the PC it requires a LAN connection. I do not have a wired connection in the room. Both computers are using WIFI network connections for the network printers and internet. Still need to get around to implementing backup NAS.

Look at TPLink devices.

Will do. Heard about it but no experience with it. I did go ahead and order a hi transfer speed dual band WIFI extender with 2 ethernet ports. Already have a couple in use for laptops and entertainment center. I do much prefer wired and may at some time get the housed wired for it. So TPLink may be the solution.

 

No, they don't, that is the problem. The scope and AWG are plugged into the new hub and are communicating with each other. But for the scope to be controlled via the PC

Do they have USB? Then you can use a WiFi dongle , like this one. A Google search for “USB WiFi dongle” turned up almost 800 products.

 

They do, the scope has 2 type A on the front plus a type B on the rear. The front ones are used for a mouse dongle and USB drive. The AWG has 1 type A on the front for USB drive and a type B on the rear. I first tried simply connecting the type B ports to the computer but the Bode Plot function on the scope requires a LAN connection, so... I think type B ports are for file transfer to a remote drive i.e. the PC. So, I need to use ethernet ports. Those do look interesting and would surely be better than adding a WIFI card to PCs that have USB ports available if they have decent throughput speed. I'll keep them in mind. Thanks for the heads up DJ!