This is probably related to how to properly setup trunk ports but is very specific to getting SonicPoints. to work across switch trunks. I currently have 3 Sonicpoints working and provisioned properly. They are setup as follows:
SonicWall NSA240 X3 interface:

The SonicWall X3 interface is connected as a trunk port to my Cisco GE11 configured as a trunk port with the PVID =23 and then tagged trunks 24,25, and 26 (to support my 3 VAPs). The PVID of 23 is what I chose to use for the SonicPoint provisioning, management, and DHCP for the devices vs PVID of 1 (used for the PC LAN). The 3 SonicPoints are connected to the same Cisco on ports 8, 9, and 10 and the ports are setup the same way with PVID =23, and Tagged trunks 24-26. This hasn't changed for a couple of years and has worked fine. Now I need to add 2 more SonicPoints to the other side of the building that is connected via a fiber trunk. I setup the ports the Sonic on that Cisco as trunk ports - the same way as the current 3. I then setup my trunk between the areas as trunk ports with the native VLAN as 1 and tagged trunks as 23,24,25, and 26. Since my native VLAN on the ports for the SonicPoints is 23, I'm not sure how that traffic is maintaining its tag when going across the main trunk between building. The Sonicpoints are not being provisioned in this setup.
Any ideas on how my config should be different to enable this to work? I thought about setting up the X3 interface with one more sub interface that would be tagged and somehow having the provisioning of the SonicPoint work over that.
Thanks for any help.