Hi all.
I'm running a TS-453BT3 with a 10gbe card as a video editing NAS. On the PC side, I'm running Windows 10 with a 10gbe card. The two devices are connected with a CAT8 cable. Additionally, both are also connected to a local switch for direct connect to my ISP. All the connections work fine individually.
The problem is that I'm finding that the NAS and PC are primarily communicating through the switch, so editing and file transfer speeds suffer quite a bit. If I unplug the NAS from the switch, the connection moves to the 10gbe and transfer speeds jump.
To state the question: How do I get the NAS and the PC to communicate over the 10gbe connection instead of the 1gbe switch?
Thanks!
QNAP and Windows communicating over wrong connection
-
- Starting out
- Posts: 15
- Joined: Wed Jul 10, 2019 2:37 am
- dolbyman
- Guru
- Posts: 35273
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: QNAP and Windows communicating over wrong connection
if you use a direct connection for 10GbE, set this connection to a separate subnet and mount shares via that subnet
e.g.
regular 1GbE subnet (with gateway) 192.168.1.0/24 (DHCP)
dedicated 10GbE subnet 192.168.10.0/24 (static IPs)
e.g.
regular 1GbE subnet (with gateway) 192.168.1.0/24 (DHCP)
dedicated 10GbE subnet 192.168.10.0/24 (static IPs)
-
- Experience counts
- Posts: 2043
- Joined: Thu Mar 03, 2016 1:11 am
Re: QNAP and Windows communicating over wrong connection
A dozen times asked, a dozen times answered!
Use a dedicated subnet without a gateway for the 10g connection and connect PC and NAS using this dedicated network (i.e. 10.0.0.1/255.0.0.0 and 10.0.0.2/255.0.0.0).
The 1g can use the current IPs for internet access.
If more details needed, please use forum search!
Regards
Edit: to late dolbyman was faster
Use a dedicated subnet without a gateway for the 10g connection and connect PC and NAS using this dedicated network (i.e. 10.0.0.1/255.0.0.0 and 10.0.0.2/255.0.0.0).
The 1g can use the current IPs for internet access.
If more details needed, please use forum search!
Regards
Edit: to late dolbyman was faster
A raid is never a substitute for backup! Never!
Deadbolt - READ 1st post!!!
Deadbolt - information
Deadbolt - find your OP_RETURN!
VPN=VPN? No!
How to clean up your NAS after malware attack
www.raidisnotabackup.com
Deadbolt - READ 1st post!!!
Deadbolt - information
Deadbolt - find your OP_RETURN!
VPN=VPN? No!
How to clean up your NAS after malware attack
www.raidisnotabackup.com
-
- Starting out
- Posts: 15
- Joined: Wed Jul 10, 2019 2:37 am
Re: QNAP and Windows communicating over wrong connection
Made a couple of adjustments and still having issues:
QNAP - Adapter 1 (1Gbe) - IP: 192.168.0.146 - Subnet Mask: 255.255.255.0
QNAP - Adapter 3 (10Gbe) - IP: 192.168.2.3 - Subnet Mask: 255.255.254.0
PC - Ethernet 1 (1Gbe) - IP: Obtained Automatically -
PC - Ethernet 2 (10Gbe) - IP: 192.168.2.8 - Subnet Mask: 255.255.254.0
Seems like everything should be separated - what am I missing?
Thanks
QNAP - Adapter 1 (1Gbe) - IP: 192.168.0.146 - Subnet Mask: 255.255.255.0
QNAP - Adapter 3 (10Gbe) - IP: 192.168.2.3 - Subnet Mask: 255.255.254.0
PC - Ethernet 1 (1Gbe) - IP: Obtained Automatically -
PC - Ethernet 2 (10Gbe) - IP: 192.168.2.8 - Subnet Mask: 255.255.254.0
Seems like everything should be separated - what am I missing?
Thanks
- dolbyman
- Guru
- Posts: 35273
- Joined: Sat Feb 12, 2011 2:11 am
- Location: Vancouver BC , Canada
Re: QNAP and Windows communicating over wrong connection
Why is the subnet mask a /23?
Anyways, did you mount the shares on the dedicated subnet then ?
Anyways, did you mount the shares on the dedicated subnet then ?
-
- Starting out
- Posts: 15
- Joined: Wed Jul 10, 2019 2:37 am
Re: QNAP and Windows communicating over wrong connection
Finally got it. I had unmounted the old connection, but there was a shortcut to a folder keeping it alive somehow. Also, I found that when I tried to connect to the 10gbe adapter directly, QTS would put my PC's IP address in jail for 5 minutes. Deleted the shortcut, whitelisted the IP. Everything is running really well, now.
Thanks guys!
Thanks guys!