Thanks for posting up the config. I Suggest removing vlan association on VLAN 100. You may need to add a static route for the remote subnet. Something along the lines of: ip route 192.168.5.0 255.255.255.0 192.168.6.9   Which device has IP address 192.168.255.2? I am not sure I am fully understanding the static route on the router.
I recently inherited an old network with a failing 3com switch. I am trying to replace the 3com switch in the simplest manner possible with a N2048.  Currently, our ISP connection comes in on port 24 (via ethernet handoff from a Level3 router in our basement) on the 3com switch and our firewall plugs in port 48 of the 3com switch. I have attempted to configure the N2048 exactly the same as the existing 3com switch. When I do this and patch the connection in, I have connectivity in our local subnet as well as internet. However, I cannot communicate to a subnet that connects to a remote office. Local subnet: 192.168.6.0/24Local internet gateway: 192.168.6.38Local gateway for remote subnet: 192.168.6.9Remote subnet: 192.168.5.0/24 The remote subnet is accessed through the same connection as the internet via vLAN and static route that the ISP set up. I have the original document that the ISP provided for the configuration as follows: Customer CPE WAN Interface Configuration Requirements: 100M Full Duplex Customer WAN  Netblock(s) CIDR - Subnet Mask: Vlan 100  207.67.73.184/29 - 255.255.255.248Vlan 1 192.168.255.0/30 - 255.255.255.252 Customer CPE Default GW / Remote  Neighbor IP:207.67.73.185192.168.255.1 Static Route:192.168.6.0/24 - 255.255.255.0 destination 192.168.255.2 On the N2048 ports 1-48 are members of VLAN 1 and ports 24,48 are members of VLAN 100.VLAN 1 are untagged and VLAN 100 are tagged.  Comparing the 3COM and N2048 switch everything seems to configured the same. It seems this should be a simple setup but I cannot figure out why the N2048 will not communicate with the remote subnet.  Any thoughts or advice would be greatly appreciated. 
Using N2048 vLANs in shared circuit