DNS + Trunking are KILLING ME (TS-869 Pro)

[dewder]

I have a Zyxel 48 port switch GS-1548 (supports all port trunk modes), and a TS-869 Pro that I'm using in my small business. I am connecting about 25 machines to the switch.

The problem is no matter what trunking configuration I try, the TS is only discoverable with the finder. No IP or server name access works through explorer.

I've tried EVERY SINGLE configuration possible, both in combination with the two ports trunked on the switched and not.
e.g:
RR + ports 47+48 trunked on switch
RR + ports 47+48 non trunked on switch
802.3ad + ports 47+48 trunked on switch
802.3ad + ports 47+48 non trunked on switch
etc....

What am I doing wrong?

Next, even though if I turn off trunking and the NAS is discoverable once again on the network, it complains DNS is not correct (set it as the same as my router 10.0.0.1) and it cannot live update nor can I use alerts or OpenVPN.

Please help.

[pwilson]

I have a Zyxel 48 port switch GS-1548 (supports all port trunk modes), and a TS-869 Pro that I'm using in my small business. I am connecting about 25 machines to the switch.

The problem is no matter what trunking configuration I try, the TS is only discoverable with the finder. No IP or server name access works through explorer.

I've tried EVERY SINGLE configuration possible, both in combination with the two ports trunked on the switched and not.
e.g:
RR + ports 47+48 trunked on switch
RR + ports 47+48 non trunked on switch
802.3ad + ports 47+48 trunked on switch
802.3ad + ports 47+48 non trunked on switch
etc....

What am I doing wrong?

Next, even though if I turn off trunking and the NAS is discoverable once again on the network, it complains DNS is not correct (set it as the same as my router 10.0.0.1) and it cannot live update nor can I use alerts or OpenVPN.

Please help.

OpenVPN typically wants 10.0.0.1 for itself in a standard configuration. Perhaps your Router and your NAS are both attempting to grab this IP address. Try moving your network to a different PrivateNet, or use scripting to establish VPN connection, so you can use different IP's for OpenVPN.

Afraid I'm not qualified to address your trunking issues, as I don't use it personally.

Patrick.

[dewder]

Can I just use different manual IPs for my router and NAS instead of scripting the VPN?

Afraid I don't know the first thing about scripting network settings.

[pwilson]

Can I just use different manual IPs for my router and NAS instead of scripting the VPN?

Yes you can. Unfortunately it is indeed probably less work to reconfigure your network to stay away from 10.0.0.0 network, as this will resolve this issue. It's work to do so, but it will alleviate the need to script OpenVPN.

Patrick.

[schumaku]

Start the configuration with the basics, ie. first single LAN, then trunking, - once it's running reliably (should be a no-brainer honestly...), configure the VPN required.

Ensure the VPN does not make use of the same TCP/IP subnet as the LAN - things can and will go wrong. Rememer, the VPN implementation on the NAS are _not_ bridged ot the LAN, it's routed and NATed.

Just change the OpenVPN pool IP address range, this will also change the NAS OpenVPN .1 base address - there is neither a need for scripting required, nor the reconfiguation of your complete LAN subnet.

In case you are running more than one 802.3ad trunk on the switch - ensure each group has it's own ID.