Hi guys, I just installed a linksys gigabit network adapter EG1032 on a vista 32bit system. The adapter supports vlan tagging. After installing the drivers and enabling vlans in the configure section of the adapter, I still cannot seem to see any of the vlans coming in. I tried researching for utilities that will enable me to configure the system to see the vlans by ID number but nothing so far except the intel proset utility which, ofcourse, wont work with my adapter. How can I configure my vista machines for particular vlans? any help would be appreciated. Thank you

After installing the drivers and enabling vlans in the configure section of the adapter, I still cannot seem to see any of the vlans coming in. Coming in from where exactly? Are you plugged into a network utilizing enterprise level managed switches, routers and VLAN tagging? Or, are you plugged into your SOHO router at home? If the former, use a packet sniffer like WireShark to view LAN traffic. If the latter, it's not going to happen as there won't be any VLAN traffic. How can I configure my vista machines for particular vlans? Actually, you don't. You configure the port(s) of the switch the PC is plugged into for a particular VLAN. This of course requires an enterprise level, managed, VLAN capable switch. From the sounds of your post, I suspect your knowledge of VLAN tagging is very limited. It might do you well to do some reading/research on the subject before you go any further just to expand your own knowledge in that area.

Thank you for your prompt response. I am indeed connected to a vlan capable switch. the port in which the PC is configured with 3 vlans (different tags). However, I am not able to reach any machines connected on any of the vlans despite having configured my IPs to match the subnets of the vlans. I even tried deisabling 2 of the vlans and have the switch provide me with just one tagged vlan, still nothing. If I switch the port to untagged, ofcourse, I get to see the network just fine. My knowledge in vlans is mediocre at best, however, I really dont see the difficulty in what I am trying to do or what I am doing wrong. Any guidance would be appreciated, thank you.

ip is a layer above vlan and as such doesn't apply. A vlan is a hardware switch, just like a light switch. You can have a light that goes on from one switch up to many switches. Same idea with vlans. "I really dont see the difficulty in what I am trying to do" What are you trying to do with vlans? What do you think they will do for you?

My knowledge in vlans is mediocre at best, however, I really dont see the difficulty in what I am trying to do or what I am doing wrong. Not an uncommmon assumption. However, if you're not aware of the old adage regarding the word "assume", here it is: Assume - makes an ass out of u and me and well, you've just assumed. While not an overly complex technology, one does need a good solid basic understanding of both networking and subnetting in order to understand VLAN tagging. I am indeed connected to a vlan capable switch. the port in which the PC is configured with 3 vlans (different tags). However, I am not able to reach any machines connected on any of the vlans despite having configured my IPs to match the subnets of the vlans. Ok, you can't have multiple VLAN's on the same port unless it's a trunk port. In most cases, the trunk port is tagged "tag all" and carries all assigned VLAN's on the management VLAN. These trunk ports are used when interconnecting switches. I even tried deisabling 2 of the vlans and have the switch provide me with just one tagged vlan, still nothing. If I switch the port to untagged, ofcourse, I get to see the network just fine. First off, your sketchy details are making this tougher than it needed to be. If you had put in your original post that you were plugged into a VLAN capable switch and put the make/model of the switch in as well, I wouldn't have had to ask about the switch in my first response. I also wouldn't be asking you what make/model switch right now. Without further ado....what make/model switch are you using? Different OEM's use different nomenclature and are configured differently. So that's why I'd like to know what make/model you have, it would help me to help you...especially if I'm familiar with that switch and it's operating system. Chances are, when you configured the port with 3 VLAN's, you were forced to make it a trunk. If you removed two of the tags without changing it from a trunk to an access port, then it still won't work. Now, having said that. I'm going to do some assuming myself (and I do not like to assume but you've left me no choice...lol) Assuming you have only the one switch, no routers and several PC's and/or laptops. On the switch, configure two VLANs. Most all switches I've worked with have VLAN 1 as the default. By default it's also the management VLAN. Just leave it alone for now and make two more: VLAN 2 and VLAN 3 Assign a contiguous block of ports to each VLAN. Say ports 2-12 for VLAN 2 and ports 13-24 for VLAN 3. Now take two PC's and give them IP's within the same subnet and plug them into two of the VLAN 2 ports. They should communicate with each other without problem. Take one of those two PC's and plug it into a port for VLAN 3, communication should stop. Now move the other PC to a port in VLAN 3 and they should start communicating again. The above is a very basic setup but will tell you if your tagging is working as it should.