VLAN support on Intel 82567LM on Latitude E6500?

Has anyone else tried getting the VLAN support working on a Dell Latitude E6500? The network device I have is a "Intel(R) 82567LM Gigabit Network Connection".

Using the latest drivers available from support.dell.com, both the Dell download page and the driver report it as version 9.50.14.2. The Dell download page states it as A01, and dated 2009-02-24. The driver reports a date of 2008-04-04.

Under the "Advanced" tab of the properties from Device Manager, it shows "Priority & VLAN" as set to "Priority & VLAN Enabled". However, it doesn't appear to provide a way to add and configure the VLANs. For Intel network cards, this typically requires the Intel PROSet application. The only download I can find from Dell is the "Intel 825xx Gigabit Platform LAN Network Device - Application", 14.0.2/Gold Build 01, A00, 2008-08-13 - and it is for 32-bit Windows only. I'm running Vista 64-bit SP2.

I tried using the "base drivers" / "generic version" directly from Intel - version 14, 2009-04-01. This updated the reported driver version to 9.52.20.2 / 2008-11-21. It also provided an extra "VLANs" and other context tabs on the properties from Device Manager.

From here, I can add additional VLANs. They are listed under the context tab, and the additional virtual adapters appear underneath "Network Connections". However, the "Status" of these VLANs on the VLANs context tab is always listed as "Disabled". Also, the virtual network connection always shows itself as "Network cable unplugged" in "Network Connections", while the base network connection appears normal. I can find no way of "enabling" these VLANs. I have this working with other Intel network adapters on other computers (desktops and notebooks), but now I'm at a loss.

Thanks!

 

May I ask what you're trying to do? VLANs are configured on the switch. You won't even see dot1Q tags unless you're plugged into a trunk port.

 

Certainly. However, you're not entirely correct. I can configure the switch to not strip the VLAN tags on a per-port basis - essentially making them trunk ports, or possibly "semi-trunk" ports, depending upon the exact configuration.

The network adapter can be configured to emulate additional adapters to the operating system - one per configured VLAN. I don't believe that a specific network adapter or special hardware is even required for this, just a supporting driver. This essentially means I can split the one network adapter on my desktop or laptop into 16 more more Gigabit ports for different uses, though with shared bandwidth. I could even perform routing between the network segments in this aspect if desired.

I've successfully created these additional emulated adapters through the upgraded driver (from Intel, not Dell). The issue is just that these adapters do not currently appear as "functional" - due to a driver issue, I'm guessing. It's possible that this is a Vista and/or a 64-bit issue, which I plan on testing soon with 32-bit and Windows XP installs to try to narrow-down the issue.

 

Some additional details - I just noticed that there are 2 errors being logged to the Windows Event Log under System for each attempt. Both with "Source" of "iANSMiniport".

The first has Event ID 3: Unable to read required registry parameters. To resolve, remove the adapter team and then create a new team.
The second has Event ID 4: Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.

Note that I certainly have attempted to remove and re-create the virtual adapters multiple times, as well as the physical adapter configuration and drivers. (Here, "adapter team" is probably overly-generic of the error message, though VLANs are considered part of the "teaming" functionality. Otherwise, I have made no attempt at enabling teaming (fault tolerance) - nor is this possible with only one physical adapter.)

I do have an open support case with Dell on this. They originally refused my request as "VLAN Setup and Configuration" is on their list of "advanced features" that are not supported by Dell technical support. However, after I explained that Intel will not support my either since Dell has the support responsibility as the OEM, they have apparently reconsidered and are following-up on my request. I'll keep this thread updated with any solutions that may arise.

 

Working properly and as expected under Vista 32-bit.

Also working properly on a fresh install of Vista 64-bit SP1. Also working after upgraded to SP2.

There is certainly still an issue here. Unfortunately, without any additional logging or other details available from Intel, I'm not sure I'll find out what it is short of re-installing.

 

I have noticed the exact same problem as you.

Windows Vista x64 Business

Same errors in my event log. Using intel drivers for the onboard nic provided in a dell optiplex 755 (Intel 8266DM-2 Gigabit Adapter).

I'm thinking it may be a conflict between what the intel driver is trying to do and a service also bound to that nic. I have vmware workstation 6.5 installed on this machine which binds a few extra things to my nics.

Do you have vmware workstation installed? if so, did you have it installed on your test setups?

I have set up everything properly on my Cisco 4509 switch by enabling dot1q on the port and enabling trunking on the switch port...

I noticed in the properties of my physical adapter accessed via device manager, in the vlan tab, that the vlans I have created are set as "disabled". Theres no way I can enable them... the virtual adapters are enabled and state that they are "working properly".

Very odd.

 

asphix20 - I did not have VMware installed, but I did have the similar Sun VirtualBox installed. I've not reinstalled it yet, but will re-test immediately after I do, and will post my results.

 

I figured out the problem on my end. Thought I did a quick reply a while ago but I dont see it here now.

On your physical adapter disable everything except Intel(R) Advanced Network Services Protocol. When I created the vlan connections / virtual adapters it appears the driver disabled the "client for windows networking" as well as IPv4 and IPv6 protocols but left everything else in tact. Disabling everything but the protocol that shares the physical adapter with the virtual adapters fixed things for me.

Immediately I noticed that the virtual adapters were trying to pull an ip address and in the VLANS tab of the physical adapter (via device manager) both were now showing enabled instead of the prior disabled.

Let me know if this helps you.

 

asphix20 - What you state about the "Intel(R) Advanced Network Services Protocol" is correct. However, this was already the case for me both before and after my reinstall.

I did just reinstall VirtualBox, and have no issues. Solved for now, I guess...

 

I have a somewhat similar situation - not exaxct. I actually have a HP elitebook 8530p, which has the same nic. I installed the latest drivers from Intel and got the vlans working. However, I'm running VMServer 2.01, on windows xp pro sp3.

In vmserver the guest OSs can't communicate on the guest nics bridged to host vlan nics using tagged vlans. They CAN communicate on nics bridged to the host nic on the untagged vlan.


Does anyone have any advice or suggestions (or konw if this SHOULD / DOES work elsewhere)? I don't know how VMWare does the bridging, but I suspect the use the nics in some type of promiscuous mode where vmware has full access to the nic, and I'm wondering if the vlan nics using taggs are having problems with that.


As a note, on my 'core' nic, the 'physical' nic, I disabled all services execpt the Intel Advanced Services Protocol.