Erratic drive mapping - Vlan assignment RRS feed

  • Question

  • Hello all,

    We are having issues with inconsistent drive mapping after vlan change. The client computers (running Windows 7) first authenticate against our NPS server (using mac authentication bypass), and are then placed in vlan 10. After the users log in, they are placed into a different vlan based on user's AD group membership. The actual vlan switch works fine, and the users always end up in the right vlan. The drives, however, aren't always there. The user's home drive is mapped via the Home Folder in the users' properties in AD, and the rest of the drives (staff data, etc.) are mapped via a log on script. Drives mapped via GP are almost always mapped, but drives mapped via AD properties are missing much more often. All of the drives can be manually accessed from all of the vlans. There are no errors on the NPS side, and the only errors I can see in the event viewer are DHCPNack messages (The IP address lease 10.42.13.xx for the Network Card with network address 0x has been denied by the DHCP server 10.42.10.xx). Does anyone have any advice or a possible solution? Any info would be much appreciated.

    Here's how authentication is set up locally:

    Cache user information for subsequent connections to this network Enabled
    Authentication Mode
    User authentication
    Maximum Authentication Failures 2

    Maximum EAPOL-Start Messages Sent Not setup

    Held Period (seconds) Not setup

    Start Period (seconds) Not setup

    Authentication Period (seconds) Not setup

    Single Sign On
    Before user logon

    Maximum acceptable delay for network connectivity 10
    This network uses different VLAN for authentication with machine and user credentials
      is enabled

    Allow additional dialogs during single sign on is disabled

    Fast Reconnect is disabled

    Authentication method is PEAP-MSCHAP V2

    Thank you,


    Tuesday, March 25, 2014 10:48 PM

All replies

  • Hello,

    Thank you for your question.

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

    Thank you for your understanding and support.

    Friday, March 28, 2014 9:43 AM
  • Hi,

    When an interface changes VLANs, line protocol goes down for a moment then comes back up again. It is similar to physically disconnecting the interface for a very short time. Your problem might be caused by the interface being down for this short period of time, because this is when the home drives are being mapped, but I'm not sure.

    If the GP mappings are almost always working, why not do everything there and dispense with the home drive mapping?

    You can also try setting Computer Configuration -> Administrative Templates -> System ->  Logon -> Always wait for the network at computer startup and logon to Enabled and see if this helps.


    Monday, March 31, 2014 11:39 PM
  • "Always wait for the network..." is enabled, and using GP exclusively to map drives is what we'll most likely have to do

    Tuesday, April 1, 2014 1:40 AM