QNAP NAS Community Forum

Posted: **Wed Sep 11, 2019 10:09 am**

Hi Guys,
I'm trying to connect a Windows Test server to the second port on my TS-431P QNAP device.
I basically want to restore large backups from the QNAP NAS to my Server without using up all the available bandwidth on my primary network.

My primary LAN is 10.2.2.x
My secondary LAN is 10.5.5.x

My Test Server has 4 ports of which only two are connected / configured. One with 10.2.2.10 and the other with 10.5.5.10
My QNAP device has 2 ports. Once is configured to use 10.2.2.23 and the other with 10.5.5.2
These two devices can see each other on the primary LAN but I want them to be able to communicate on the second LAN.

The primary LAN is still working no problem but...
I can't ping 10.5.5.2 from my test server and
I can't ping 10.5.5.10 from a telnet session on my Qnap device.
I can ping 10.2.2.23 from my test server and
I can ping 10.2.2.10 from the Qnap device

My first thought is I need to add a static route on both devices so the system knows which interface to use and not try and use the default gateway.
Here is the route table from my Windows Server
This is the static route entry I added.

Code: Select all

10.5.5.0    255.255.255.0        10.5.5.10        10.2.2.10     11

Code: Select all

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.2.2.5        10.2.2.10    266
         10.2.2.0    255.255.255.0         On-link         10.2.2.10    266
        10.2.2.10  255.255.255.255         On-link         10.2.2.10    266
       10.2.2.255  255.255.255.255         On-link         10.2.2.10    266
         10.5.5.0    255.255.255.0        10.5.5.10        10.2.2.10     11
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link         10.2.2.10    266
        224.0.0.0        240.0.0.0         On-link         10.5.5.10    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link         10.2.2.10    266
  255.255.255.255  255.255.255.255         On-link         10.5.5.10    266
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0         10.2.2.5  Default
===========================================================================

When I do a Tracert to 10.5.5.10 on my windows server it looks out on the internet and of course fails.

When I do a traceroute on the qnap device it succeeds with a suprisingly long round trip time.
[~] # traceroute 10.5.5.10
traceroute to 10.5.5.10 (10.5.5.10), 30 hops max, 38 byte packets
1 QNAP2.campsie.local (10.5.5.2) 3000.654 ms !H 2999.518 ms !H 2999.869 ms

I have not modified the routing table on my QNAP device and this is how it looks now.
https://drive.google.com/file/d/11XwMVO ... sp=sharing
https://drive.google.com/file/d/1eKCYxz ... sp=sharing
I tried doing the pictures in line but it didn't work so here they are as links.

I have allowed ping through the windows firewall. I also tried with the firewall disabled.

Any suggestions or ideas on where I'm going wrong or what I'm missing here?

Posted: **Thu Sep 12, 2019 12:18 pm**

What r u using to copy from NAS to PC?

Posted: **Thu Sep 12, 2019 1:47 pm**

I have noticed if I try and do a tracert from my Windows machine it is using the default gateway not the specified route.
So the problem seems to be on my windows machine.

C:\Users\Administrator>tracert 10.5.5.2

Code: Select all

Tracing route to 10.5.5.2 over a maximum of 30 hops
  1     7 ms     5 ms     1 ms  10.2.2.5
  2    18 ms    18 ms    18 ms  gw1.nsw.asp.telstra.net [203.45.254.1
  3     *     ^C

Has anyone come across this behaviour before?

Posted: **Thu Sep 12, 2019 3:51 pm**

you say you added this route.

Code: Select all

10.5.5.0    255.255.255.0        10.5.5.10        10.2.2.10     11

Code: Select all

Network Destination	Netmask		Gateway		Interface	Metric
10.5.5.0		255.255.255.0	10.5.5.10	10.2.2.10	11

so you have forced any 10.5.5.0 access via the 10.2.2.10 interface. are you not connecting the 10.5.5.x interfaces directly? or have you another switch?

Posted: **Mon Sep 23, 2019 2:01 pm**

Hi Toxic17,
Sorry for not getting back to you. Seems the notifications on this forum aren't working for me.
I had a second LAN cable connected directly from a second port on the server to the second port on the QNAP NAS.

I gave up on the two port idea and when back to a single adapter on the primary NAS port.
I eventually got that to work.

Thanks for your interest.
David

QNAP NAS Community Forum

Configure Second Network Adapter

Configure Second Network Adapter

Re: Configure Second Network Adapter

Re: Configure Second Network Adapter

Re: Configure Second Network Adapter

Re: Configure Second Network Adapter