T40 Wireless Issue - No IP Address Assigned

I am using a T40 in wireless mode and am unable to get automatic assignment of the IP address. Connection to the wireless access point is confirmed but there is no internet connectivity because the IP address assignment is not being completed. The wireless network is working because I have a second laptop which attaches with no issues. This laptop was working but my son was visiting over the holidays and he could not get his laptop to linkup. To make a long story short some wireless setup adjustments were made to my unit to try to determine the problem with his. I don't know what they were. Now neither laptop works. I am confident this is a setup issue but I can't seem to find the setup adjustment that needs to be made. Does anyone have some ideas where I can start?

Hi Dsnyder5516,
Welcome to the forum!
I suggest using System Restore in Windows to the point where your wireless was working fine.
I hope it helps.
Maliha (I don't work for lenovo)
ThinkPads:- T400[Win 7], T60[Win 7], IBM 240[Win XP]
IdeaPad: U350
Apple:- Macbook Air [Snow Leopard]
Did someone help you today? Compliment them with a Kudos!
Was your question answered today? Mark it as an Accepted Solution!
Lenovo Deutsche Community Lenovo Comunidad en Español
Visit my YouTube Channel

Similar Messages

HP d5560 Wireless Issue - No IP Address (Mac OS 10.9)

Hi there,
I recently moved house. In my previous house I had my printer set-up and working wirelessly.
I've moved and now have a new Wireless hub and I can not get my printer to connect with my Virgin Media Super Hub.
I have tried doing the one-touch wirelessly connection.
I have printed several times the Wireless Network Test Report and each time it can see my wireless hub in the list of SSID networks and it reports:
Wireless No - PASS
Wireless Working - PASS
Network Name (SSID) Found) FAIL
Network Name (SSID) ... <I think this is referring to our old wfi name>
IP Addresss - Not applicable
Authentication Type - WPA-PSK
Encryption - Automatic (AES or TKIP)
My Wi-Fi Super Hub has WPA Auto security mode.
Can anyone please assist with advice on how to rectify this problem?
Do I have to un-install and re-install my HP printer software?
Do I have to re-set the printer to factory settings?
Previously in my old flat when I set up the printer, it took forever and I even had to have it replaced with another one to get it set up again. I hope I don't have to go through the same again.
Thanks in advance for any assistance.

Hi there,
Thanks for the advice. I have tried the instructions but unfortunately because I am on Mac OS 10.9 there are no drivers and therefore no "Printer Setup & Software" settings in the current HP Utility HP basic software. All other settings are governed by Mac's System Preferences and Printer and Scanner.
Do I have to reset the printer to factory settings? If so, how do I do that?
I can not access an IP address for the printer and so can not access it that way either.
Any other thoughts?
Thanks.

Issue with the IP address assigned on my HP Photosmart Software

I am having an issue wtih the ip address assigned to the hp all in one printer loaded throgh my software not matching the ip address on my wireless network.
I can't seem to manually update this configuration.
Any ideas, other than uninstall and re-installing the device?

Couple of questions for you: what printer? what operating system?
Here is a document that may help with the connection, though it is not printer specific:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02790693&cc=us&dlc=en&lc=en#N56
007OHMSS
I was a support engineer for HP.
If the advice resolved the situation, please mark it as a solution. Thank you.

C4780 Wireless Issues with Windows 7

Hello,
I've been having some problems keeping my HP C4780 connected to my HPDV8t laptop (running Windows 7). I installed the printer correctly for wireless and currently have three computers wirelessly connected to it (my HP laptop, a Macbook Pro, and an iMac). I've never had any issues printing wirelessly with wither of the Macs.
On the HP, I was printing fine for the first 3-4 days. I see the printer available in all applications, however, it doesn't appear under the device manager (printer and faxes). The only thing that appears is the "My PC" Icon, which prompts me to troubleshoot with the yellow exclamation mark.
When I troubleshoot, it tells me that it cannot find the driver to the printer, and goes into an endless troubleshooting loop trying to "fix" the printer (it won't find it even if I have the original HP installation CD in the drive). When I press cancel, I can no longer print to the printer from any application. I've tried uninstalling and reinstalling the software twice. Each time, the printer works for a few days, then prompts troubleshooting and then loses the printer. (again, I know the printer is established on the network since the Macs can still find it)
Please advise. Thanks much in advance.

My guess is that the printer is changing it's iP address and the SW on your computers are having a difficult time keeping track of the change.
It's not unusual (or wrong) for the printer to be given different IP addresses from your wireless-router. Since the wireless-rotuer "leases" IP addresses to devices on the network, if the lease expires when the printer is off, the wireless-router may assign the printer's old IP address to another device.
For your issue, lets try to fix the IP address assigned to your printer. There are two methods to try. The first print our the C4780 Network Configuration Page and note the printer's IP address.
1) If your wireless-router supports it, make a DHCP reservation for your printer. Depending on your wireless-router (btw -- what kind do you have), this may be easy to do and is the recommended option here.
2) Alternatively, you can make the existing IP address assigned to your printer "static". On the C4780, the easiest way to do this is to open the printer's internal web page by browsing to the C4780's IP address. From the web page, select Networking then Wireless (802.11) then IPv4 Configuration.
Select Manual IP and enter the printer's current IP address in the field plus an offset of plus or minus 20. For example, if the current printer IP address is 192.168.x.100 or lower, then use 192.168.x.120. If the printer's IP address is 192.168.x.200 or higher, then use 192.168.x.180.
For the subnet mask, enter 255.255.255.0. Leave the default gateway IP address empty.
Select Manual DNS Server and leave those entries empty as well.
Now reinstall the SW (hopefully for the last time).
Regards / Jim B / Wireless Enthusiasts
( While I'm an embedded wireless systems engineer at work, on this forum I do not represent my former employer, Hewlett-Packard, or my current employer, Microsoft )
+ Click the White Kudos star on the left as a way to say "thank you" for helpful posts.

AP not getting ip address assigned.

Hi all,
I have a problem with my AIR-AP1041N-E-K9, i do not seem to get an ip-address assigned after a reset to factory defaults.
I do see the AP with CDP:
Device-ID: ap
Advertisement version: 2
Platform: cisco AIR-AP1041N-E-K9
Capabilities: TransBridge IGMP
Interface: gi5, Port ID (outgoing port): GigabitEthernet0
Holdtime: 163
Version: Cisco IOS Software, C1040 Software (C1140-K9W7-M), Version 12.4(25d)JA1, RELEASE SOFTWARE (fc1)
Technical Support:
http://www.cisco.com/techsupport
Copyright
Duplex: full
Power drawn: 15000 milliwatts
SysObjectID: 0.0
Addresses:
unknown addres
So that should mean that layer 2 connectivity is fine.
I have the AP connected to a cisco SG300 switch,and assigned switchport trunk allowed vlan's: 1,3,4,8.
Can someone help me?
Regards,
Menno
Message was edited by: Menno Hogenbirk
I also noticed that when i connect to the AP via console-cable, i can see the AP boot up in the console session, but then i do not get a login prompt, but it seems like the AP is responding; if i shutdown the interconnecting link between the switch and the AP, i do see log messages appearing in the console-connection.
I have tried to debug on the Switch, but i need a password, so i can debug, which i do not have.,

Hi, thanks for your reply,
I'm should be getting my ip via DHCP(as i believed that this is the way that the AP searches for an ip, when it has no config yet). The DHCP-server is configured on a cisco 871 router that is connected to the switch, as i found no option to configure it on my switch, which is in layer 3 mode. The DHCP-pool is assigned to the vlan(native) 1 address-range(in this case 192.168.0.x/24). I also have configured a range for my workstations, and here i do get Ip-addresses assigned.
The AP does not connect to a Wireless controller. Also i have checked my inter-vlan routing on my switch, and i have connectivity to all vlans, so i believe my AP should have connectivity to the DHCP-server configured on the router.
Ping-test from switch shows no issues:
Swouter#ping 192.168.0.1
Pinging 192.168.0.1 with 18 bytes of data:
18 bytes from 192.168.0.1: icmp_seq=1. time=0 ms
18 bytes from 192.168.0.1: icmp_seq=2. time=0 ms
18 bytes from 192.168.0.1: icmp_seq=3. time=0 ms
18 bytes from 192.168.0.1: icmp_seq=4. time=0 ms
----192.168.0.1 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
Message was edited by: Menno Hogenbirk
Problem has been resolved.

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.
Bought my girlfriend the newest Macbook Pro 13" and began experiencing problems with my wifi the moment we got home. Her Macbook would not connect to our home Wi-Fi while my old Macbook Late 2008 running Snow Leopard connected without a problem. Airport would say that it had a Self-Assigned IP address (168.x.x.x). Did not realize it was a Lion problem until after using her Macbook Pro and becoming jealous of the new OSX, I upgraded. Soon after I was unable to go online. Luckily I had my iPad 2 and I began to scoure the net for help. Ran into allot of suggestions but it was not until I tried the following all together was I able to share the good new, from my Macbook. Hope this works:
First go to Preferences > Network and click on the cog next to the + and - on the sidebar and click Set Service Order
     - Move Wi-Fi to the top and click ok.
     - Set location to Automatic
     - Click Apply
     - Click Advanced
     - Click the "-" on the selected Wi-Fi router you wish to connect to
     - Click Apply
     - Click Lock to Prevent Further Changes
Go to your Mac's harddrive, (Macintosh)
     - Go to Library > Preferences > SystemConfiguration >
     - Delete "com.apple.airport.preferences.plist" file
Turn off your computer
     - push and hold Option+Command+R+P
     - turn on computer
     - when the grey screen turns on you will hear the OS X "ON" sound (for lack of a proper term) and it will momentarily restart.
     - you will once again hear the "ON" sound, let go of all keys.
     - this resets your PRAM
Go to Preferences > Network > Advanced > + sign
     - click Choose a Network
     - Select your network and enter password
Viola!!! I tried this on my Macbook Late 2008 and my girlfriends new Macbook Pro 2010

     No you are clearly mistaken. The Self-Assigned IP address problem exists on many Macbook Pro models, including the current model, which I mentioned as being the original computer with the problem. While my 2008 Macbook is older it was working perfectly on Snow Leopard and didn't suffer issues until switching to Lion. So clearly the problem exists on the operating system and not so much the hardware.
     I called Apple Support and they had no fix for the problem and told me that this would hopefully be addressed in a subsequent update. It wasn't until I came accross the answer after trying many different methods that I got both of the Macbooks to connect to my router. Otherwise I wouldn't or could not have been surfing the internet for the last 4 months.
Cheers.

10.5.3 Update Wireless Issues (WiFi, Wireless)

Hi there,
I see several posts regarding networking issues with the +Mac OS 10.5.3 Update+, but have not seen one describing my exact issue.
After updating my 15" MacBook Pro (2.33GHz) with the +Mac OS 10.5.3 Update+ via +Software Update+, I had no problem connecting to and using my home and office networks (AirPort Express and AirPort Extreme, respectively).
At a third location however, I connect to a Netgear MR814v2 802.11g router which shares a Comcast Cable Modem. Wired into the router are two computers, an X-Box (or some sort of gaming console) and a Vonage VoIP box. Wirelessly connected are generally 1 - 4 Macs. Two are running Mac OS 10.4.11 and two are running Mac OS 10.5.2.
After performing the +Mac OS 10.5.3 Update+, all devices on the network loose their connection to the internet whenever my machine attempts to connect to the router. On my machine, I'll see that I'm connected to the router but I'll have a self assigned IP address.
Resetting only the router does not solve the problem.
Resetting the Comcast Cable Modem solves the problem of the other devices on the network loosing their internet connection (at least until I attempt another connection), but still does not allow me to successfully connect.
Deleting AirPort as a type of network connection and re-adding it in the Network pane of the +System Preferences+did not solve the problem
Thanks!
Message was edited by: Allen Evans

This:
After performing the Mac OS 10.5.3 Update, all devices on the network loose their connection to the internet whenever my machine attempts to connect to the router. On my machine, I'll see that I'm connected to the router but I'll have a self assigned IP address.
is what makes me think the issue is in your Netgear or Comcast router, not with Mac OS X 10.5.3.
But more to the point, Comcast's routers generally will only issue four IP addresses via DHCP, and if you want to connect more devices than that you need to have your home router setup to create a NAT network locally. That's where your router receives an IP address from your Comcast router, but then the Netgear creates its own network via ethernet and wireless and all packets are translated to and from the Internet through it.
I presume you've also tried the various suggestions at the Netgear MR814v2 troubleshooting page?
Also, you state you have a "MR814v2 802.11g" router, but the MR814v2 is 802.11b only

How to manage IP address assignment for laptops?

Dear All,
I'm looking for an efficient way to manage IP address assignment for laptops.
I have a DHCP server with reservation for all my devices.
Laptops usually have 2 NICs: LAN and WiFi card.
So, how can I manage the IP assignment for these devices?
If I make a DHCP reservetion with two different IP addresses, I can have problems with DNS round-robin.
Should I enable the DNS secure dynamic update for domain members and then reserve two different IP addresses on DHCP?
I don't want that user needs to manually change their NIC configuration.
What you suggest?
Thanks

The best way to manage it would be to "not" manage it. DHCP by definition is supposed to be "dynamic". DHCP Reservations are great for a few devices that live under "special circumstances" but you never want to set Reservations for everything,...if
you do that then just don't have DHCP to start with and statically assign everything.
The combination of DHCP with dynamically updated DNS in AD means you never have to know or ever care what the IP# is. Everything is referred to by it's hostname.
Some things to keep in mind:
Every interfaces has a different MAC,...meaning the Laptops have two MACs. Therefore it is impossible to reserve the same IP# for both. So they end up with a different IP# depending on which Nic they use. Running two laptop nics on the same LAN at
the same time is always bad. Either always use the wireless,...or always turn off the wireless nic when laptops are local within your facility and can use the physical nic. In other words pick one,...or the other,...never allow both to work
at the same time. This is a responsibility and education issue of the user,...you can't do this for them.
User can not change their own network IP Specs unless they are Local Administrators on their machines,...and they should never be allowed to be Local Administrators.

If you have a Blue Screen / Error due to Wireless issues (B110a), fix in here.

For the original thread created by somebody else, please see here:
http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-and/B110a-network-connection-problem/m-p/319...
Here's a youtube video of what happened to me: http://www.youtube.com/watch?v=adE1kq36ld4
I'm reposting it here so it can hopefully help some of you guys if anybody else stumbles across this. In short, my printer was fresh out of the box and I attempted to connect it to the wireless network. It would throw a blue screen on the LCD with an error of B8126AD6.
I narrowed it down to an issue with DHCP. For some reason the printer connects to the wireless access point but as soon as it tries to get an IP address from the DHCP server it crashes with that blue screen and the error code in the first post above. This look like a massive bug in the printers firmware! For reference my router is a Billion 7401VGPR3 which is acting as my default gateway and DHCP server. I have a Linksys WRT54G as my Access Point for the house.
To solve it, I turned DHCP off on my router and then tried connecting the printer to the wireless network. This time it connects fine but you still can't talk to it because it doesn't have a proper IP address. If it still doesn't connect properly, try turning WPA/WPA2/WEP off on your Access Point. Leave it completely open for a moment until you can reach the web interface (as below).
To fix the IP issue, I then went into the Settings menu on the printer and printed the "HP Network Configuration Page". Note that under the Wireless menu option there are a couple of different "Print Network Test Page" options. I believe it's the 2nd one that I selected. You'll know you have the right one when it prints out the page with the following info:
IPv4 IP Address
Subnet Mask
Hostname
Default Gateway
Primary DNS
etc, etc.
Take note of the IP Address from the printout above and the Subnet Mask. My IP was 169.254.73.5 and subnet mask 255.255.0.0. Now I manually configured my computers IP address to be similar (within the same subnet): 169.254.73.10 with the same subnet mask.
Now you can load up the web interface of the printer using http://169.254.73.5 in my case. (You should also be able to ping the printer at this point too). In here you have a Network tab where you can now manually set the IP Address of the printer. Set the address you want it to be in your network (in my case 192.168.0.3 with a subnet mask of 255.255.255.0 and default gateway 192.168.0.1 and dns server 192.168.0.1).
Once I clicked OK I changed my PC's IP back to normal, and I can now reach the printer on its IP address set above. YAY!
The great thing is, in the web interface you get a million more options to play with. You can manually set the IP address, gateway, DNS, wireless settings such as WPA1/WPA2 AES/TKIP Encryption, WPA Passkey, etc. So if you had to set the Access Point to completely Open, setup the encryption again and put the passkey in here. When I did this I had to go back into the Settings menu on the printer LCD and select "Disable Wireless" then "Enable Wireless" to force it to re-join the network.
Finally I went into the Settings menu again and Updated the software on the printer. I don't know if the new software fixes the bug or not - I haven't tested it (can't be bothered!).
Hopefully this will help some of you guys out there too!
EDIT: I've just stumbled across another couple of posts with similar results to mine:
- http://h30434.www3.hp.com/t5/Printer-networking-and-wireless/How-to-install-Photosmart-B109n-z-on-a-...
- http://forums.techguy.org/networking/627989-hp-6980-printer-wireless-problem.html

Many thanks to gardz for an exhaustive overview on this critical problem with the B110a printer!
I am happy to report that I have managed to set the printer to a static IP and am now able to connect to it wirelessly from my home computers, and also able to use the web apps and ePrint features on the printer. The printer shows the IP address and I am able to use the EWS (Embedded Web Server) to connect to its IP address from my PC's internet browser. The Wireless Network Test Report also showed no problems. I have also completed the Product Update on the printer, and there are no more pending updates now.
However, the core wireless problem is still not satisfactorily resolved.
I get the BSOD and blinking-lights error ("Please turn off printer and then on"), only if I start the printer when Wireless is enabled on the printer. If wireless is disabled prior to printer boot, there is no error.
The workaround I have adopted for now, is to always switch off the printer's wireless, before switching off the printer, and enabling the wireless setting only when I need to print/scan.
Is this happening with anyone else? Why would the printer crash if it boots with wireless enabled? If it is already set to a static IP, why would it still conflict with the DHCP on the router?
My router is perfectly working, it is in the same room as the printer, so the signal strength is good. The printer itself is quite stable except for this crash-after-boot-if-wireless-was-enabled issue on the printer.
I made the mistake of connecting the USB cable to my primary computer before installing the printer drivers, so even the USB option is not working (Windows recognizes the printer as an unknown USB device). If anyone can point me to the printer drivers (inf files), I would be grateful. The CD does not have the driver files in a convenient location. It seems to be embedded within the setup package somewhere.
Gardz and PrintDoc, I hope you can help us out on this one. I know many B110a users are struggling with the wireless issues, so HP needs to release a firmware fix and driver update soon. Wireless ought to work out-of-the-box, as this product is aimed at the SOHO users.

This is a workaround for the MBP wireless issue

There have been many topics on the MBP wireless issues already, but I thought some people might find this workaround helpful.
Firstly, my system is a 2.2Ghz MBP, running 10.4.10, and also airport extreme update 2007-04. I am using an airport express base station. My previous Powerbook never had any wireless problems, so I really couldn't blame the basestation for the MBPs poor wireless.
Warning - The workaround requires a little bit of work in the terminal. A little bit of understanding of how networks work is assumed here as well. So it is probably not for everyone ...
What I have observed - whenever the MBP loses connection, the airport basestation IP and MAC addresses are missing from the ARP table.
- To view the ARP table, type (in a terminal window) arp -a.
So, when the MBP wireless hangs, open up the terminal and type that in.
Do a Cntrl-C if the arp command is hanging and not returning anything.
In normal situations, a list of IP addresses and MAC addresses will show up.
As others have already noted, clicking on the airport icon in the menubar, will magically bring the wireless back to life. When this happens, the ARP table also gets magically populated correctly. Coincidence? I think not!
So, the workaround is to store a PERMANENT entry in the ARP table for the airport basestation IP and MAC address. In my case, I can use the Airport Utility software to confirm what the basestation IP and MAC addresses are (note MAC address = Airport ID in Airport Utility). I found the basestation IP=10.0.1.1 and the MAC=0:11:24:07:d7:f
To create a permanent ARP table entry for my airport basestation, I opened up a terminal window, and did the following -
1) login to my administrator account
2) type in the following command sudo arp -s 10.0.1.1 0:11:24:7:d7:f
3) type in my administrator password to authorise the change
4) type in (to confirm the changes have been made) arp -a
5) logout of my administrator account (from the terminal)
Ever since I did this, my MBP wireless performance has been flawless.
Note, if you shutdown or restart your computer, the arp entry disappears. This is ok for me as I hardly ever power down my MBP. As insurance I have added an account startup item to remind me to do the arp table entry.
This workaround is great for me because I don't have a need to use multiple wireless networks. It might not be practical for people who roam around onto different networks.
Give it a go and see if it works for you.
Message was edited by: michael louey

OK, after some further experimenting, I changed the multicast rate on my airport express. It was set at 6Mbps, and I changed it to 2Mbps.
I have read that the default multicast rate for previous 802.11g versions of Airport basestations is actually 2mbps. Excellent results so far !! I have set up a terminal command to continuously ping my airport router address every 15 sec, and there have been virtually no dropped packets so far over many hours.
ping -i 15 10.0.1.1
Interestingly, in Apple's Airport Admin software in my MBP there is no option to set the rate at less than 6Mbps (!!!!), so I had to use the Windows XP version of Airport admin software to make this change using a windows machine. Using the XP software you can set the muticast rate as low as 1Mbps.
If you are using Apples airport admin software (Tiger and Leopard) and you commit any sort of change in settings, the multicast rate will be re-set at a minimum of 6Mbps. My understanding of the multicast rate is that setting it too high is similar to shrinking the coverage area of the basestation, and limiting access only to clients who can transmit at the required multicast rate.
So my new theory is that the dropouts are caused by the MBP dropping off the airport due to not being able to achieve the set multicast rate. (this could be due to factors such as low signal strength, excessive interference or noise).
If you are using Apples more recent Airport admin software, you are having a minimum 6mbps muticast rate set, and this might be too high for your particular environment.
Just a theory.
(oh yeah, I enabled interference robustness on the MBP and the basestation just for good measure)

Macbook Pro (Late 2008) - Windows 7 64-bit, Bootcamp 3.1 - Wireless Issue

Hi Everyone,
I have a Macbook Pro (15-inch, Late 2008) model with Snow Leopard and Windows 7 64-bit dual boot. I have done a search and cannot find any reference to this problem on my hardware.
I have had no issues in Windows 7 when using Bootcamp v3.0. In the last week I have upgraded to Bootcamp v3.1. (completed twice, rolled back in between to prove that the issues was related to the Apple Update)
After I update to v3.1, I have issues with my wireless network. The network cannot resolve the name for any internet address. I can connect to wireless networks (tried multiple networks), all the DHCP settings seem to be retrieved correctly (Gateway, DNS etc) and I can ping local and machines outside my network without an issue provided I use the IP address. (Skype works - which uses direct IPs rather than names I have found over time)
As soon as I use a name for a destination for Web traffic, Mail, pinging (any application), my Macbook Pro cannot resolve the address and just bombs out.
If I connect to a wired network, the machine works perfectly and name resolution on that interface works. If I rollback (using Windows 7 rollback capability) to before the v3.1 Bootcamp is installed, the wireless networking also works perfectly.
I noticed this in the support area at apple:
http://support.apple.com/kb/TS3196
But this refers to wireless issues in Bootcamp drivers prior to v3.1 and on 13 inch Macbook. Wonder if this is a similar issue or related?
Anyone else seen this or point me in the direction of a fix?
Thanks,
Thommo

I'm looking into running Windows 7 64bit on the exact same MBP you have, so I'm curious as to whether or not you've found a solution yet outside of the forums.
Do you think it might be that the bootcamp 3.1 update is only for Windows 7 32bit and not for the 64bit version?

IP address Assignment for 802.1x Client

Working on a Wireless deployment using 802.1x and a question has come up regarding Address Assignment.
The design requires wireless vlan assignment based on username and Active Directory group assignment.
The simplest way to provide dynamic addressing would obviously be multiple DHCP Scopes on a server and use ip helper functionally to provide relay servers.
Another option (I think) would be to create IP address pools in the ACS server based on ACS group and have ACS pass it back as part of the authentication process. I'm wondering if this is even a valid option with 802.1x authentication. It seems to me that it would cut down on alot of the traffic assoiciated with a DHCP discovery/request/offer conversation as the number of wireless clients start to grow.

Err, no. There is no provision in EAP-TLS, PEAP (CHAP), or even basic EAP to provide network information (eg IP address/mask/gateway/DNS/etc).
There is also no provision in Windows 2k or XP interface management software to accept IP details for interface configuration via any wireless authentication protocol.
peter

Message on WCS/NCS: Attempted to use IP Address assigned to another device

Hi
i have two WLCs AIR-CT5508-K9, monitored by WCS (in retiring stage) and NCS.
All APs are grouped in HREAP groups based on their locations. The wireless users are getting ip from a dhcp pool running on routers located at each site. All dhcp commands on every routers are the identical. Eg. rtr1, located on site 1 has ip pool for wifi users 192.168.8.0/24. Rtr2 on site 2 has a ip pool for wifi users in range 192.168.8.0/24. Occasionally i am getting bellow message when some wifi users are unable to connect. After creating a HREAP group and associating APs to correct group, this message stops showing for a while but now i am getting them again.
The temp solution to get it all running is to clear ip dhcp pool on router located at affected site.
Any suggestions for a better solution?
Thanks
====================
NCS has detected one or more alarms of category Security and severity Minor in Virtual Domain ROOT-DOMAIN
for the following items:
1. Message: Client '14:5a:05:6c:75:37 (0.0.0.0)' which was associated with interface '802.11b/g/n' of AP 'STV-AP-7198' is excluded. The reason code is '3(Attempted to use IP Address assigned to another device)'. - Controller Name: GEORGE-WLC
===================

endpoint,
You are locally switching your networks, yes, but even without HREAP and WLCs, they are still connected networks in your overall topology, correct? I would never have site A with a given network that overlaps with a network in site B. With few exceptions, they should be completely separate, unique, non-overlapping network spaces. HREAP doesn’t even come into it.
The problem you’re likely having is that the WLC is seeing clients coming in from two different sites and because you are duplicating your configurations from site to site, the WLC sees duplicate IP assignment.
That said, you can try to turn off client IP address learning on the WLAN Advanced tab to see if that helps.
Justin

MacBook wireless issue (ongoing) & DIY airport card replacement

Hello,
With reference to the ongoing MacBook/OSX (10.5.3) Leopard intermittent wireless issues discussed in this forum has anybody gone ahead and taken matters into their own hands and purchased and installed a new Airport card for their MacBook from www.ifixit.com?
Further details at: http://www.ifixit.com/MacBook-Parts/MacBook-Core-2-Duo-Santa-Rosa-Penryn-802-11n -Airport-Extreme-Card/IF186-062
If so, did it resolve your intermittent Airport issues?
It seems to me that when the MacBook is running on battery power only the Airport card does not realise that the MacBook has come out of sleep sometimes and therefore does not always function correctly. Maybe the Airport card does not receive sufficient power when the MacBook comes out of sleep mode whilst running on batteries only?
Typically when I run the MacBook connected to power the intermittent wireless problem does not occur.
This issue has been a recurring problem for me for 6 months now and unfortunately I have not seen Apple address this issue.
My MacBook is 6-months old and is a black MacBook using a 2.2GHz processor running Leopard OSX 10.5.3.
Cheers,
treaders

Visit Apple Store and replaced the Airport card.

TM2T-1000 Wireless issue

Im not sure if this issue has been addressed at all but after a quick scan of the forum i couldnt find my problem coming up at all so i thought i would ask it anyway.
So anyway i have a TM2T-1000 and when i am at home my wireless keeps dropping. It says that it is still connected and i have an ip addy still but i cant browse around and i also cannot ping outside websites either. i log into the router and and change the wireless channel or disconnect and reconnect the connection and this sometimes resolves the problem for about 30 seconds to a minute but then just stops working again. now normally i wouldnt blame the computer but the problem im having is so weird and dont know what is causing it. What i mean by that it that i use my comp at work and never seem to have any trouble with the wireless there and it just works like it is supposed to. Now i know that this will have some telling me that its my router at home, but i cant blame it completely either because we have another laptop an Acer that has no trouble maintaining the wireless with the home router and even when my tm2 drops i will ask my friend if his is still working and he will tell me that he isnt having any trouble. So im wondering if maybe it is a driver or perhaps a hardware compatability issue. This issue appears to occur after waking the computer out of sleep and i try to get on the internet which will work for about a minute then drop. I have a d-link dir-601 router and was thinking maybe the wireless card was simply incompatable or perhaps a driver thing but ive tried updating my driver and it says that it is up to date. So unfortunately i remain confused. There is a glimpse of light at the end of this tunnel however which is that i have found a work around but it still annoying and i wish that instead it would just work. but that is to restart my comp after sleep everytime i intend to be on the internet for any extended period of time and after a restart it seems to hold the connection fine that is until i close it and open it out of sleep again... So to recap the issue appears to be that i have trouble maintainning home connection only when awaken from sleep mode..... so weird any help would be appriciated. thanks

started facing this issue for past one week - now i think i fixed it ,
Try this
1, Press windows key + X
2, in the inegrated wireles devices dropbox in Hp customization
3, Choose Open wireless Assitsant
4, First turn on all wireless devices wireless adapter and bluetooth adapter
5, then click on the Properties button
6, Uncheck everhing and hit apply

T40 Wireless Issue - No IP Address Assigned

Similar Messages

Maybe you are looking for