Packet captures from other hosts getting pinged by this server successfully show everything functioning as normal. BTW, both the VOIP VLAN server and the NSA 240 are both untagged in their respective VLANs. I think it must be a security setting on the NSA 240. I have the router connected to a port on th switch which I designated a trunk port. To me this proves (although i certainly could be wrong) that there is nothing wrong with the VLANs or 元 routing. The NSA 240 from its diagnostic screen however, CAN ping this exact same server. The server that needs internet access in the VOIP VLAN (VLAN 50) can ping everything else on the default VLAN (as the Procurve is an 元 switch and has routing enabled) except for the LAN interface of the NSA 240. Currently the Sonicwall NSA 240 firewall is set on one of the switches' Untagged ports in VLAN 1. First, the 'stick' is just a single router interface. The router has physical connections to the broadcast domains where one or more VLANs require the need for routing between them. It is a method of inter-VLAN (virtual local area networks) routing where one router is connected to a switch via a single cable. Some ports are setup as "access" ports (called "Untagged" in HP Procurve speak) some are "trunk" ports (called "Tagged" or "Auto" in HP Procurve speak). In computing, a router on a stick, also known as a one-armed router, is a router that has a single physical or logical connection to a network. A particular kind of inter-VLAN routing, called Router-On-A-Stick, uses a trunk from the router to the switch to enable all VLANs to pass to the router. The switch is split into 2 VLANS one for VOIP and the default VLAN. Trunks allow the traffic from multiple VLANS to travel over a single link, while keeping the VLAN identification and segmentation intact.