- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As the PROset adapter configuration does not allow you to create VLANs, I've tried with with the following powershell commands as administrator:
PS C:\Users\username> Get-IntelNetAdapter
Location Name ConnectionName LinkStatus
-------- ---- -------------- ----------
0:25:0:0 Intel(R) Ethernet Connection I217-LM Ethernet 1,00 Gbps ...
PS C:\Users\username> Add-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection I217-LM" -VLANID 0,196
Add-IntelNetVLAN : Failed to add one or more of the specified VLAN IDs.
At line:1 char:1
+ Add-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection I217-LM" - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (IANet_PhysicalE...e = "username-HP2"):CimInstance) [Add-IntelNetVLAN], Ex
ception
+ FullyQualifiedErrorId : Error executing cmdlet.,Intel.PowerShell.Network.VLAN.AddIntelNetVlan
This disables the adapter, but does not create a VLAN interface. What am I doing wrong. Even tried this in safe mode, with no success as well.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see your Powershell prompt says "C:\Users\username>". This is generally the case when you run Powershell as a normal user and not as the Administrator. Have you tried running the commands in Admin Mode in Powershell? I'm curious if your commads will hang up like mine did this morning.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yup, here is the full window with administrator clearly in the screenshot :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same issue, been fighting with it all day. Intel Ethernet I219-LM, Windows 1809. When I try to create a VLAN adapter, it disables the adapter and then fails.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For what it's worth, I was in a position that I could rebuild my machine. Reinstalled 1809 from scratch, installed the 23.5 drivers, and I was able to add VLANs with the PowerShell cmdlets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this I217-LM integrated into a board, and what is the make and model of the board?
- Yes, it's in a HP Zbook 15 G2 notebook
Did you remove any VLANs and Teams, and uninstall the existing ANS software prior to updating to 23.5?
- Yes
See the attached log.
Thanks Daniel!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
intel i219-lm, win 10 17763.195.
Same problem here. Not possible to work with VLANs at all. Have no VLANs tab.
Tried various drivers versions and win10 driver signature bypass boot. Have no success.
Need solution asap. =(
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did:
PS C:\WINDOWS\system32> Add-IntelNetVLAN
cmdlet Add-IntelNetVLAN at command pipeline position 1
Supply values for the following parameters:
ParentName[0]: Intel(R) Ethernet Connection I217-LM
ParentName[1]:
VLANID[0]: 0
VLANID[1]: 196
VLANID[2]:
Add-IntelNetVLAN : Failed to add one or more of the specified VLAN IDs.
At line:1 char:1
+ Add-IntelNetVLAN
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (IANet_PhysicalE...e = "user-HP2"):CimInstance) [Add-IntelNetVLAN], Ex
ception
+ FullyQualifiedErrorId : Error executing cmdlet.,Intel.PowerShell.Network.VLAN.AddIntelNetVlan
PS C:\WINDOWS\system32>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Reinstalled the 23.5 software (and removed the folder), then imported the CMDLets and tried again.
Still same behavior. The `Get-IntelNetAdapter` responds directly, but the `Add-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection I217-LM" -VLANID 0,196` indeed hangs for a couple of minutes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear danield
I have the same problem after updating my windows to 1809 and I use the Intel software and drivers23.5 but i have this error:
PS C:\WINDOWS\system32> Import-Module -Name "C:\Program Files\Intel\Wired Networking\IntelNetCmdlets\IntelNetCmdlets.dll"
PS C:\WINDOWS\system32> Get-IntelNetAdapter
Location Name ConnectionName LinkStatus
-------- ---- -------------- ----------
0:31:6:0 Intel(R) Ethernet Connection (2) I219-LM Ethernet 1.00 Gbps ...
4:0:0:0 Realtek PCIe GbE Family Controller 1.00 Gbps ...
PS C:\WINDOWS\system32> Add-IntelNetVLAN
cmdlet Add-IntelNetVLAN at command pipeline position 1
Supply values for the following parameters:
ParentName[0]: Intel(R) Ethernet Connection (2) I219-LM
ParentName[1]:
VLANID[0]: 0
VLANID[1]: 2003
VLANID[2]:
Add-IntelNetVLAN : Failed to add one or more of the specified VLAN IDs.
At line:1 char:1
+ Add-IntelNetVLAN
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (IANet_PhysicalE...e = "ADMIN-PC"):CimInstance) [Add-IntelNetVLAN], Exception
+ FullyQualifiedErrorId : Error executing cmdlet.,Intel.PowerShell.Network.VLAN.AddIntelNetVlan
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same behavior as before, after the delay you get the same error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Daniel,
I am not the OP but I have the same exact error and inability to add VLANs after upgrading to Windows 10 1809 and updating to 23.5. This is clearly a problem for multiple people and not an issue isolated to a single user. I cannot accept having to do a fresh install of Windows 10 as a solution. The driver/software needs to be fixed or at the very least, a viable workaround that does not involve a clean install of Windows needs to be provided.
Please push for a solution with expediency.
As for trying 23.4, can you confirm if 23.4 is compatible with 1809? The page for 23.4 does not have any mention of 1809 compatibility, whereas 23.5 explicitly states it is compatible. As you may know, Windows 10 1809 introduced some changes to the driver model and new drivers are required. I am willing to try 23.4 if you can confirm that it is compatible with 1809.
Thank you
-Darren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi DDupr,
Can you provide what is the exact model of your network adapter? Is it an onboard NIC or standalone network adapter. Thank you.
Best Regards,
Whybe T
Intel Customer Support Technician
Under Contract to Intel Corporation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please see the PowerShell output below. Note that this is an integrated/onboard NIC on a Gigabyte X299 UD4 motherboard.
Happy to give any other information needed and try anything other than a fresh install of Windows 10.
PS C:\WINDOWS\system32> Import-Module -Name "C:\Program Files\Intel\Wired Networking\IntelNetCmdlets\IntelNetCmdlets.dll"
PS C:\WINDOWS\system32> Get-IntelNetAdapter
Caption : Intel(R) Ethernet Connection (2) I219-V
Description : Intel(R) Ethernet Connection (2) I219-V
InstallDate :
Name : Intel(R) Ethernet Connection (2) I219-V
Status : OK
AdditionalAvailability : {3}
Availability : 3
CreationClassName : IANet_PhysicalEthernetAdapter
DeviceID : {C0F315E7-31B1-4A7C-82F4-38849814422A}
ErrorCleared :
ErrorDescription :
IdentifyingDescriptions :
LastErrorCode :
MaxQuiesceTime :
OtherIdentifyingInfo :
PowerManagementCapabilities :
PowerManagementSupported :
PowerOnHours :
StatusInfo : 3
SystemCreationClassName : Win32_ComputerSystem
SystemName : BORG
TotalPowerOnHours :
AutoSense :
FullDuplex : True
MaxSpeed : 1000000000
NetworkAddresses : {1C1B0D, 1C1B0DEC96CA}
OctetsReceived :
OctetsTransmitted :
PermanentAddress : 1C1B0DEC96CA
Speed : 1000000000
AlignmentErrors :
Capabilities : {32, 33, 34, 43...}
CapabilityDescriptions : {, , , ...}
CarrierSenseErrors :
DeferredTransmissions :
EnabledCapabilities :
ExcessiveCollisions :
FCSErrors :
FrameTooLongs :
InternalMACReceiveErrors :
InternalMACTransmitErrors :
LateCollisions :
MaxDataSize :
MultipleCollisionFrames :
SingleCollisionFrames :
SQETestErrors :
SymbolErrors :
TotalPacketsReceived :
TotalPacketsTransmitted :
MiniPortInstance : {C0F315E7-31B1-4A7C-82F4-38849814422A}
MiniPortName : e1dexpress
AdapterStatus : 51
BusType : 7
BusTypeString : PCI Express
ConnectionName : Ethernet
ControllerID :
DeviceStatus : 1
DeviceStatusString : Link Up
DriverVersion : 12.18.8.4
EEE : 3
EEEString : Not Negotiated
ETrackID : 0x00000000
ExtendedStatus : 0
HardwareStatus : 1
Location : 0:31:6:0
MediaType : 1
MediaTypeString : Copper
NegotiatedLinkSpeed : 0
NegotiatedLinkSpeedString : Not Supported
NegotiatedLinkWidth : 0
NegotiatedLinkWidthString : Not Supported
NVMVersion : 0x00000000
OriginalDisplayName : Intel(R) Ethernet Connection (2) I219-V
OtherCapabilityDescriptions :
OtherEnabledCapabilities :
OtherEnabledCapabilityIDs :
OtherMediaType :
OtherPhyDevice :
OTPVersion :
PartitionNumber : 65535
PartitionNumberString :
PartNumber :
PCIDeviceID : VEN_8086&DEV_15b8&SUBSYS_1458e000&REV_00&0&fe
PHYDevice : 0
PortNumber : -1
PortNumberString : Not Supported
SanMacAddress :
SlotID : 0:31:6:0
SpeedString : 1.00 Gbps Full Duplex
Temperature : 0
TemperatureString : Not Supported
PSComputerName :
PS C:\WINDOWS\system32> Add-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection (2) I219-V" -VLANID 0,3
Add-IntelNetVLAN : Failed to add one or more of the specified VLAN IDs.
At line:1 char:1
+ Add-IntelNetVLAN -ParentName "Intel(R) Ethernet Connection (2) I219-V ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (IANet_PhysicalE...mName = "BORG"):CimInstance) [Add-IntelNetVLAN], Exception
+ FullyQualifiedErrorId : Error executing cmdlet.,Intel.PowerShell.Network.VLAN.AddIntelNetVlan
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page