bondbill2k2 Posted April 19, 2012 Posted April 19, 2012 Having joined around 100 laptops to our domain about 10 are having problems finding the DHCP server. When assigned a static IP they work fine and wired in they also work great but soon as you attempt to auto assign on the wireless the laptop connects to the wireless then has the limited/no network connectivity warning. I have ran ipconfig /release wireless then renewed plus netsh winsock reset before leaving the laptop off for several minutes and rebooted but still no joy I have set up most the laptops with reserved IPs for now so they can be used but ideally I would like to solve this issue, having read similar problems the above and reinstalling NIC drivers have worked but this also didn't help.
SYNACK Posted April 19, 2012 Posted April 19, 2012 More information may be needed; wireless system, encryption, network structure (vlan'ed?), DHCP server config...
bondbill2k2 Posted April 19, 2012 Author Posted April 19, 2012 More information may be needed; wireless system, encryption, network structure (vlan'ed?), DHCP server config... Wireless is Cisco Aironet 1142 APs managed by Cisco 5500 WM. SSID visible with WPA2-PSK. Network is 2 vlans for admin and curric, DHCP server in curric vlan and clients set to obtain IP automatically.
2097 Posted April 19, 2012 Posted April 19, 2012 Wireless is Cisco Aironet 1142 APs managed by Cisco 5500 WM. SSID visible with WPA2-PSK. Network is 2 vlans for admin and curric, DHCP server in curric vlan and clients set to obtain IP automatically. try setting up the DHCP on the cisco controller , see if this works first . Then disable and look for something on the controller thats blocking the port
Davit2005 Posted April 19, 2012 Posted April 19, 2012 Are all the make/model of the laptops the same. Could some have slightly different wireless chips.
bondbill2k2 Posted April 19, 2012 Author Posted April 19, 2012 Can't believe I didnt check it first, DHCP was moved over by LEA but wireless interface on manager hadn't been configured to the new server. Strange how some devices picked up the new IP tho! *facepalm*
kellssmith Posted April 19, 2012 Posted April 19, 2012 kindly restart the service of DHCP by typing service.msc command
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now