I reading your post a question that comes to mind is desktop vs. server. The server adapter supports the multiple VLAN, but not the desktop. Before posting this I contacted some folks over in our NIC adapter group and asked for more guidance. A few questions first so I can go obtain the correct help:
1. Is the NIC onboard or add-in? If onboard it is desktop adapter and may require an actual server adapter to correctly achieve the goal.
2. Does PROSet show the NIC as having the capability to configure multi-VLANs?
You are using the correct protocol 802.1q, but the concern is whether you are using a desktop adapter (which would not have the required firmware) or server adapter.
I have the exact same problem.
My NIC is an add-in Intel Pro 1000 GT Desktop Adapter. I do have the capability to configure multi-VLANs.
The VLANs receive a DHCP address but they can't communicate on the network. I took a packet capture and it shows the NIC is sending out ARPs and the switch is replying back to the NIC but the NIC keeps asking for the ARP over and over again.
ie. NIC says "who has the mac-address for 172.31.6.1" ?
switch says "here's the mac-address".
this keeps repeating over and over
the only way I've been able to get it to work is by statically creating an ARP entry on the Windows system for the default gateway.
Is the desktop adapter just not compatible with multi-VLANs?
I have the same problem with the Pro 1000 MT Server Adaptor.
Ipconfig/all shows each VLAN nic as having the same MAC address and you can't selectively change them, if you change one they all change, I suspect this is the problem, and if it is then it's a driver issue I'd say??
Any assistance here would be appreciated Intel.......
I also run into problems related to this post.
Some Vlans need special treatment which is accomplished by sourcing from a different mac address. Now this is not possible with the CT and PL desktop network adapters which I own. Is there a sollution for this issue?
Sometimes you must let go an issue if you aren't able to figure it out fast. I was in that state, but I have fixed the problem.
As stated above, you can change the root mac address and all the vlans, that you have configured, will source from that locally administered address. Since the mac address is locally significant on a network subnet it doesn't matter that it is the same address. So.....my issue is gone.