10-19-2016 05:58 AM - edited 03-11-2019 12:10 AM
I have a user that has issues in the morning when she puts her laptop in the docking station and brings it out of sleep.
Here is the scenario -
Users company laptop at home on wifi -
Closes lid and laptop goes to sleep -
Comes to work in the morning and puts laptop in the replicator -
Replicator is hard wired to the network -
brings it out of sleep -
ISE puts it in the sandbox with limited network and no internet -
If she reboots while it is in the replicator it is fine -
If she takes it off of the replicator before a reboot and uses company wifi it connects fine -
If you plug the Ethernet directly into the laptop it works fine -
Any thoughts?
Latitude E5000
Win 7 64bit
Dell E-Port Plus II Replicator
10-20-2016 06:33 PM
Hi there! I have seen this issue once before where the port-replicator was causing the issue. I have a few questions for you:
1. Can you check your switch port and see if the port replicator has its own mac address that is different than the one on the laptop
2. Do you have 802.1x configured on the wired network as well
3. Do you have port-security enabled on the ports
4. What type of authentication are you doing? PEAP, MAR, etc?
5. Confirm if the following patches are installed on the affected machine:
http://robert.penz.name/555/list-of-ieee-802-1x-hotfixes-for-windows-7/
Thank you for rating helpful posts!
10-03-2017 08:31 PM
Hi,
Forgive me for resurrecting a year old post, hopefully we tie it up.
My organisation is in the process of enabling 802.1x on 2960-x's authenticating by ISE with AD integration and MAB fallback.
So far our laptops with the Dell Port Replicator have the exact same issues as OP.
E-Port Plus Advanced Port Replicator II for Select Dell Latitude Laptops
http://accessories.ap.dell.com/sna/productdetail.aspx?c=au&l=en&s=bsd&cs=aubsd1&sku=452-11522
1. MAC doesn't change, tested docking, redocking, using the NIC on the dell notebook and NIC on port replicator.
2. Wired 802.1x supplicant configured on the Dell Latitude notebook pc.
3. No port security (just multi-domain and MAB fallback
4. PEAP (computer authentication). the computer's AD credentials are authenticated.
5. Not Applicable. Using Windows 10 1607, Security and Feature patches current as of 4 Oct 2017
Looks to me like they are just not compatible with this setup but haven't found confirmation yet...
Any thoughts?
05-08-2019 04:26 PM
Hi rmletcrmletc,
Did you find any solution fo this issue? I'm thinkg I'm having the same problem.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide