Thanks for the responses everyone! I'm in an unfortunate situation where my ability to 'test' network settings is very limited. I don't want to risk changing port types at the moment because the network is actively in use, and the physical cables are not labeled well enough for me to know what's plugged in to which port.   The real issue I am getting ready to tackle is this: our VLAN 1 network uses 192.168.1.xx, and we also use VPN and Remote Desktop Connection to access our VLAN 1 devices (desktop PCs). We do this so that we can connect and work from home and from client offices.    However, we frequently run into an issue, and I think it is related to the IP address of the client office using '192.168.1.xx' as well as our office using the same IP address. We think the fix is to just change our VLAN addresses to something different, like '192.168.50.xx' to limit potential conflicts while using VPN from other sites.   In preparation to do that, I was tinkering with adding a new VLAN, but I think it may be best to just change the Address of VLAN 1 instead of creating an entirely new VLAN. ... View more

Thank you so much for the article! I'm a novice at networking so that article was very helpful, but it has made me question something I used to take for granted:   We often use Remote Desktop Connection from a VLAN 2 device to access a VLAN 1 device. How does this work? I imagine the VLAN 2 device gets 'tagged' at the 'Native VLAN 2' trunk port as 'VLAN 2', but then how does it get to a VLAN 1 device (which is behind a 'Native VLAN 1' trunk port)?    We also do a similar thing through VPN, we connect to the office on VPN, then use RDC to take over our desktops for work. How does the VLAN tagging work for that? ... View more