Not a bad recommendation at all. I'll make the changes, test and follow up. ... View more

This is WSAM and is just configured for Outlook. Such a weird problem. ... View more

OK, so what I said was accurate then. It will send it to the default VLAN. The default VLAN on Crisco can be changed, but that doesn't move things like STP or Crisco proprietary stuff over, that still remains on VLAN 1. Word. ... View more

All, From what I have gathered from this incredibly long thread is that you are trying to use the physical interface (which cannot be tagged) and sub-interfaces (which can be tagged). I'm going to talk Foundry since that's the evil I know. On a Foundry, there is what is called dual-mode. On the physical interface of the switch, you configure it for dual-mode, and tell the interface for what default VLAN you want untagged traffic dropped into. All other traffic will be tagged (802.1q) and will be dropped into the proper VLAN. Example: conf t int e 1 dual-mode 111 vlan 112 tag e 1 vlan 113 tag e 1 vlan 111 untag e 1 Someone in the world of Crisco, can you confirm what I'm saying: If a dot1q trunk receives a tagged frame on the native vlan, it drops it. When a cisco trunk port receives untagged frames it forwards them to the native vlan #1 by default So, if you want the native VLAN to be something other than 1, you can change the default VLAN, but this does not move STP or other Crisco things from VLAN 1. Message Edited by Munpe_Q on 11-17-2008 05:54 PM Message Edited by Munpe_Q on 11-17-2008 05:54 PM ... View more

Actually it won't prevent that at all, in fact once you get your head wrapped around it, you'll see how much flexibility you have with LDAP to AD. I promise. ... View more

In my experience, using LDAP authentication against AD is the most flexible for what you are trying to do. You will be able to see groups and OU's very easily. Do you have an option of moving your auth to LDAP? ... View more