> Hello Mike,
>
> VS2005R2 does not support VLAN tagging.
> It will be in Windows Server Virtualization available.
>
> --
> Mit freundlichen Gr=FC=DFen / Kind regards - Alexander Ortha (Microsoft)
>
> This posting is provided "AS IS" with no warranties, and confers no right=
>
> "Mike" <(email address - cut out)> wrote in messagenews:1161031449.063229.26120@=
>
>
>
> > I'd like to find out if anyone else is doing what I'm doing because so
> > far on all of the servers I am doing this with I am getting bluescreens
> > and failures.
>
> > A Dell PE2950 is configured with an Intel PRO 1000 PT dual-port server
> > adapter. It is configured with 5 VLAN's on the NIC, which I assume is a
> > common practice so that the server can participate in numerous VLAN's.
> > The latest Intel drivers are installed (v11.1).
>
> > The problem occurs right after installing VS 2005 R2. When attempting
> > to RDP into the server or performing any network activity on the server
> > causes a bluescreen. A dump file analysis determined that the file
> > VMNETSRV.SYS was the cause of the bluescreen.
>
> > To further troubleshoot the problem I removed the Intel card completely
> > from the server and used the integrated Broadcom NIC. I enabled VLAN's
> > on the NIC and installed VS 2005 R2. Now, the problem is so bad that no
> > communication occurs on any of the tagged VLAN's with the exception of
> > the single tagged VLAN.
>
> > It appears that there is an inherent problem with the way VS 2005 R2
> > handles communication with network cards configured in a VLAN scenario.
>
> > Can anyone else confirm this and/or know of a workaround or a pending
> > fix from Microsoft?
>=20
> > Thanks.- Hide quoted text -- Show quoted text -

> I'd like to find out if anyone else is doing what I'm doing because so
> far on all of the servers I am doing this with I am getting bluescreens
> and failures.
>
> A Dell PE2950 is configured with an Intel PRO 1000 PT dual-port server
> adapter. It is configured with 5 VLAN's on the NIC, which I assume is a
> common practice so that the server can participate in numerous VLAN's.
> The latest Intel drivers are installed (v11.1).
>
> The problem occurs right after installing VS 2005 R2. When attempting
> to RDP into the server or performing any network activity on the server
> causes a bluescreen. A dump file analysis determined that the file
> VMNETSRV.SYS was the cause of the bluescreen.
>
> To further troubleshoot the problem I removed the Intel card completely
> from the server and used the integrated Broadcom NIC. I enabled VLAN's
> on the NIC and installed VS 2005 R2. Now, the problem is so bad that no
> communication occurs on any of the tagged VLAN's with the exception of
> the single tagged VLAN.
>
> It appears that there is an inherent problem with the way VS 2005 R2
> handles communication with network cards configured in a VLAN scenario.
>
> Can anyone else confirm this and/or know of a workaround or a pending
> fix from Microsoft?
>
> Thanks.
>

> It's hypervisor based virtualization that's supposed to come out with
> Longhorn Server.
>
> --
> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>
>
>
>
>
>
> "Mike" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>
> Alexander, thanks for the response.
>
> What is "Windows Server Virtualization" and when will it be available?
>
>
> On Oct 17, 1:22 am, "Alexander Ortha [MS]"
> <(email address - cut out)> wrote:
> > Hello Mike,
> >
> > VS2005R2 does not support VLAN tagging.
> > It will be in Windows Server Virtualization available.
> >
> > --
> > Mit freundlichen Gr=FC=DFen / Kind regards - Alexander Ortha (Microsoft)
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> > "Mike" <(email address - cut out)> wrote in
> > messagenews:(email address - cut out)...
> >
> >
> >
> > > I'd like to find out if anyone else is doing what I'm doing because so
> > > far on all of the servers I am doing this with I am getting bluescree=
> > > and failures.
> >
> > > A Dell PE2950 is configured with an Intel PRO 1000 PT dual-port server
> > > adapter. It is configured with 5 VLAN's on the NIC, which I assume is=
> > > common practice so that the server can participate in numerous VLAN's.
> > > The latest Intel drivers are installed (v11.1).
> >
> > > The problem occurs right after installing VS 2005 R2. When attempting
> > > to RDP into the server or performing any network activity on the serv=
> > > causes a bluescreen. A dump file analysis determined that the file
> > > VMNETSRV.SYS was the cause of the bluescreen.
> >
> > > To further troubleshoot the problem I removed the Intel card complete=
> > > from the server and used the integrated Broadcom NIC. I enabled VLAN's
> > > on the NIC and installed VS 2005 R2. Now, the problem is so bad that =
> > > communication occurs on any of the tagged VLAN's with the exception of
> > > the single tagged VLAN.
> >
> > > It appears that there is an inherent problem with the way VS 2005 R2
> > > handles communication with network cards configured in a VLAN scenari=
> >
> > > Can anyone else confirm this and/or know of a workaround or a pending
> > > fix from Microsoft?
> >
> > > Thanks.- Hide quoted text -- Show quoted text -

> Hello Mike,
>
> VS2005R2 does not support VLAN tagging.
> It will be in Windows Server Virtualization available.
>
> --
> Mit freundlichen Grüßen / Kind regards - Alexander Ortha (Microsoft)
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Mike" <(email address - cut out)> wrote in
> messagenews:(email address - cut out)...
>
>
>
> > I'd like to find out if anyone else is doing what I'm doing because so
> > far on all of the servers I am doing this with I am getting bluescreens
> > and failures.
>
> > A Dell PE2950 is configured with an Intel PRO 1000 PT dual-port server
> > adapter. It is configured with 5 VLAN's on the NIC, which I assume is a
> > common practice so that the server can participate in numerous VLAN's.
> > The latest Intel drivers are installed (v11.1).
>
> > The problem occurs right after installing VS 2005 R2. When attempting
> > to RDP into the server or performing any network activity on the server
> > causes a bluescreen. A dump file analysis determined that the file
> > VMNETSRV.SYS was the cause of the bluescreen.
>
> > To further troubleshoot the problem I removed the Intel card completely
> > from the server and used the integrated Broadcom NIC. I enabled VLAN's
> > on the NIC and installed VS 2005 R2. Now, the problem is so bad that no
> > communication occurs on any of the tagged VLAN's with the exception of
> > the single tagged VLAN.
>
> > It appears that there is an inherent problem with the way VS 2005 R2
> > handles communication with network cards configured in a VLAN scenario.
>
> > Can anyone else confirm this and/or know of a workaround or a pending
> > fix from Microsoft?
>
> > Thanks.- Hide quoted text -- Show quoted text -

> Alexander, thanks for the response.
>
> What is "Windows Server Virtualization" and when will it be available?

> I'd like to find out if anyone else is doing what I'm doing because so
> far on all of the servers I am doing this with I am getting bluescreens
> and failures.
>
> A Dell PE2950 is configured with an Intel PRO 1000 PT dual-port server
> adapter. It is configured with 5 VLAN's on the NIC, which I assume is a
> common practice so that the server can participate in numerous VLAN's.
> The latest Intel drivers are installed (v11.1).
>
> The problem occurs right after installing VS 2005 R2. When attempting
> to RDP into the server or performing any network activity on the server
> causes a bluescreen. A dump file analysis determined that the file
> VMNETSRV.SYS was the cause of the bluescreen.
>
> To further troubleshoot the problem I removed the Intel card completely
> from the server and used the integrated Broadcom NIC. I enabled VLAN's
> on the NIC and installed VS 2005 R2. Now, the problem is so bad that no
> communication occurs on any of the tagged VLAN's with the exception of
> the single tagged VLAN.
>
> It appears that there is an inherent problem with the way VS 2005 R2
> handles communication with network cards configured in a VLAN scenario.
>
> Can anyone else confirm this and/or know of a workaround or a pending
> fix from Microsoft?
>
> Thanks.