Kinda sounds like you don't have the native VLAN setup correctly on your trunk. For instance, if your server is part of VLAN 100, your trunk config would be:
interface fa0/1 switchport trunk encapsulation dot1q switchport mode trunk switchport trunk native vlan 100 Hope this helps! Aaron T. Rohyans Senior Network Engineer CCIE #21945, CCSP, CCNA, CQS-Firewall, CQS-IPS, CQS-VPN, ISSP, CISP, JNCIA-ER DPSciences Corporation 7400 N. Shadeland Ave., Suite 245 Indianapolis, IN 46250 Office: (317) 348-0099 Fax: (317) 849-7134 arohy...@dpsciences.com <mailto:arohy...@dpsciences.com> http://www.dpsciences.com/ <http://www.dpsciences.com/> From: Webb, Brian (Corp) [mailto:brian.w...@teldta.com] Sent: Friday, July 24, 2009 3:43 PM To: NT System Admin Issues Subject: VLAN tagging in Windows 2003 x64 Anyone seen any issues with VLAN tagging on a Windows 2003 x64 machine? We are trying to move a NetBackup server from an x86 machine to an x64 machine and are having problems getting the multiple VLANs on a single NIC to work. We have had our network people check the Cisco trunking config 3 different times and they say it is right. Ping works to all VLANs. Tracert works to all VLANs and shows only the one hop as expected when going to a machine a VLAN that is tagged. RDP fails when connecting to a host on a tagged VLAN, but works when the target is on the default VLAN (or VLAN that can be reached by route on the default VLAN). Any ideas? We are using the most recent HP teaming NIC drivers with the 2 built in HP NICs teamed in a fault tolerant with preference config and the tagged VLANs are listed in the HP network configuration. Brian Webb ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
